Web accessibility: what WCAG asks and how to build it in
Website accessibility in plain English: what WCAG 2.2 level AA asks, which laws may apply, a self-check list, and how to build it in rather than patch it.


Someone tries to book with you using only a keyboard, a screen reader or a phone at 200% zoom, and gets stuck on a button that cannot be reached. They leave, and you never hear why. Website accessibility means making sure people with disabilities, and many others, can use your site or app without hitting walls like that one.
This guide explains what the reference standard, WCAG 2.2 level AA, asks in plain English, which legal duties may apply, a self-check list for this week, and how to build accessibility in instead of patching it.
Why website accessibility matters for your business
Accessibility is often presented as a legal topic. It is first a customer topic.
- Your customers. Some visitors are blind, deaf or cannot use a mouse; others are older, have a broken wrist or read in bright sunlight. An accessible site serves all of them.
- Quality. The same habits that help a screen reader (clear headings, real buttons, labelled fields) give you cleaner code, fewer bugs and pages that search engines understand better.
- Legal duties. In several markets, some websites and apps must meet an accessibility standard, depending on country, sector and size (see below).
What WCAG 2.2 level AA asks, in plain language
The Web Content Accessibility Guidelines (WCAG) are published by the World Wide Web Consortium (W3C). As of October 2026, WCAG 2.2, published in October 2023, is the current W3C Recommendation; WCAG 3 is still a working draft. Each requirement, called a success criterion, has a level: A (the minimum), AA (the usual target in laws and contracts) and AAA (the most demanding). In practice, “accessible” usually means meeting levels A and AA.
The criteria rest on four principles: perceivable, operable, understandable and robust. On a real page, that means:
Contrast and readable text
- Normal text needs a contrast ratio of at least 4.5:1 against its background; large text needs 3:1.
- Buttons, field borders and icons that carry meaning need at least 3:1 against what surrounds them.
- Colour must never be the only signal: an error shown in red also needs a word or an icon.
- Text must stay readable when zoomed to 200%, and pages must reflow on a narrow screen without scrolling sideways.
Keyboard and focus
- Everything you can do with a mouse must work with a keyboard alone: menus, forms, date pickers, pop-up windows.
- The keyboard focus must be visible, follow a logical order, and never be hidden behind a sticky header or a cookie banner.
- Nobody should get trapped in a component they cannot leave with the keyboard.
Text alternatives and captions
- Images that carry information need a text alternative; decorative ones should be ignored by screen readers.
- Videos need captions; pre-recorded videos also need an audio description when important information is only shown, not said.
Forms and sign-in
- Every field has a visible label tied to it in the code, not just a placeholder that disappears.
- Errors are explained in words, next to the field, with a suggestion when one is possible.
- Signing in must not depend on solving a puzzle or remembering a code without help: letting people use a password manager or paste a code is one way to meet it.
What WCAG 2.2 added
Compared with WCAG 2.1, version 2.2 adds nine success criteria. At levels A and AA, the ones you will notice most are: click and tap targets of at least 24 by 24 CSS pixels (or enough space around them), focus not obscured by other content, an alternative to dragging movements, help placed consistently across pages, no asking twice for information already given in the same process, and the sign-in rule above.
The legal side: duties depend on where you are
Accessibility law differs by country, sector and company size. The points below are general information as of October 2026, not an answer to whether a law covers your business.
- European Union. The European Accessibility Act (Directive (EU) 2019/882) has applied since 28 June 2025 to certain products and services, such as e-commerce and banking services. Micro-enterprises that provide services are exempt. Each country has its own transposing law; the official text is on EUR-Lex.
- France. Public bodies and some companies must follow the RGAA, the government’s reference framework built on WCAG (accessibilite.numerique.gouv.fr).
- United States. The Americans with Disabilities Act (ADA) has been applied to websites by many court decisions; the Department of Justice publishes guidance on ada.gov.
- Australia. The Disability Discrimination Act 1992 applies to services, online ones included; the Australian Human Rights Commission publishes guidance on humanrights.gov.au.
Note that the W3C does not certify websites, and no standard turns an automated score into legal compliance. If a contract or a law may apply to you, have a lawyer confirm what it requires.
This article gives practical guidance. It does not replace advice from a lawyer in the country where you operate.
A website accessibility checklist you can run in an hour
No special skills needed. Pick your three most important pages (home, a service page, a form) and check:
- Keyboard only. Put the mouse aside and press Tab. Can you use every link, button and field, and always see where you are?
- Zoom. Zoom to 200%, then narrow the window to phone width. Is anything cut off or reachable only by scrolling sideways?
- Contrast. Test text and button colours with a free contrast checker.
- Images. Do informative images have a short, useful text alternative, and charts a written summary?
- Headings. One main heading per page, then sub-headings in a logical order?
- Forms. Does every field have a visible label? Submit the form empty: are the errors clear and next to the fields?
- Video and audio. Are there captions, and are they accurate?
- Language. Does each page declare its language, so screen readers pronounce it correctly? This matters on a multilingual website.
- Automated scan. Run a free tool such as the axe browser extension, WAVE or Lighthouse (examples as of October 2026). They find some problems fast but cannot judge whether a text alternative makes sense.
- Real users. If you can, ask someone who uses a screen reader or keyboard every day to try your key journey.
How to build accessibility in rather than patch it
Fixing accessibility after launch means reopening finished designs, components and content. Building it in costs far less.
At design
Check contrast in the design system before the first screen, design visible focus states and large enough targets. Write accessibility requirements into the specification, with “WCAG 2.2 level AA” as the target, so everyone works to the same rule.
In development
Start from semantic HTML: a real button is a <button>, a real link is an <a>. Fewer scripts and simpler components also keep pages light and quick to load on mobile networks, as our guide to lighter websites and apps explains. Build accessible components once (menu, modal, date picker, table) and reuse them everywhere. If your content is managed in a CMS, including a headless CMS, make alternative text and headings part of the editing screens. The same principles apply to mobile apps, which have their own accessibility features; our guide on choosing a web or mobile app covers that choice.
In testing and release
Add automated accessibility checks to the pipeline that tests every change, so regressions are caught before they reach users. Our founder, Anass Chabbab, led this kind of build and test automation in his previous roles, on the Orange Business Services projects: continuous integration with Jenkins and SonarQube. Accessibility checks belong in that kind of pipeline, alongside keyboard and screen-reader tests during user acceptance testing.
After launch
Train the people who publish content: most new issues come from images without alternatives. Publish an accessibility statement saying what is not yet accessible and how to contact you, and answer those messages.
Frequently asked questions
Is there an official WCAG certification for a website?
No. The W3C writes the guidelines but does not certify sites. A company can claim conformance after an audit against WCAG, and some countries have their own framework, such as the RGAA in France. An audit describes a site on one date; each release can change the result, so ongoing checks matter more than a one-off report.
Do accessibility overlays or plugins make a site accessible?
Not on their own. Widgets that add a toolbar or repair a page automatically cannot fix the underlying code: a button out of keyboard reach, a form without labels, a video without captions. Some users find they get in the way of their own assistive tools. The durable fix is in the design, the code and the content.
What changed between WCAG 2.1 and WCAG 2.2?
WCAG 2.2 adds nine success criteria (the six at levels A and AA are listed above) and removes one obsolete criterion about HTML parsing. A site that meets WCAG 2.2 also meets WCAG 2.1, so aiming for 2.2 now is the simpler choice.
In short
Website accessibility lets everyone use your site and improves quality for all. WCAG 2.2 level AA is the usual target: contrast, keyboard, text alternatives, captions, clear forms and visible focus. Legal duties depend on country, sector and size: check official sources and a lawyer. Start with the one-hour checklist, then build accessibility into design, code and testing.
We build websites and business applications with accessibility in the specification from day one, as part of our web development work. Unsure where your site stands? Book a free 30-minute discovery call: we look at your key journeys together and tell you where to start.
Related servicesWebsites and web appsCustom softwareSaaS products
Let’s talk about it on a 30-minute discovery call, free and with no obligation.
Get our next articles in your feed: follow AnazTech on LinkedIn.Follow on LinkedIn






