How AccessStamp works

Two parts: a web scan you can use today, and an Android build plugin in development.

Live now: the free web scan

You give it one public HTTPS page. It loads the page in a browser, runs the axe-core engine with WCAG 2.0, 2.1 and 2.2 level A and AA rules, and returns findings grouped by rule. Items the engine cannot decide are listed separately as needing manual review.

The report records the time, the engine version, the viewport and the scope. It is shown on the page. Try it.

In development: the Android build plugin

The plan is a Gradle plugin for Android projects. You add it once, run one command in CI, and get a dated report on every build.

Developer preview 0.1.0, source for pilot teams only

A first version exists and is tested on a fixture project. Its runtime checks have not been run on a device yet. See the integration steps for exactly what it does and does not do.

  • Static checks on layouts and Jetpack Compose source, such as missing content descriptions and small touch targets.
  • Runtime checks that run Google's Accessibility Test Framework through the UI tests you already have. These cover only the screens your tests visit.
  • A dated HTML report that maps issues to WCAG criteria, plus JSON or SARIF output for tooling.
  • A coverage ledger of tested and untested screens, and a release evidence bundle with build hash, timestamp, tested journeys, findings, waiver history and explicit unknowns.
  • A baseline so builds fail only on new issues, similar to lint.

Scope and order may change as we learn from pilot teams. Web dashboard, iOS support and automatic screen crawling are not part of the first version.

What automated checks cannot do

Automated checks only cover the rules they implement and the screens they run on. They cannot judge whether alt text is meaningful, whether reading order makes sense, or whether a flow works with a screen reader. Keep manual testing and user feedback in your process.

No certification. AccessStamp does not certify compliance with the European Accessibility Act, WCAG or EN 301 549. It gives you evidence of checks you ran.

Why dated evidence

When a customer, auditor or regulator asks what you do about accessibility, a record of regular checks with dates and scope is more useful than a statement of intent. It does not prove compliance. It shows a process.

See the founding pilot