Open-source accessibility testing

Audit the pages that matter.
Remove barriers before release.

Start with one website and choose from the unique pages we find, or enter up to 20 public pages yourself. GitHub Actions runs and reports stay in your repository; local plugin reports stay on your device.

WCAG 2.2 Keyboard Reflow Evidence

Create an audit

Set up your accessibility audit

Setup progress

Stage 1 of 4: add pages
  1. 1Add pages
  2. 2Choose pages
  3. 3Repository
  4. 4Review

Step 1 of 4

Add pages

Let us find pages from one website, or add the exact pages yourself.

How to add pages

Choose the quickest way to build your audit list.

Enter one public https:// address. We check unique HTML pages on that exact website. Job, tag, category, archive, utility, and query pages stay unchecked by default.

One run. One evidence pack.

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.

Claude Desktop

Download

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

Download the current ZIP

Installation note: Claude Desktop accepts its ZIP directly. The local-agent and Copilot archives must be extracted and installed using the linked client instructions. They 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.

Approve the exact pages, choose a repository, and let the builder save and start the managed workflow for you.

  1. Choose your pages

    Discover unique exact-origin pages from one URL, or enter up to 20 public pages yourself.

  2. Choose where it runs

    Connect GitHub and select a repository you control, or create a starter repository first.

  3. Run and review

    Connected setup starts the Action immediately; the manual fallback gives you the workflow to add and run yourself.

Honest by design

All 55 WCAG 2.2 Level A and AA criteria stay accountable.

Every report pairs selective automated evidence with one criterion-specific human procedure and an evidence prompt. Untested, partial, or inconclusive work stays visible and never becomes an automatic pass or certification claim.

Evidence-led browser checks

Chromium runs by default, with optional Firefox and WebKit coverage. Checks include semantics, names, contrast signals, structure, component states, links, 200% text resize, 320px reflow, and configurable keyboard, form, focus, and live-region journeys. Unresolved tool results become review work; bounded checks disclose partial coverage.

Review-ready, trackable outputs

An executive summary and prioritised actions lead the accessible HTML report. Standard A/AA results stay separate from supplemental and optional AAA advice. Consolidated remediation items retain their page, viewport, state, and selector occurrences across Excel, JSON, CSV, SARIF, screenshots, and ZIP exports.

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

Your GitHub account

Choose a repository

Only repositories you selected when installing the CarlasHub GitHub App are shown.

New repository missing? Add it to the GitHub App’s repository access, then refresh this list.

Manage repository access