Public accessibility report
us.gobicashmere.com
Scanned · https://us.gobicashmere.com/?country=US
Automated score
Significant findings
At a glance
Axe rules in a real browser. Not a substitute for manual testing.
Score 40/100 based on automated checks — 5 findings, highest severity: serious.
What this means: Treat this as a prioritized to-do list from automation—not proof everything is fixed, and not a substitute for manual checks when it matters.
Findings by severity
This report is not indexed by search engines by default.
We list the highest-severity rule types first (critical and serious before moderate and minor). Each card explains how the issue can affect real tasks—forms, navigation, reading text—not just a rule name.
Up to five priority rule types (deduplicated by rule ID). Start here before reading every row in the full breakdown—guides open in plain language, with technical references optional.
Why it matters
This affects people who rely on names and descriptions instead of visuals alone.
Ensure each HTML document contains a non-empty <title> element
Documents must have <title> element to aid in navigation
Rule ID: document-title
Why it matters
Higher-severity items are more likely to block tasks or confuse assistive technology on this page.
Ensure every HTML document has a lang attribute
<html> element must have a lang attribute
Rule ID: html-has-lang
Why it matters
Fixing it reduces friction for people using keyboards, screen readers, or zoom.
Ensure the document has a main landmark
Document should have one main landmark
Rule ID: landmark-one-main
Why it matters
Fixing it reduces friction for people using keyboards, screen readers, or zoom.
Ensure that the page, or at least one of its frames contains a level-one heading
Page should contain a level-one heading
Rule ID: page-has-heading-one
Why it matters
This can affect keyboard-only users and focus order—worth checking interactive components.
Ensure all page content is contained by landmarks
All page content should be contained by landmarks
Rule ID: region
Follow this path to turn the report into real fixes, then confirm with a new scan—no account required.
Fix the items above on real user paths
Checkout, signup, contact, and main navigation matter more than obscure pages.
Use our guides where they match
Each “Open fix guide” links to a short article. Browse the issue library for more.
Verify with quick manual checks
Tab through forms and menus; note anything you cannot reach or operate without a mouse. Spot-check with zoom and your OS screen reader if you can.
Run a fresh scan to see if the score moves
Use Run a fresh scan below—each run gets its own link so you can compare before and after without logging in.
Use a checklist for important launches
Pre-launch accessibility checklist covers common gaps automation misses.
Keep improving over time
Fix repeated patterns (headers, cards, nav) before one-off pages. After updates, rescan and keep both report links to see what changed. One automated pass does not catch everything—use it as a structured starting point, not the final word.
Every finding from this scan—open when you need the complete list.
Findings are grouped by category when the scanner provides one. Fix higher severity items in each group first.
document-titleEnsure each HTML document contains a non-empty <title> element
Documents must have <title> element to aid in navigation
html-has-langEnsure every HTML document has a lang attribute
<html> element must have a lang attribute
landmark-one-mainEnsure the document has a main landmark
Document should have one main landmark
page-has-heading-oneEnsure that the page, or at least one of its frames contains a level-one heading
Page should contain a level-one heading
regionEnsure all page content is contained by landmarks
All page content should be contained by landmarks
Grouped by automated severity. Each rule links to our issue guide when we have a match.
Blocks or severely harms access for some users—fix before release when possible.
None in this bucket for this scan.
Serious findings—often forms, names, or major contrast failures on key UI.
Moderate and minor rules—still worth fixing in templates to avoid repetition.
Pair fixes with the pre-launch checklist and WCAG in plain English.
Methodology, comparison, sharing, and caveats—open when you need them.
Either many rules fired or the page was minimal. Use severity counts and categories below; confirm the worst issues manually with a keyboard.
This URL scored 40/100 on our automated summary. For orientation only, we show an illustrative blended average of 62/100 from sample public scans (not a live industry census). Your page is below that reference point (-22 points).
WCAG 2.1 Level AA is the conformance target most teams cite for policy. Automated scans surface many (not all) AA-related patterns; manual testing still covers context, state changes, and complex interactions.
Link to this report or embed it on an internal wiki. The iframe loads the full public report; only use when the page is appropriate to share.
<a href="https://testaccessbility.com/report/us-gobicashmere-com-accessibility-report-8ce726be" rel="noopener" style="display:inline-flex;align-items:center;gap:0.35rem;font:600 14px system-ui,sans-serif;color:#0f766e;text-decoration:none;border:1px solid #99f6e4;border-radius:9999px;padding:0.35rem 0.75rem;background:#f0fdfa">TestAccessibility: 40/100 · us.gobicashmere.com</a>
[TestAccessibility score 40/100 — us.gobicashmere.com](https://testaccessbility.com/report/us-gobicashmere-com-accessibility-report-8ce726be)
<iframe src="https://testaccessbility.com/report/us-gobicashmere-com-accessibility-report-8ce726be" title="Accessibility report for us.gobicashmere.com" width="100%" height="480" style="border:0;border-radius:8px;max-width:42rem" loading="lazy"></iframe>
This public report already lists all violations above. Download a machine-readable snapshot, or use your browser's print dialog to save a PDF. Multi-format exports (PDF, Excel, CSV) with extra options are available from a completed scan in Free scan when signed in (audit view).
Other completed public scans on the same hostname or with a similar score.
After you fix issues, scan the same URL again. Each run gets its own report link—keep both to see whether the score and severity counts improved.
No account required. High-traffic or template pages are good candidates to rescan first.