Open-source accessibility testing

Audit every page.
Remove barriers before release.

Add up to 20 public pages. Create a ready-to-run repository or add the audit to one you already own. Every run and report stays under your account.

WCAG 2.2 Keyboard Reflow Evidence

Create an audit

Which pages do you want to audit?

Setup progress

Stage 1 of 4: add pages

Pages to audit

Use complete public https:// addresses. Add up to 20 pages for one combined audit.

Page 1 URL

1 of 20 pages

Where should the audit run?

Choose a new audit repository or add one workflow to a repository you can edit.

Create a new repositoryGitHub opens a prefilled copy of the free starter template. Use an existing repositoryGitHub opens a prepared workflow for you to review and commit.

The optional connector only authorises the repository change and starts the workflow. It never runs audits or stores reports. All Actions usage, audit history, and reports belong to you—not CarlasHub. Manual setup remains available.

Checkpoint reached

Your workflow file is ready

The workflow is configured for your pages.

1
Copy the workflow
Use the button below to copy the generated file.
2
Add one file
In your repository, create .github/workflows/accessibility-audit.yml and paste.
3
Run the audit
Open Actions → Accessibility audit → Run workflow.
4
Get the evidence
Download the combined report from the run summary.

Open starter repository

Preview the workflow file

One run. One evidence pack.

Accessible HTML
Excel workbook
JSON data
Screenshots
ZIP archive

Use it where you work

One audit engine. Six ways to run it.

Choose a ready-to-use option or install the open-source developer package in your preferred coding assistant. Every card states what is available today.

GitHub Actions

Ready

Create your own audit repository from the ready template, or add a prepared workflow to an existing project. Runs and reports stay in your GitHub account.

Set up GitHub Actions

Claude Desktop

Download

Upload the packaged custom-plugin ZIP in Customize → Plugins. Keep the ZIP compressed.

Download v1.3.1 ZIP

Claude Code

Developer install

Clone and build the plugin once, then load that checkout in the project you want to audit.

npm ci && npm run build
claude --plugin-dir /path/to/accessibility-audit-plugin

Claude Code instructions

Cursor

Developer install

The repository includes Cursor’s plugin manifest, command, rule, skill, and MCP configuration. Build it, add it to Cursor’s local plugin directory, then reload.

Cursor instructions

Codex CLI

Package ready

The repository includes the portable Agent Plugin manifest, Codex fallback manifest, marketplace catalog, skill, and MCP server. Install from a configured marketplace, then open the CLI plugin browser.

/plugins

Codex instructions

GitHub Copilot

Package ready

Build the included Copilot CLI or VS Code payload locally. Public marketplace listing is a separate submission step.

npm run build:marketplace
copilot plugin install ./marketplace/carlashub-plugin-marketplace/accessibility-audit/copilot-cli

Copilot instructions

Developer-install note: local agent integrations require Node.js 22 or later and a Playwright-supported browser. The Codex IDE extension does not currently support plugins. Only audit websites you are authorised to test.

A shorter setup

From a page list to useful evidence.

Choose a new or existing repository, confirm the workflow on GitHub, then rerun it whenever your site changes.

Add your pages
Enter one or several public pages that you are authorised to test.
Choose where it runs
Create a repository from the template or add the prepared workflow to one you already use.
Run and review
Start the Action and download one combined evidence pack for every page.

Honest by design

All 55 WCAG 2.2 Level A and AA criteria are accounted for.

Every report pairs automated evidence with one criterion-specific human procedure and an evidence prompt. Untested or inconclusive criteria stay visible and never become automatic passes.

Evidence-led browser checks

Semantics, accessible names, contrast signals, structure, component states, links, independent 200% text resize and 320px reflow, plus configurable keyboard, form, focus, and live-region journeys.

Review-ready outputs

Structured findings, screenshots, an accessible HTML report, and a native Excel workbook stay together.

Human decisions remain explicit

No automated tool can certify WCAG conformance. Screen-reader experience, meaning, usability, and exceptions still require qualified review.

Built in public

Inspect it. Improve it. Use it.

The Action and its test methodology are open source under the MIT licence.

Explore the GitHub project

Audit every page.Remove barriers before release.