Fixes
Every failure family, and exactly what we do about it
19 families of accessibility failure, keyed to the engine's own rule tables — 14 applied automatically, 5 routed to your review queue. For each one: which of our engines detects it, whether a fix is applied automatically or waits for your approval, and how to fix it yourself if you would rather.
The catalogue
14 families are applied for you. 5 wait for a human, on purpose.
Across the whole WCAG 2.2 A and AA surface we track 55 success criteria. 39 of them have at least one automated rule or probe behind them; 16 cannot be tested by any machine and are handled by the professional audit. We would rather tell you that than imply automation covers everything.
- Buttons with no accessible name Auto-applied A nameless button — search, cart, quantity — cannot be operated by voice or announced by a screen reader.
- Checkout fields missing an autocomplete purpose Auto-applied Without autocomplete tokens, autofill cannot help — and checkout gets longer for everyone who needs it shorter.
- Content links distinguished by colour alone Auto-applied If colour is the only link cue, colour-blind readers cannot find the links.
- Document links without type and size Auto-applied A bare "Download brochure" link springs a 40 MB PDF on people who could not see it coming.
- Focus outline suppressed by theme CSS Auto-applied outline: none makes the keyboard cursor invisible — nobody can see where they are.
- Form fields with no label Auto-applied An unlabelled checkout field is a guess for anyone who cannot see its placement.
- Images without alternative text Auto-applied Product images with no alt text are invisible to anyone using a screen reader.
- Links with no discernible text Auto-applied An icon-only or image-only link announces itself as "link" and nothing else.
- Missing document language Auto-applied The page never declares what language it is in, so screen readers guess the pronunciation.
- Missing document text direction Auto-applied An RTL store served without dir="rtl" renders its own language back to front.
- No skip link past repeated content Auto-applied Without a skip link, a keyboard user tabs through the whole header on every page.
- Positive tabindex hijacking focus order Auto-applied A tabindex of 1 drags keyboard focus out of reading order on every page it touches.
- Redundant or conflicting title attributes Auto-applied Empty and duplicate title attributes add announcement noise; conflicting ones get a human decision.
- Viewport meta that blocks zooming Auto-applied user-scalable=no locks pinch-zoom away from the people who need it most.
- Ambiguous link text Review queue "Read more" ×14 tells a screen-reader user nothing about where any of them go.
- Dense text with no plain-language summary Review queue Page text that reads like a contract shuts out people with cognitive differences, dyslexia or ADHD.
- Landmark structure problems Review queue Missing or duplicated landmarks remove the shortcuts screen-reader users navigate by.
- Links that open a new tab without warning Review queue An unannounced new tab strands screen-reader users with a back button that no longer works.
- Text that fails colour contrast Review queue Low-contrast text is unreadable for many people — and a brand decision, so a human always approves the fix.
Detection runs the whole automatable surface, not just these ten — the families are what the product can act on. How detection, fixing and proof fit together →
Which of these does your store have?
Run the free scan and find out. Three engines, 19 Klarvo checks, your real pages including a populated basket and a hydrated checkout.