WCAG 2.2 Level AA · 1 page scanned · 19-Aug-2026
22 issues found across 1 page, checked against WCAG 2.2 Level AA.
21 of 27 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 6 most serious issue types.
Our team can remediate all 22 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. |
Tap targets are too small or too close together | High | 1 | Tap targets are too small or too close together, causing mis-taps for anyone with limited dexterity or using a phone one-handed. | Make the tappable area at least 24×24px, or leave 24px of clear space around it. Padding on the link/button is usually enough — the visible icon itself doesn't have to grow. |
Links are shown by colour alone | High | 1 | Links are distinguished from surrounding text by colour alone, so colourblind readers cannot tell what is clickable. | Underline links inside body text, or otherwise distinguish them by something other than colour alone (weight, icon) so colourblind readers can spot them. |
Text is hard to read against its background | High | 1 | Text is hard to read for anyone with reduced vision, and for everyone on a phone in daylight. Low-contrast pricing, form labels and calls-to-action measurably reduce conversion. | Darken the text color or lighten the background until the contrast ratio reaches 4.5:1 (3:1 is enough for large text — ≥18pt, or ≥14pt bold). Check hover/focus states too, not just the default. |
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. |
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. |