1
00:00:00,000 --> 00:00:07,506
This guide covers Gatekeeper Q A from the command line and in GitHub Actions. We will configure an

2
00:00:07,506 --> 00:00:15,012
explicit page, inspect a failing result, fix a button label, and retrieve a successful retest. Browser captures are

3
00:00:15,012 --> 00:00:23,518
from real runs. Command cards are readable instructions; local result cards summarize retained execution logs. Narration is synthetic.

4
00:00:23,518 --> 00:00:29,225
Use Node J S twenty four with N P M. In a new project directory, initialize package dot

5
00:00:29,225 --> 00:00:34,933
J S O N, install Gatekeeper Q A C L I version zero point three point zero, then

6
00:00:34,933 --> 00:00:40,641
install Playwright Chromium. In an existing project, skip N P M init. The clean GitHub runner installation shown

7
00:00:40,641 --> 00:00:47,349
later also verifies this published package.

8
00:00:47,349 --> 00:00:52,965
Start your application using its normal development command, and wait until its page is available. Save gatekeeper Q

9
00:00:52,965 --> 00:00:58,581
A dot J S O N with the actual U R L. This example uses localhost port three

10
00:00:58,581 --> 00:01:04,198
thousand. Replace that address if your app uses another port. The C L I checks explicit U R

11
00:01:04,198 --> 00:01:10,814
Ls, not a whole-site crawl.

12
00:01:10,814 --> 00:01:16,280
Run the C L I with your configuration and a separate before output directory. Open report dot H

13
00:01:16,280 --> 00:01:21,746
T M L after the command finishes. In our local demonstration, the unnamed button produced a critical button-name

14
00:01:21,746 --> 00:01:27,212
finding and exit code one. The retained transcript records that real result; the equivalent N P X command

15
00:01:27,212 --> 00:01:33,678
is shown here.

16
00:01:33,678 --> 00:01:39,040
The C L I writes H T M L, J S O N, Markdown and J Unit X

17
00:01:39,040 --> 00:01:44,402
M L. It does not directly produce a P D F. Exit zero means the configured gate did

18
00:01:44,402 --> 00:01:49,763
not fail, and can include a warning. Exit one indicates a gate or execution failure. Exit two indicates

19
00:01:49,763 --> 00:01:56,125
setup or configuration trouble. Always read the report.

20
00:01:56,125 --> 00:02:02,560
Give the button meaningful visible text and run the same scope into an after directory. Our local retest

21
00:02:02,560 --> 00:02:08,995
returned pass and exit zero. Preserve the baseline. Reproduce the affected page state and test the interaction manually,

22
00:02:08,995 --> 00:02:16,429
including a screen reader. A passing automated result does not prove the entire experience is accessible.

23
00:02:16,429 --> 00:02:22,405
Copy the downloadable accessibility workflow into dot github slash workflows slash accessibility dot Y A M L in

24
00:02:22,405 --> 00:02:28,380
your repository. Commit it to the default branch so Run workflow is available. The template uses a manual

25
00:02:28,380 --> 00:02:34,356
trigger, read-only repository permission, Node twenty four, the pinned C L I, and seven-day report artifacts. It does

26
00:02:34,356 --> 00:02:41,331
not deploy your application.

27
00:02:41,331 --> 00:02:47,483
Open Actions, select the workflow, and choose Run workflow. Select the branch containing your intended workflow version and

28
00:02:47,483 --> 00:02:53,635
enter an authorized public page. Our recording uses an existing verification workflow on the review branch, with C

29
00:02:53,635 --> 00:02:59,787
L I zero point three point zero. The downloadable template has the same scan and artifact steps, with

30
00:02:59,787 --> 00:03:06,939
a manual trigger.

31
00:03:06,939 --> 00:03:12,033
The first GitHub run failed on the original demonstration page. Expand Scan authorized U R L and Enforce

32
00:03:12,033 --> 00:03:17,127
result to see the result and exit code. Save reports runs before the gate is enforced, so a

33
00:03:17,127 --> 00:03:22,220
failed accessibility result still leaves evidence. Open the artifact on the run summary rather than relying on the

34
00:03:22,220 --> 00:03:28,314
red status alone.

35
00:03:28,314 --> 00:03:34,048
After publishing the button fix, we ran the same workflow and public U R L again. This run

36
00:03:34,048 --> 00:03:39,782
succeeded, with one report artifact. Open the accessibility job for its scan output, then download accessibility reports from

37
00:03:39,782 --> 00:03:45,516
the summary. Extract the archive and open report dot H T M L; retain the machine-readable files for

38
00:03:45,516 --> 00:03:52,250
your tools.

39
00:03:52,250 --> 00:03:57,220
The saved artifact contains the generated report files. Download it before its seven-day retention ends. The runner installed

40
00:03:57,220 --> 00:04:02,189
the public N P M package and Chromium cleanly; the two recorded runs took fifty four and forty

41
00:04:02,189 --> 00:04:07,159
one seconds. Check your own GitHub plan for runner billing. A completed job proves this run, not every

42
00:04:07,159 --> 00:04:13,129
page or state.

43
00:04:13,129 --> 00:04:18,478
For pull-request testing, first build and start the changed application on the runner, or deploy a preview and

44
00:04:18,478 --> 00:04:23,826
wait for it. Point the scan at that changed version. A manual scan of production is not a

45
00:04:23,826 --> 00:04:29,175
pull-request check. Add the appropriate trigger and branch protection deliberately. This guide does not configure a P R

46
00:04:29,175 --> 00:04:35,523
bot or automatic comments.

47
00:04:35,523 --> 00:04:41,858
You now have a repeatable C L I and Actions workflow: explicit scope, a clear gate, report artifacts,

48
00:04:41,858 --> 00:04:48,193
and a separate retest. Use the browser tester guide to record manual observations and compare saved reports. Download

49
00:04:48,193 --> 00:04:54,527
the workflow and read the developer quick start on gatekeeper Q A dot com. Keep human testing part

50
00:04:54,527 --> 00:05:01,862
of every release.