Accessible websites work for more people: customers using a keyboard, a screen reader, or a phone in bright sunlight. They also tend to be clearer for everyone. The standard most organisations aim for is the Web Content Accessibility Guidelines (WCAG) 2.2, at Level AA.
What the standard is
WCAG is published by the W3C. It is organised around four principles, often shortened to POUR:
- Perceivable: people can see or hear the content
- Operable: people can use the controls, including with a keyboard
- Understandable: the content and behaviour are clear
- Robust: the site works with current and future assistive tools
The full standard and its explanations are at W3C: Web Content Accessibility Guidelines 2.2.
Level AA is the level most businesses target. It is also the level that most accessibility guides and some legal requirements refer to. Check the requirements that apply to your business with a qualified adviser.
Ten checks you can do today
- Keyboard only. Press Tab to move through the page. Can you reach every link, button, and form field? Can you see where the focus is?
- Text size. Zoom the browser to 200 percent. Does the text stay readable without sideways scrolling?
- Colour contrast. Is body text clearly readable against its background? Light grey text on white is a common failure.
- Images have descriptions. Photos that carry meaning need alternative text. Decorative images can be skipped.
- Form fields have labels. Each field should have a visible label, not only placeholder text.
- Error messages are clear. A form error should say which field is wrong and how to fix it.
- Headings make sense. The page should have one main heading, with sections in a logical order.
- Links describe where they go. "Read our pricing" is clearer than "click here".
- Phone number and contact are easy to find. Visitors should not need to hunt for them.
- Video and audio have text. Captions or a transcript help everyone, including people in noisy places.
What not to claim
Do not say your website is "fully WCAG compliant" unless it has been tested against the standard. A more accurate statement is that the site was designed and tested with WCAG 2.2 Level AA in mind, and list the date and method. This is the careful wording many accessibility guides recommend.
A practical order
- Fix the things that stop people completing tasks: keyboard access, form labels, and the contact route.
- Fix contrast and text size.
- Review images, headings, and links.
- Test again after every big change to the site.
Accessibility is ongoing. Each new page, plugin, or photo can introduce a new problem.
This is general guidance. It is not legal advice or a formal audit.