For testers: scan, review and retest
4:31 · narrated screen captures · English captions
Tester guide: scan, review and retest
Welcome to Gatekeeper Q A. This guide shows a real browser scan, a saved review, a report export, and a comparison after a fix. We use our own demonstration page. These are captured steps with pauses shortened, and synthetic narration. Automated checks support human testing; they do not certify accessibility.
1. Enter an authorized public page
Open scan dot gatekeeper Q A dot com. Enter one public page you own or have permission to test. Our target is slash guide dash demo. The hosted scanner needs a public address. Use the developer C L I for localhost. This recording is already signed in, so the report can be retained in the account.
2. Confirm permission and run
Confirm the permission checkbox, then choose Run accessibility scan. Additional page U R Ls are optional and use your plan allowance. A scan checks the initially loaded page, not every linked page or a signed-in journey. Wait for the result. If execution is incomplete, inspect the limitation and retry; do not treat it as a pass.
3. Read the result before making changes
Our first completed scan failed. It found one critical button-name violation affecting one element, with zero scan errors. Open the finding and read why it matters. A screen-reader user needs to know what the button does. A failed accessibility gate is useful evidence, not a reason to hide the result.
4. Expand the element evidence
Choose View locations and scan evidence. Here the selector is checkout, and the captured button has no text. Send the rule, location, observed page state and proposed fix to the developer. For this example, visible Checkout text is appropriate. Always verify the meaning of a label in the actual page.
5. Save and open your report
Find the result under My reports. Rename it with a useful baseline label, then choose Open report. Guests can use Save report and complete sign-in; that sign-in step is not shown here. Check that the intended report appears before leaving the page. Saved reports have an expiry, so download evidence you need to retain.
My reports Rename: Tutorial — before button fix Open report Saved tester review Choose the finding or manual check
6. Record what you actually tested
In Saved tester review, select the finding or manual check. Set a tracking status, enter a reviewer name, and describe your test steps and evidence. Choose Save review. We kept this finding open. Our first keyboard attempt did not produce the expected message, and the note says so. Screen-reader testing remains outstanding.
7. Export the right copy
Choose Open reviewed report slash save P D F to include saved notes. It opens separately, so your working page stays available. Use its Print slash save as P D F control and your browser print dialog. Original downloads remain unchanged. The reviewed J S O N and review C S V are separate ways to retain your notes.
8. Fix the page and check its behavior
The developer added visible Checkout text and corrected the demonstration script loading. On the updated page, the button now receives focus and Enter displays the no-payment confirmation. That is one observed interaction, not a complete manual assessment. Check keyboard order, visible focus, screen-reader behavior, zoom and relevant page states for your own application.
9. Rescan the same scope
Return to My reports and choose Rescan on the baseline. Review the U R L and confirm permission again. Our fresh scan of the same page passed. Rename it as the after report. A pass means this automated gate found no blocking result in that scan. It does not establish full W C A G conformance.
10. Compare, then verify
In Compare reports, select the earlier baseline and the later retest. Choose Compare findings. Our comparison shows one finding no longer detected, zero newly detected, and zero still detected at the same location. Expand the result and verify it manually before closing the issue. Preserve both reports and your review evidence.
Your repeatable testing loop
Use the same loop on each authorized page: scan, inspect evidence, record manual observations, make a fix, and retest the same scope. Keep incomplete results and unreviewed checks visible. The developer guide covers local commands and GitHub Actions. Visit the testing guide on gatekeeper Q A dot com for the written workflow.
SCAN → REVIEW → FIX → RETEST Keep the same page scope. Record observations, not assumptions. Export evidence before expiry. PASS is not an accessibility certification.