Critical3 pages · 12 elements
Checkout fields need accessible names
One shared form-component fix can clear all 12 affected fields.
Deterministic product example
Example accessibility report
This report uses fictional fixture data. The finding detail matches the live free scanner; the site coverage and change summary preview the approved Monitoring report contract.
Monitoring report preview
Coverage and change, without page-count noise
Monitoring is in development and cannot be purchased yet. This deterministic preview shows the approved information hierarchy, not a live customer scan.
- Pages sampled
- 25
- Templates covered
- 8
- New findings
- 2
- Verified fixed
- 4
- Unchanged
- 1
Coverage example: 25 of 42 discovered pages, selected across 8 path/template groups. A sampled report documents what was checked; it does not claim untested pages passed.
Accessibility scan
https://northstar.example/checkout
- Critical
- 2
- Serious
- 1
- Moderate
- 0
- Minor
- 0
3 distinct issues across 45 elements on this page. Lighthouse score: 71/100
Your 3 highest-priority issues
Ranked by severity and how many elements are affected.
- CriticalWCAG 4.1.2 (Level A)12 elements affected
Form fields need accessible names
The checkout fields do not expose names that assistive technology can announce.
Screen-reader and voice-control users may not know what information each field expects.
How to fix it
Connect every input to a visible label with matching `for` and `id` values.
Estimated effort: minutes
Show affected elements
<input name="address" autocomplete="street-address">
- CriticalWCAG 4.1.2 (Level A)2 elements affected
Buttons have no discernible text
Two icon-only cart controls have no programmatic name.
Screen-reader and voice-control users cannot identify or invoke the controls reliably.
How to fix it
Add concise visible text or an `aria-label` that describes each button action.
Estimated effort: minutes
Show affected elements
<button class="icon-only"><svg aria-hidden="true">…</svg></button>
- SeriousWCAG 1.4.3 (Level AA)31 elements affected
Text contrast is below the minimum
Secondary product text is too faint against its background.
People with low vision or reduced contrast sensitivity may be unable to read the text.
How to fix it
Darken the shared muted-text token until normal text reaches at least a 4.5:1 contrast ratio.
Estimated effort: minutes
Show affected elements
<p class="muted">Shipping calculated at checkout</p>
Keep this page from regressing
Monitoring samples up to 25 pages, saves change history, and alerts you when a new finding appears. Your complete single-page result stays free.
Ask about monitoring — $9/monthThis is an automated scan using Google Lighthouse (axe-core rules). Automated testing reliably detects roughly a third of WCAG 2.1 success criteria; issues such as keyboard traps, focus order, and screen-reader flow require manual review. This report is not legal advice and does not certify compliance with the ADA, Section 508, or the European Accessibility Act.