What a manual accessibility audit catches that a scanner misses
Use a scan to find clues. Then take a customer task through its menus, errors and confirmation screens.
A scan of a bakery's ordering page may find that every field has a label. That same form can still leave you guessing which of two "Date" fields means pickup day. Try the order yourself and it becomes clear what the label needs to say.
Start with a page a customer actually depends on. Choose an order or inquiry you can complete using test information. Keep a scan report and notes from the task together so you can see what each method found.
Run a scan on a short list of pages
Pick your main service page and the first page of the transaction it starts. Include the page that tells a customer how to reach you. The W3C guide to evaluating web accessibility recommends using evaluation tools as part of a wider review. A tool can flag issues its rules know how to detect. W3C says a human evaluation is still needed.
Read a finding before opening a ticket. Check what element the tool points to and what was on screen. If the alert is about one shared menu, try the menu on another page. That helps you describe one repair for the menu template instead of assigning one ticket for every copy of the same bar.
A report should point to the state in which a result was found. A scan of the closed menu and a check of that menu after it opens are different parts of the job.

Listen to a label in context
Suppose there are two buttons named "Select." One applies to a two-person class. One applies to a private lesson. Find them using a list of controls in a screen reader. Ask whether you can tell which option you are choosing when you encounter the button.
The W3C guide to accessible forms explains how to identify controls with meaningful labels. Try renaming the two buttons with the session names and listen again. Check the surrounding text too. If the name of the lesson is already part of the button's accessible name, a repeated phrase might make the choice harder to follow.
Write the URL where the task starts and make a separate note of every screen that loads after a choice.
Walk into the awkward states
Open the mobile menu, choose a service, and then back out of a dialog. Look for where the keyboard focus goes after each step. Repeat with an empty form or a date that has no available times. Use W3C first review checklist as a starting point for checks such as focus, headings and form labels.
Write down the sequence that produced a problem. A screenshot of a calendar with no options can help, but also write the date and service you chose. If the experience depends on a certain staff member or location, put that in the steps. Your teammate should be able to bring up the same screen without asking you to do it again.
Match the finding to what the visitor needs
A tiny typo and a checkout trap belong in the same record with different priorities. Ask what happens to the transaction. If the checkout trap blocks keyboard use and there is no other online route, put the repair near the top. Attach the test that shows where the customer gets stuck.
Use one issue to describe one barrier. Write down the expected result in plain language. "After closing the date picker, focus returns to the date field" is something a tester can verify. Invite a tester who uses assistive technology to try tasks in their usual setup. W3C guide to involving users in evaluation explains how user evaluation fits alongside checks against a standard.
Keep the wording of the error if the problem appears on an unavailable date or during a failed submission.

Compare findings after the fix
Rerun the scan on the affected page. Find the original issue and see whether the tool reports it again. Then repeat the manual route with the same starting conditions. If you fixed a broken dialog, open and close it more than once. Try reopening it after an error so you can see whether that path works too.
Keep the original result, the repair and the retest date in one place. It is useful to say which browser and input you used. A short record may read "closed with Escape, returned to date field, continued to confirmation." That gives the next tester a result they can act on.
Decide what each review covers
List the pages, templates and tasks you checked. Include anything outside that sample, such as an account screen or a third-party payment step, in an open queue. The W3C guide to evaluating web accessibility links to methods for planning and documenting a more formal evaluation.
Before the next site update, ask the editor to run one scan and one manual task on the part they changed. For a content update, try reading the new heading or image description in context. For a booking update, start at the public link and follow the entire sequence. Add a dated note so the next person can see what you covered.
Have someone else follow the steps from a clean browser and check whether they reach the same result.
Access Heroes may earn a commission if you buy a tool we recommend. You pay the tool's maker directly, and we always tell you before you sign up. This article is general information, not legal or tax advice.
Sources
Bring an automated report or a page that worries you. TJ can help you pick a manual test to run alongside it.




Comments