Start with a clear page structure
Headings should describe the content beneath them and follow a sensible order. Visitors using a screen reader often navigate by headings, while everybody benefits from being able to scan a page quickly.
Keep navigation labels familiar, place important actions where people expect them and avoid making visitors decode clever wording before they can continue.
- Use one clear page title
- Keep heading levels in a logical order
- Write descriptive link text
- Make important services easy to find
Make everything work without a mouse
Some visitors navigate with a keyboard, switch device or other assistive technology. Every link, button, menu and form control should be reachable and usable without requiring precise pointer movement.
A visible focus indicator is essential because it shows which element will respond when the visitor presses Enter or Space.
Check colour, contrast and text size
Text needs enough contrast against its background, including text placed over photographs. Colour should not be the only way an error, status or category is communicated.
Visitors should also be able to enlarge text without losing content or being forced to scroll sideways. Testing at 200% zoom is a useful practical check.
Describe images and provide alternatives
Meaningful images need concise alternative text that communicates their purpose. Decorative images should be ignored by assistive technology so they do not create unnecessary noise.
Videos should include captions, and audio information should have a written alternative. Automated captions are a useful starting point but should still be reviewed for accuracy.
Make forms forgiving and understandable
Every field needs a visible label. Required information should be explained before submission, and error messages should identify both the problem and how to correct it.
Avoid short time limits where possible. People may need additional time to read instructions, find information or use assistive technology.
Accessibility tools can help, but they are not the whole answer
Features such as an inline screen reader, contrast controls or text resizing can be useful additions for particular audiences. Hear for Norfolk, for example, provides visible accessibility options and a Listen function on its website.
These tools work best alongside accessible code, clear content and thoughtful design. A toolbar cannot repair an inaccessible underlying page on its own.
Test with real tasks, not only automated scores
Automated accessibility tools are valuable for finding technical issues, but they cannot decide whether instructions make sense or whether a booking journey feels manageable.
Try completing the website’s important tasks with a keyboard, at high zoom and on a small screen. Where possible, include people with lived experience in testing and respond to the feedback they provide.
