Founding pilot open
Dated accessibility evidence for your Android app
AccessStamp checks for accessibility issues and records what was checked and when. Built for teams that sell to EU consumers under the European Accessibility Act. It shows the work, it does not certify it.
In validation. The free web scan is live. The Android build plugin is in development.
What exists today
A plain status list, so you know what you can use now and what is still being built.
| Part | Status | What that means |
|---|---|---|
| Free web scan | Live | Checks one public web page with the axe-core engine against WCAG 2.0 to 2.2 level A and AA rules. Run it. |
| Android Gradle plugin | Developer preview | Version 0.1.0 source. Scans XML and Compose source for a few review-candidate patterns and writes HTML and JSON reports. Tested on a fixture project. Runtime checks have not been run on a device. Integration steps. |
| Evidence bundle, SARIF, report history | Planned | Not built yet. Scope may change with pilot feedback. |
Why this exists
The European Accessibility Act applies to many consumer apps and sites sold in the EU. Auditors and customers ask what you checked. Most teams cannot answer with a dated record.
Find issues early
Automated checks flag missing labels, weak contrast and other common problems before they ship.
Keep a dated record
Each run records the date, the rules applied and the engine version, so you can show what was checked and when.
Your developers fix
Reports point to the element and the rule. AccessStamp does not rewrite your code or promise a fix.
How it works
Same idea for the web preview today and the Android plugin we are building.
Point it at your product
Today: paste a public page URL. Planned for Android: add one Gradle plugin line to your project.
Run the automated checks
Rules map to WCAG success criteria, the standard the European Accessibility Act points to through EN 301 549.
Get a dated report
Findings, items for manual review, and the limits of the check, written down in one report.
What it does, and what it does not
It does
- Run automated WCAG A and AA rule checks
- List affected elements and link to rule guidance
- Separate confirmed findings from items needing manual review
- Record date, engine and scope in every report
It does not
- Certify compliance with any law or standard
- Replace keyboard, screen reader and user testing
- Find every issue. It reports only what it tested
- Give legal advice
What we are building, and how it differs
Accessibility testing tools for Android exist, and several are sold through sales teams to large companies. AccessStamp is aimed at small and mid-size Android teams who want to start without a sales call.
Self-serve, Android-first
Published prices per project, from EUR 29 a month in our plan. Add the Gradle plugin and run it. No sales call.
Release evidence bundle
One Gradle command writes a bundle: build hash, timestamp, tested journeys, findings, waiver history and explicit unknowns. It is preparation for expert review, not certification.
Coverage ledger
A list of the screens and flows that were tested, and the ones that were not, so a clean report is never mistaken for full coverage.
Precise findings
Each finding names the element, the rule and a suggested fix, in a readable HTML report and a machine-readable JSON or SARIF file.
New-issues-only CI gates
A baseline lets builds fail only on newly introduced issues, like lint, so adoption does not start with a wall of old findings.
Local-first
Checks run in your own build and CI. The aim is that your app code and screens do not need to be uploaded to a third party.
All items above are planned for the Android plugin, which is in development. Only the free web scan is live today.
Questions
Does AccessStamp make my app compliant with the European Accessibility Act?
No. AccessStamp finds a subset of accessibility issues automatically and records dated evidence of what was checked. Automated checks cover only the rules and screens they test. Compliance depends on your whole product, manual testing and your legal assessment. We never issue a compliance certificate.
What is live today?
The free web scan. It checks one public web page with the axe-core engine against WCAG 2.0 to 2.2 level A and AA rules. The Android build plugin is in development and is not available yet.
What is the founding pilot?
A pre-purchase for early access to the Android build plugin while it is being built, at EUR 299. You help shape what it checks and how reports look. It is early-stage software, so it suits teams that are comfortable with that.
Is the web scan the same as the Android plugin?
No. The web scan checks one rendered web page. The Android plugin is a separate product that will check Android apps during your build. The web scan is a free preview of the kind of report you would get.
Do you store the pages I scan?
The scan runs on request and the report is shown on the page, with a PDF download. We do not keep a database of reports. See the privacy page for details.
Who should buy this?
Android teams at banks, e-commerce companies, e-book publishers and transport companies that sell to EU consumers and need to show they check accessibility regularly.
Try the free web scan
Paste a public page you own or have permission to test. You get an on-page report in about 30 seconds.
Scan a page