3 pages · WCAG 2.2
Web accessibility
One page per real barrier, with the WCAG 2.2 criterion it fails, who it affects, how to test it and how to fix it. And one per sector, where accessibility has a different story.
Barriers
Every barrier, explained without jargon: what fails, who it affects and how to fix it.
- 01
Keyboard navigation
If a control cannot be reached and operated with a keyboard alone, it does not exist for a large group of your users — and no automated scanner will tell you.
- 02
Accessible forms
Most accessibility money is lost in forms. A label that is only a placeholder, an error announced only in red — each is a small thing, and together they are a checkout nobody can complete.
By sector
Where accessibility has its own story and its own risks.
- Sector
E-commerce
E-commerce is explicitly named in the European Accessibility Act, and the checkout is where accessibility barriers stop a sale rather than merely annoying someone.
Keep reading
-
Regulations
What the law asks, and of whom.
-
Guides
How to test and verify.
-
The method
All 37 checks, published.
Rather have it checked for you?
A person tests your site with a keyboard and a screen reader, and hands you what needs fixing.
Regulatory requirements vary by jurisdiction, service, organisation and other factors. Uxerfy provides accessibility assessments and compliance-oriented information, not legal advice or legal certification. Consult qualified legal counsel for a determination of your obligations.