Turn a scan finding into a focused manual test

Start with one affected element

Open a finding and review its explanation, rule reference, and affected elements. Use the extension highlight to locate the element on the page. Check the surrounding context: a selector or short snippet helps you find the issue, but the visible page and its behavior determine whether the report applies.

Reproduce the user impact

For a keyboard issue, reload the page and use Tab, Shift+Tab, Enter, Space, and arrow keys where appropriate. Check that focus is visible, stays in a logical order, and is not trapped. For a form issue, submit empty and invalid values and inspect where errors appear and whether they are announced and associated with the relevant fields.

Use assistive technology for the relevant task

Read the page with the screen reader available on your platform and try the task a user needs to complete. Check names, roles, state changes, landmarks, headings, and error announcements. The extension’s reading-order and read-aloud controls can help inspect page structure, but they are not a substitute for a screen reader.

Make and verify a small change

Fix the underlying markup or interaction, then repeat the same steps. Re-run the scan and confirm the original element is no longer reported. Also check nearby states: an accessible default view can still fail after opening a menu, submitting a form, or loading new results.

Record what was actually tested

Note the page, browser, input method, assistive technology, steps, and outcome. Separate automated evidence from manual observations. A clean scan is useful evidence, but it does not establish WCAG conformance by itself.