Just shippedOur pick for the best security, implementation, and planning skills.Best skills for each job.See the picks →
Runs daily. The agent checks your web app against WCAG 2.2 accessibility guidelines and reports the problems it finds.
schedule: daily + workflow_dispatch
How it works
Setup
.github/workflows/agentics-accessibility-review.md (markdown, not a .yml file).gh aw compile. Actions runs the compiled file at .github/workflows/agentics-accessibility-review.lock.yml.Let your agent do it
Paste it into your coding agent in this repo. It does the setup and asks before anything leaves your machine.
Runs the same job in your agent session, on the plan you are signed in with. No API key, no Action.
Do the job of the "Accessibility review of web UI changes" workflow from AgentFlows (https://agentflows.sh/flows/agentics-accessibility-review) right here, in this session, using the plan I'm signed in with. No API key and no GitHub Action. What it does: Runs daily. The agent checks your web app against WCAG 2.2 accessibility guidelines and reports the problems it finds. The workflow normally runs on: schedule: daily + workflow_dispatch. Instead, ask me which pull request, issue, or branch to work on, then follow these instructions: ```text # Accessibility Review Your name is Accessibility Review. Your job is to review a website for accessibility best practices. If you discover any accessibility problems, you should file GitHub issue(s) with details. Our team uses the Web Content Accessibility Guidelines (WCAG) 2.2. You may refer to these as necessary by browsing to https://www.w3.org/TR/WCAG22/ using the WebFetch tool. You may also search the internet using WebSearch if you need additional information about WCAG 2.2. The code of the application has been checked out to the current working directory. Steps: 0. Read the markdown corresponding to the workflow file under `.github/workflows/accessibility-review.md`. If the section "Build and run app in background" already contains actual commands, then go to the next step. If it still contains a placeholder, then: a. Work how to replace it with the actual commands to set up the runtime, install dependencies, build the project and run it in the background, e.g., using `&` at the end of the command. b. Don't actually make the changes (since you're not allowed to make changes under .github/workflows), but rather create a discussion showing the exact changes that are needed to the workflow file. Do this by using a markdown codeblock to copy-and-paste into the file, plus a deep link to GitHub to the range of the file to replace. c. In the discussion body mention that the user must (1) make these changes manually and (2) then run "gh aw compile" to compile the workflow file using GitHub Agentic Workflows (https://github.com/github/gh-aw). d. Also instruct them to remove this section from the markdown. e. Exit the workflow with a message saying that the workflow file needs to be updated. 1. Use the Playwright MCP tool to browse to `localhost:3000`. Review the website for accessibility problems by navigating around, clicking links, pressing keys, taking snapshots and/or screenshots to review, etc. using the appropriate Playwright MCP commands. 2. Review the source code of the application to look for accessibility issues in the code. Use the Grep, LS, Read, etc. tools. 3. Use the GitHub MCP tool to create discussions for any accessibility problems you find. Each discussion should include: - A clear description of the problem - References to the appropriate section(s) of WCAG 2.2 that are violated - Any relevant code snippets that illustrate the issue ``` Use the gh CLI for anything on GitHub, and show me what you plan to post or change before you do it.
The file
Copy the file as-is. The notes beside each block explain it.
.github/workflows/agentics-accessibility-review.md
File
gh-aw source. Paste it as markdown, then compile. It is not a finished Actions YAML file.
---description: | This workflow is an automated accessibility compliance checker for web applications. Reviews websites against WCAG 2.2 guidelines using Playwright browser automation. Identifies accessibility issues and creates GitHub discussions or issues with detailed findings and remediation recommendations. Helps maintain accessibility standards continuously throughout the development cycle.Trigger
GitHub starts a run when the schedule in this block is due, or you run it by hand.
on: schedule: daily workflow_dispatch:Permissions
This token may network: defaults. Anything not listed is not granted.
permissions: read-allnetwork: defaultsWhat you get
What the agent is allowed to write back: mentions, allowed-github-references, create-discussion, add-comment, playwright, web-fetch, github. gh-aw blocks other writes.
safe-outputs: mentions: false allowed-github-references: [] create-discussion: title-prefix: "[accessibility-review] " category: "q-a" max: 5 add-comment: max: 5tools: playwright: web-fetch: github: toolsets: [all]timeout-minutes: 15Steps
These steps run in order on that job.
steps: - name: Checkout repository uses: actions/checkout@v4 with: fetch-depth: 0 persist-credentials: false - name: Build and run app in background run: | # This step should set up the runtime environment for your app, # including installing any necessary dependencies, and it should # start your app in the background (e.g., using `&` at the end of the command). echo "Building and running the app in background..."---# Accessibility ReviewYour name is Accessibility Review. Your job is to review a website for accessibility bestpractices. If you discover any accessibility problems, you should file GitHub issue(s) with details.Our team uses the Web Content Accessibility Guidelines (WCAG) 2.2. You may refer to these as necessary by browsing to https://www.w3.org/TR/WCAG22/ usingthe WebFetch tool. You may also search the internet using WebSearch if you needadditional information about WCAG 2.2.The code of the application has been checked out to the current working directory.Steps:0. Read the markdown corresponding to the workflow file under `.github/workflows/accessibility-review.md`. If the section "Build and run app in background" already contains actual commands, then go to the next step. If it still contains a placeholder, then: a. Work how to replace it with the actual commands to set up the runtime, install dependencies, build the project and run it in the background, e.g., using `&` at the end of the command. b. Don't actually make the changes (since you're not allowed to make changes under .github/workflows), but rather create a discussion showing the exact changes that are needed to the workflow file. Do this by using a markdown codeblock to copy-and-paste into the file, plus a deep link to GitHub to the range of the file to replace. c. In the discussion body mention that the user must (1) make these changes manually and (2) then run "gh aw compile" to compile the workflow file using GitHub Agentic Workflows (https://github.com/github/gh-aw). d. Also instruct them to remove this section from the markdown. e. Exit the workflow with a message saying that the workflow file needs to be updated.1. Use the Playwright MCP tool to browse to `localhost:3000`. Review the website for accessibility problems by navigating around, clicking links, pressing keys, taking snapshots and/or screenshots to review, etc. using the appropriate Playwright MCP commands.2. Review the source code of the application to look for accessibility issues in the code. Use the Grep, LS, Read, etc. tools.3. Use the GitHub MCP tool to create discussions for any accessibility problems you find. Each discussion should include: - A clear description of the problem - References to the appropriate section(s) of WCAG 2.2 that are violated - Any relevant code snippets that illustrate the issueKeep going
gh-aw source is Markdown + YAML frontmatter compiled with `gh aw compile` to a .lock.yml. Writes go through `safe-outputs`.
issues: opened
Est. cost per run~$0.02 runner + engine tokens/credits (UNVERIFIED)Checked Oct 16, 2026
Not executed· 2 caveats`label_command` removes the label after activation by default (`remove_label: true`).
label_command: ai-review
Est. cost per run~$0.03 runner + engine tokens/credits (UNVERIFIED)Checked Oct 16, 2026
Not executed· 1 caveatTrimmed from gh-aw's own .github/workflows/ci-coach.md (removed imports, experiments, AI-credit caps).
schedule: daily + workflow_dispatch
Est. cost per run~$0.12 runner + engine tokens/credits (UNVERIFIED)Checked Oct 16, 2026
Not executed· 1 caveat