Record the starting conditions.
Note the page, task, browser and relevant assistive technology. Describe expected behavior in plain language, such as opening and closing an inquiry dialog.
Diagnostic guide
Find the step where the keyboard path breaks.
Use a safe task and stop before an action would send a message, place an order or change live records.
Reviewed October 16, 2026 ยท Faith Forge Labs
Follow the focus.
Record which keys reach the relevant control and whether its focused state can be seen. Note skipped controls, unexpected jumps or a point where focus becomes trapped.
Check feedback and recovery.
In a fictional form test, leave a required field blank. Can the user find the error, return to the field and understand the result after correction? A visible red border alone does not explain the problem to every user.
Write a reproducible finding.
Include steps, the observed result, the expected result and the effect on completion. Keep private form values out of the report. A screenshot can help explain appearance but does not capture the whole keyboard interaction.
Retest after the repair.
Repeat the complete path and a nearby failure case. Record the conditions checked and anything still unresolved. This first review is not a complete conformance evaluation.