Accessibility

Accessibility features of websites: what to check in real use

Explore accessibility features of websites through practical checks of navigation, forms, images and media, and understand where an initial review stops.

Accessibility features of websites: start with a real task

Accessibility features of websites should help people read information, move around and complete tasks in ways that work for them. A badge or settings panel cannot show whether someone can actually request a quote. Choose an important journey and test it from the first link to the final confirmation.

This is an introduction to practical checks, not a conformance audit or legal assurance. W3C explains that its own Easy Checks cover only a limited set of issues: a page can pass them and still contain serious barriers. Record what you tested, what failed and what needs specialist review rather than declaring the whole site accessible.

Make keyboard navigation visible and predictable

Try navigating without a mouse. Check whether you can reach links, buttons, menus and form controls, see where focus is, activate controls and move away again. W3C accessibility principles include keyboard operation and avoiding keyboard traps. A menu that opens but cannot be closed can block the rest of the journey.

For your test record, describe the exact control and action rather than writing “keyboard issue”. For example, note whether focus disappears when a dialogue opens or whether closing it returns you to a sensible place. Ask the developer to explain the intended behaviour, fix the barrier and repeat the same task. Testing only the home page will miss problems in later steps.

Use meaningful structure and clear instructions

Headings should describe sections and organise the page, rather than merely make text larger. Link wording should help people understand the destination. A collection of identical “read more” links can be harder to interpret without the surrounding layout. These are design and content decisions as well as development tasks.

Form fields need labels that remain understandable while someone enters a value. Explain required information and useful formats before a mistake occurs. If input is invalid, identify the affected field and tell the person how to correct it. GOV.UK’s error summary pattern demonstrates linking a summary of problems to the relevant inputs. Do not erase valid answers while asking someone to fix one field.

Keep content usable when its appearance changes

Try zooming and viewing the page on a narrow screen. Look for text hidden behind fixed banners, overlapping controls and instructions separated from their fields. Check contrast with an appropriate tool rather than judging it only by eye. Do not use colour as the sole way to explain a status or error.

Use realistic content during testing: a long service name, a multi-line address and a useful error message. Short placeholder text can conceal layout problems. When you record an issue, include the browser, zoom setting and step that produced it. This gives the team a repeatable case to investigate rather than a vague request to make everything more readable.

Give images and media an equivalent purpose

Alternative text depends on what an image does in context. W3C distinguishes informative images, which need an appropriate text alternative, from decorative images, which can use an empty alternative. A linked image needs to communicate the function or destination. Do not fill image descriptions with SEO phrases unrelated to the image.

For a diagram, ask whether someone can obtain the important information without seeing it. A short label may be inadequate for a complex process. For recorded media, plan captions and other alternatives appropriate to the content. Captions, transcripts and audio description solve different problems; consider the information carried by speech, sound and visuals rather than treating one file as a universal substitute.

Turn checks into an ongoing improvement plan

Combine automated checks with manual review and research involving people with relevant access needs. Automated tools can identify some issues, but they do not establish that every task is usable. Prioritise barriers that prevent essential actions, while keeping a record of the remaining issues and who owns them.

Before commissioning an audit, agree its scope, the applicable standard and how fixes will be retested. Legal duties depend on the organisation and context; seek qualified advice where needed. Give editors guidance for new headings, links, images and documents, then repeat checks after changes. Accessibility is easier to maintain when responsibility continues after the initial launch.

Further reading

Big idea. Small first step.

What could work
better for your business?

Tell us where you want to go. We’ll help you work out how to get there.

Let’s talk about it