WCAG 2.2 Level AA · 1 page scanned · 21-Aug-2026
16 issues found across 1 page, checked against WCAG 2.2 Level AA.
22 of 26 automated checks passed.
Around 1 in 5 people has a disability that can affect how they use a website. On the pages we scanned, some of them cannot complete key tasks today — they will leave, and you will never see it in your analytics as anything other than a bounce.
Number of individual problems found in each area, across every page scanned.
Start here. These are the highest-impact fixes across the pages we scanned.
Fixing these clears 4 of your 4 most serious issue types.
Our team can remediate all 16 issues and re-audit to confirm you're compliant.
Book a free consultationEvery automated check we ran, grouped by the part of the experience it affects. A category passes only when every check in it passed on every page scanned.
Images, icons, audio and video have text alternatives so they still make sense to someone who can't see or hear them.
Text stands out enough from its background to stay readable in poor light or with reduced vision.
Every field is clearly labelled, so people know what to type and screen readers can announce it.
The whole page can be operated with a keyboard alone, without getting stuck, and the focused item is always visible.
Headings, landmarks and lists are used properly, so assistive tech can navigate the page in a sensible order.
Buttons, links and controls have names that describe what they do when read aloud.
The page declares its language so screen readers use the right pronunciation.
Content reflows and stays usable when zoomed in or viewed on a small screen.
Every issue we found, worst first — what it is, who it affects, and what fixes it.
| Issue | Severity | Pages | Business Impact | Recommendation |
|---|---|---|---|---|
Buttons don't say what they do | Critical | 1 | These buttons are announced with no name. A customer using a screen reader cannot tell what the button does — if it is "Add to cart" or "Submit", the journey ends here. | Give the button visible text, or an aria-label/aria-labelledby/title describing what it does — icon-only buttons need an accessible name. |
There's no visible focus indicator | High | 1 | There is no visible focus indicator, so keyboard users cannot see where they are on the page. Navigating becomes guesswork. | Don't remove the default focus outline (outline:none) without replacing it — add a visible :focus-visible style (outline or box-shadow) with enough contrast against the background. |
Lists are built incorrectly | High | 1 | Lists are malformed, so screen readers may not announce how many items there are — which matters for product lists, features and steps. | Make sure <ul>/<ol> elements only contain <li> children (move any other markup outside the list, or into an <li>). |
Links don't say where they go | High | 1 | Screen readers announce these links as "link" with no destination. Customers navigating by links alone cannot tell where any of them go, so they stop. | Give the link visible, non-empty text, or add aria-label/aria-labelledby describing its destination — icon-only or image-only links need an accessible name. |