What does FastPass check while you use the page?
FastPass runs automated checks and offers a visual aid for the sequence reached by Tab. Run the scan for detectable problems, then use the keyboard and see whether each useful control is reached in a sensible order.
Some results need human review. The separate Assessment mode offers a longer set of guided checks based on WCAG 2.1 AA. Choose the scope you need and record the pages and states you actually checked.
What goes in a report you can hand to a teammate?
Export the FastPass result or copy the details of a failure. Include which page state you used and the first step where the keyboard could not reach a control. Review what the report contains before sharing it.
Use the MIT-licensed Web extension in Chrome or Edge. Check its usage and crash-report settings before using it on a private test page. The Windows desktop product is a separate tool in the same family.
How can you check that a button can be reached without a mouse?
Use a standalone sample with a Search field and a Clear button that only clears fictional input. Use no connected services. If you cannot install the extension, write the expected sequence and mark the extension run as pending.
- Start with the intended pathFocus the sample, press Tab and note where the outline goes. Check that Search and Clear are both reachable. Use Shift+Tab to check the return path.
- Compare with Tab stopsTurn on the visual aid and repeat from the same page state. If it highlights a possible failure, confirm it with the keyboard yourself.
- Record what needs fixingIf Clear is skipped, record the last control reached and the next one. After a fix, repeat the same sequence and save the result you actually observed.