How to test website accessibility
By Adrian Diaz
Start with real tasks
Choose the journeys that matter: find a service, read a page, submit an enquiry, or complete a purchase. Test each journey as a visitor would, including error and success states. Record the page, browser, device, steps, expected result, and actual result for each issue. Prioritize barriers that prevent a person from completing a task before cosmetic refinements.
Use the keyboard
Unplug or set aside the mouse. Use Tab and Shift+Tab to move through controls, Enter to activate links, and Space where appropriate for buttons and checkboxes. Check that focus is visible, follows a logical order, and does not become trapped. If a dialog opens, confirm that you can reach its controls, close it, and return to the place you came from.
Review structure and labels
Check that each page has a clear main heading and that subheadings describe the sections beneath them. Links should make sense in context. Every form field needs an associated label, and errors should identify the field and explain what to fix. Informative images need useful alternatives; purely decorative images should not add noise to a screen reader.
Check contrast and motion
Use a contrast checker on text, controls, and focus indicators against their actual backgrounds. Examine text over images as well as solid colors. Zoom the browser and check that content reflows without hiding the primary task. Test reduced-motion settings and make sure animation does not prevent reading or navigation.
Use tools and assistive technology
Run an automated accessibility scanner on representative pages and states, including open menus and form errors. Treat its results as a starting point rather than a complete audit. If possible, test important journeys with a screen reader and include people with relevant lived experience in testing. Capture what you observe instead of assuming how every person uses assistive technology.
Fix, retest, and maintain
Address issues at their source, then repeat the original task to confirm the barrier is gone. Check that the fix has not introduced a new problem elsewhere. Include accessibility checks in content updates, component changes, and launch reviews. Keep a short record of known issues, owners, and retest dates so improvements remain visible to the team.
Create a useful issue report
A report should let another person reproduce the barrier without guessing. Include the page address, the task, the browser and device, and the exact steps that led to the problem. Describe what happened and what the person needed to happen instead. A short screen recording can help, but it should supplement a written description rather than replace it.
Group related findings by the underlying component where possible. For example, the same missing focus style may affect several forms. Fixing a shared component can resolve multiple instances, but each affected journey still needs a retest. Record the date of the retest and whether the issue is fixed, partly fixed, or still open.
Test a form from start to finish
Choose an important form and approach it as a complete task. Start at the preceding page, navigate to the form by keyboard, and move through every field. Check that each label identifies its control and that the order of focus matches the visual and logical order. Submit the form with missing information, then use the error messages to correct it.
The error should tell a person what needs attention without relying on color alone. Check that the message can be found when navigating by keyboard and, if you use a screen reader, that the relationship between the field and its error is understandable. Submit valid test information and verify that the success state is distinguishable from an error. Confirm the receiving inbox or system has the test submission.
Repeat the task at a larger zoom level and on a small screen. Look for text that is clipped, controls that overlap, and instructions that disappear. Document a barrier with the exact steps needed to reproduce it, then repeat those steps after a fix. A passing automated scan is useful evidence but cannot establish that this complete journey is usable.
Prioritize by impact
A barrier that stops a person completing a purchase or enquiry generally deserves attention before a minor visual inconsistency. Consider how many journeys use the affected component, whether there is a workable alternative, and whether the issue prevents access entirely. Record the reason for the priority so the team can revisit it when circumstances change.
Accessibility is an ongoing practice. New copy, images, embeds, and third-party controls can introduce barriers even when the original template was checked. Give content editors guidance on headings, meaningful link text, image alternatives, and form labels, and include those checks in routine publishing.
Put the guidance into practice
Start with the page or workflow that matters most to the people using the site. Write down the current behavior, the change you intend to make, and the person responsible for reviewing it. If the site has a staging environment, test the change there before applying it publicly. Keep a record of the previous configuration and make sure the team knows how to restore it if the change causes a problem.
After the change, repeat the original task with realistic content. Check it on a small screen and with a keyboard, and include any form, payment, or integration that the change could affect. Record the date, result, and any follow-up. Share the outcome with the site owner in terms of what visitors can now do and what remains uncertain. Revisit the check when the underlying content, theme, or connected tools change.
Explore related services.