Web accessibility: where to start

Someone should be able to read your services, use the menu and send an enquiry without depending on a mouse, perfect vision or precise movements. Accessibility work starts by checking whether those tasks are possible.

People use the web with screen readers, magnification, keyboards, voice control and other tools. A page that looks clear to its designer may still prevent someone from completing a simple form.

Use WCAG to organise the work

The W3C Web Content Accessibility Guidelines provide testable criteria. WCAG 2.2 is the current W3C Recommendation; its A, AA and AAA levels build on one another. An AA assessment includes the applicable A and AA criteria.

Choose the version and level required by the project. Legal obligations depend on the service and jurisdiction; an automated score is not a compliance certificate.

Check the main tasks

Keyboard navigation. Put the mouse aside. Can you reach every link, open and close the menu, complete the form and dismiss a dialog? Keep focus visible and return it to a sensible place when a dialog closes.

Headings. Use a clear page title, section headings and subsections in a logical order. Screen-reader users can navigate by headings, so choose levels for structure rather than text size.

Images. Describe the purpose of informative images. Use an empty alt="" for decoration so it can be skipped. A linked logo needs an accessible name that explains the destination.

Forms. Give each field a visible label and explain errors beside the relevant field. A placeholder disappears while typing and does not replace a label.

<label for="email">Email address</label>
<input type="email" id="email" name="email" autocomplete="email">

Contrast and size. At WCAG AA, ordinary text generally needs a contrast ratio of 4.5:1; large text needs 3:1. Check the contrast criterion and its exceptions. Also test zoom, narrow screens and visible focus indicators.

Motion and media. Respect reduced-motion preferences. Give users control over moving content and provide captions or other appropriate alternatives for media.

Combine automated and manual checks

Tools such as axe, WAVE and Lighthouse can identify missing labels, contrast failures and other detectable problems. They cannot judge every description, focus sequence or interaction.

Test complete tasks with a keyboard and a screen reader, and involve users with disabilities when possible. Record which pages and states were checked: an open menu, a form error and a checkout dialog may reveal issues absent from the initial page.

Fix barriers to completing tasks first, then check that the correction works throughout the site. Ask us for an accessibility review if you need a prioritised list of changes.