IN THIS GUIDE
- 01Use semantic structure
- 02Make every action work without a mouse
- 03Write and design for readability
Use semantic structure
Headings, landmarks, lists, buttons and links should describe the role of the content. Correct HTML gives assistive technology useful information and usually makes the page easier to maintain, navigate and index.
Make every action work without a mouse
A person should be able to reach navigation, menus, forms and interactive controls with a keyboard, see where focus is and understand the result of an action. Focus order should follow the meaning of the page.
Write and design for readability
Use clear headings, direct language, sufficient contrast and layouts that remain usable when text is enlarged or the screen becomes narrow. Alternative text should communicate the purpose of meaningful images rather than repeat nearby copy.
Build forms around completion
Give every field a persistent label, explain required formats and connect errors to the field that needs attention. Ask only for information the process needs. Confirmation and failure states should be announced clearly and provide a way forward.
Combine automated and human testing
Automated checks find some technical problems. They cannot tell you whether a person can finish a task. Test common tasks with a keyboard, screen reader and zoom, and involve people with different access needs where possible.
Make accessibility part of change control
Content edits, new integrations and redesigns can introduce barriers after launch. Include keyboard, zoom, contrast, labels and error handling in the acceptance checks for ongoing website work.
USE THIS IN PRACTICE
A practical website accessibility review
- 01
Page structure and headings describe the content.
- 02
Navigation and controls work with a keyboard.
- 03
Focus is visible and follows a sensible order.
- 04
Text and interface elements have sufficient contrast.
- 05
Meaningful images have useful alternatives.
- 06
Forms have labels, instructions and recoverable errors.
- 07
Pages remain usable on narrow screens and at increased zoom.
Common questions
Is an automated accessibility score enough?
No. Automated tools find only some issues. Manual task testing and testing with people provide evidence that a score cannot.
Which standard should a business review?
WCAG 2.2 is the current W3C Recommendation. The applicable contractual or legal requirement depends on the organisation and should be confirmed separately.
EXPLORE THE SOURCE
EXPLORE THE RELATED CAPABILITY
Websites & ecommerce
Business websites, ecommerce stores and the integrations that connect online activity to the work behind it.
Explore Websites & ecommerce