Accessibility: what WCAG 2.2 AA means for your website
WCAG 2.2 AA is the standard behind accessibility law and public tenders. What the criteria ask for, and the ten checks that catch the common failures.
The short answer
WCAG, the Web Content Accessibility Guidelines, is the international standard that defines what an accessible website is. It has three levels: A, AA and AAA. Level AA is the one that laws, tenders and procurement documents mean when they say “accessible”. Version 2.2 is the current one.
The standard is long. The failures we find on business websites are not. Most come from the same ten things, all fixable, most of them cheap when the site is built properly.
The ten checks that catch most failures
- Contrast. Normal text needs a contrast ratio of at least 4.5 to 1 against its background, large text at least 3 to 1. Light grey text on white fails, and it is everywhere.
- Keyboard. Everything that can be done with a mouse can be done with Tab, Enter and arrow keys. Menus, forms, sliders, modals. Try it on your own site for two minutes.
- Visible focus. When you Tab through the page, you can always see where you are. Sites that remove the focus outline for looks fail here.
- Headings. One main heading per page, then a logical order without skipping levels. Screen reader users navigate by headings the way sighted users skim.
- Alt text. Every meaningful image has a description; decorative images are marked as such. This is also what search engines read.
- Form labels. Every field has a visible label that is connected to it in the code, not just placeholder text that disappears when you type.
- Error messages. When a form fails, the message says which field and why, in text, near the field. Red borders alone are not enough.
- Motion. Animations respect the visitor’s reduced-motion setting, nothing flashes, and anything that moves can be paused.
- Target size. Buttons and links are large enough to tap on a phone without hitting the neighbour. A 2.2 criterion that catches many mobile menus.
- Language and structure. The page declares its language, uses real buttons and links rather than clickable divs, and works with the browser zoomed to 200 percent.
Where automated tools stop
| Automated checks find | A person must check |
|---|---|
| Missing alt attributes, contrast failures, missing labels, missing language | Whether the alt text is meaningful, whether the order makes sense by keyboard, whether a screen reader can complete the form |
| Duplicate ids, empty links, missing headings | Whether error messages help, whether focus goes to the right place after an action, whether a modal traps focus |
Why it pays beyond compliance
The overlap between accessibility, search visibility and plain usability is almost complete. Headings, alt text, labels and language are exactly what search engines index. Contrast, focus and target size are what every visitor on a phone in sunlight needs. Forms that explain their errors convert better for everyone. Building to AA is not a tax on the design; it is a description of a website that works.
What this means for you
Run the ten checks on your homepage and your most important form. Most take a minute each. If your site fails several, the fix is usually structural and belongs with whoever runs the site, not with an overlay. If you are commissioning a new site, put AA in the contract and ask how it will be verified. Then check the legal side for your sector, because the technical standard is the same either way.
Frequently asked questions
Does WCAG apply to my business legally?
WCAG itself is a standard, not a law. Laws and regulations refer to it. In the EU the European Accessibility Act covers many businesses offering digital services, including online sales, and public bodies have had obligations for years. Which rules apply to you depends on your sector and size, so treat this article as the technical side and check the legal side for your situation.
Is an accessibility overlay or plugin enough?
No. Overlays add a toolbar on top of an inaccessible page; they do not fix the page. Many accessibility professionals and users advise against them, and they do not satisfy the standard. Fix the underlying structure, contrast and labels.
How do I know if my site passes?
Automated checks catch a share of the issues, such as missing alt text and contrast failures. The rest needs a person: navigating by keyboard only, using a screen reader on key pages, and checking that forms explain their errors. A short manual audit of your main pages tells you most of what you need.
Does accessibility hurt the design?
Good design and accessibility want the same things: readable contrast, clear structure, visible focus, forms that explain themselves. What accessibility rules out is decoration that costs function, such as light grey text on white and buttons that only show on hover. Most designers agree once they have seen a screen reader user try their site.
Sources
- W3C Web Accessibility Initiative: WCAG 2 overview (accessed 2026-09-11)
- W3C: How to meet WCAG (quick reference) (accessed 2026-09-11)
- European Commission: European Accessibility Act (EAA) (accessed 2026-09-11)