1 00:00:00,000 --> 00:00:02,786 Welcome to Gatekeeper Q A. This guide shows 2 00:00:02,786 --> 00:00:05,572 a real browser scan, a saved review, a 3 00:00:05,572 --> 00:00:06,269 report export, 4 00:00:06,269 --> 00:00:09,056 and a comparison after a fix. We use 5 00:00:09,056 --> 00:00:11,842 our own demonstration page. These are captured steps 6 00:00:11,842 --> 00:00:12,539 with pauses 7 00:00:12,539 --> 00:00:16,693 shortened, and synthetic narration. Automated checks support human 8 00:00:16,693 --> 00:00:19,808 testing; they do not certify accessibility. 9 00:00:19,808 --> 00:00:21,727 Open scan dot gatekeeper Q A dot com. 10 00:00:21,727 --> 00:00:23,645 Enter one public page you own or have 11 00:00:23,645 --> 00:00:24,125 permission to 12 00:00:24,125 --> 00:00:26,044 test. Our target is slash guide dash demo. 13 00:00:26,044 --> 00:00:27,962 The hosted scanner needs a public address. Use 14 00:00:27,962 --> 00:00:28,442 the developer 15 00:00:28,442 --> 00:00:30,360 C L I for localhost. This recording is 16 00:00:30,360 --> 00:00:32,278 already signed in, so the report can be 17 00:00:32,278 --> 00:00:32,758 retained in 18 00:00:32,758 --> 00:00:38,075 the account. 19 00:00:38,075 --> 00:00:40,612 Confirm the permission checkbox, then choose Run accessibility 20 00:00:40,612 --> 00:00:43,149 scan. Additional page U R Ls are optional 21 00:00:43,149 --> 00:00:43,783 and use 22 00:00:43,783 --> 00:00:46,320 your plan allowance. A scan checks the initially 23 00:00:46,320 --> 00:00:48,857 loaded page, not every linked page or a 24 00:00:48,857 --> 00:00:49,491 signed-in journey. 25 00:00:49,491 --> 00:00:52,027 Wait for the result. If execution is incomplete, 26 00:00:52,027 --> 00:00:54,564 inspect the limitation and retry; do not treat 27 00:00:54,564 --> 00:00:55,198 it as 28 00:00:55,198 --> 00:01:01,906 a pass. 29 00:01:01,906 --> 00:01:04,975 Our first completed scan failed. It found one 30 00:01:04,975 --> 00:01:08,044 critical button-name violation affecting one element, with zero 31 00:01:08,044 --> 00:01:08,811 scan errors. 32 00:01:08,811 --> 00:01:11,880 Open the finding and read why it matters. 33 00:01:11,880 --> 00:01:14,949 A screen-reader user needs to know what the 34 00:01:14,949 --> 00:01:15,716 button does. 35 00:01:15,716 --> 00:01:20,233 A failed accessibility gate is useful evidence, not 36 00:01:20,233 --> 00:01:23,621 a reason to hide the result. 37 00:01:23,621 --> 00:01:26,825 Choose View locations and scan evidence. Here the 38 00:01:26,825 --> 00:01:30,030 selector is checkout, and the captured button has 39 00:01:30,030 --> 00:01:30,831 no text. 40 00:01:30,831 --> 00:01:34,035 Send the rule, location, observed page state and 41 00:01:34,035 --> 00:01:37,240 proposed fix to the developer. For this example, 42 00:01:37,240 --> 00:01:38,041 visible Checkout 43 00:01:38,041 --> 00:01:42,732 text is appropriate. Always verify the meaning of 44 00:01:42,732 --> 00:01:46,251 a label in the actual page. 45 00:01:46,251 --> 00:01:49,207 Find the result under My reports. Rename it 46 00:01:49,207 --> 00:01:52,164 with a useful baseline label, then choose Open 47 00:01:52,164 --> 00:01:52,903 report. Guests 48 00:01:52,903 --> 00:01:55,860 can use Save report and complete sign-in; that 49 00:01:55,860 --> 00:01:58,817 sign-in step is not shown here. Check that 50 00:01:58,817 --> 00:01:59,556 the intended 51 00:01:59,556 --> 00:02:02,957 report appears before leaving the page. Saved reports 52 00:02:02,957 --> 00:02:06,358 have an expiry, so download evidence you need 53 00:02:06,358 --> 00:02:07,208 to retain. 54 00:02:07,208 --> 00:02:10,288 In Saved tester review, select the finding or 55 00:02:10,288 --> 00:02:13,369 manual check. Set a tracking status, enter a 56 00:02:13,369 --> 00:02:14,139 reviewer name, 57 00:02:14,139 --> 00:02:17,219 and describe your test steps and evidence. Choose 58 00:02:17,219 --> 00:02:20,300 Save review. We kept this finding open. Our 59 00:02:20,300 --> 00:02:21,070 first keyboard 60 00:02:21,070 --> 00:02:25,036 attempt did not produce the expected message, and 61 00:02:25,036 --> 00:02:29,002 the note says so. Screen-reader testing remains outstanding. 62 00:02:29,002 --> 00:02:31,443 Choose Open reviewed report slash save P D 63 00:02:31,443 --> 00:02:33,884 F to include saved notes. It opens separately, 64 00:02:33,884 --> 00:02:34,494 so your 65 00:02:34,494 --> 00:02:36,935 working page stays available. Use its Print slash 66 00:02:36,935 --> 00:02:39,376 save as P D F control and your 67 00:02:39,376 --> 00:02:39,986 browser print 68 00:02:39,986 --> 00:02:42,427 dialog. Original downloads remain unchanged. The reviewed J 69 00:02:42,427 --> 00:02:44,868 S O N and review C S V 70 00:02:44,868 --> 00:02:45,478 are separate 71 00:02:45,478 --> 00:02:51,971 ways to retain your notes. 72 00:02:51,971 --> 00:02:55,767 The developer added visible Checkout text and corrected 73 00:02:55,767 --> 00:02:59,564 the demonstration script loading. On the updated page, 74 00:02:59,564 --> 00:03:00,513 the button 75 00:03:00,513 --> 00:03:04,309 now receives focus and Enter displays the no-payment 76 00:03:04,309 --> 00:03:08,106 confirmation. That is one observed interaction, not a 77 00:03:08,106 --> 00:03:09,055 complete manual 78 00:03:09,055 --> 00:03:13,545 assessment. Check keyboard order, visible focus, screen-reader behavior, 79 00:03:13,545 --> 00:03:18,036 zoom and relevant page states for your own 80 00:03:18,036 --> 00:03:18,597 application. 81 00:03:18,597 --> 00:03:21,012 Return to My reports and choose Rescan on 82 00:03:21,012 --> 00:03:23,426 the baseline. Review the U R L and 83 00:03:23,426 --> 00:03:24,030 confirm permission 84 00:03:24,030 --> 00:03:26,445 again. Our fresh scan of the same page 85 00:03:26,445 --> 00:03:28,860 passed. Rename it as the after report. A 86 00:03:28,860 --> 00:03:29,464 pass means 87 00:03:29,464 --> 00:03:31,879 this automated gate found no blocking result in 88 00:03:31,879 --> 00:03:34,293 that scan. It does not establish full W 89 00:03:34,293 --> 00:03:34,897 C A 90 00:03:34,897 --> 00:03:41,331 G conformance. 91 00:03:41,331 --> 00:03:44,400 In Compare reports, select the earlier baseline and 92 00:03:44,400 --> 00:03:47,469 the later retest. Choose Compare findings. Our comparison 93 00:03:47,469 --> 00:03:48,236 shows one 94 00:03:48,236 --> 00:03:51,305 finding no longer detected, zero newly detected, and 95 00:03:51,305 --> 00:03:54,374 zero still detected at the same location. Expand 96 00:03:54,374 --> 00:03:55,141 the result 97 00:03:55,141 --> 00:03:59,357 and verify it manually before closing the issue. 98 00:03:59,357 --> 00:04:03,046 Preserve both reports and your review evidence. 99 00:04:03,046 --> 00:04:06,966 Use the same loop on each authorized page: 100 00:04:06,966 --> 00:04:10,886 scan, inspect evidence, record manual observations, make a 101 00:04:10,886 --> 00:04:11,866 fix, and 102 00:04:11,866 --> 00:04:15,786 retest the same scope. Keep incomplete results and 103 00:04:15,786 --> 00:04:19,707 unreviewed checks visible. The developer guide covers local 104 00:04:19,707 --> 00:04:20,687 commands and 105 00:04:20,687 --> 00:04:25,597 GitHub Actions. Visit the testing guide on gatekeeper 106 00:04:25,597 --> 00:04:30,508 Q A dot com for the written workflow.