Website accessibility testing with evidence: Find what stops people
using your website.

No — and be careful with anyone who says it does. We find barriers, prove them with evidence, propose concrete fixes and track progress. The fixes land in your code or CMS, made by your team. Compliance is a legal assessment about your product, not a button in a dashboard.

The testing is not: it needs no script on your site, and it measures what your users actually get. Separately, there is an optional visitor toolbar — one script tag, if you want it. It changes how a page is presented, and only for the visitor who asks: text size, spacing, contrast, reading aloud and the like. It fixes nothing in your code, it does not change whether your site meets WCAG or the BFSG, and our scans never see it, because it switches itself off for our crawler. What makes a site accessible is still the fix in your source, which is what the rest of Reviseberg is for.

A scanner evaluates rules and stops there. We run the rules too — every axe-core rule, on every page — and then say plainly which criteria no rule can decide, rather than leaving them blank and letting the blank read as a pass. On top of that, the keyboard agent performs a task: it tabs through your journey with real key presses, records where focus lands and keeps the trail, so a finding is something you can replay rather than a rule id. Beside both, checks of our own lay every page out again at 320 px, zoomed to twice the size and with wider text spacing and, on a crawl from an account, operate controls and fill forms with test data on one page per template — each reporting a failure only where it measured one, and a question where a person has to decide. The agents that would do the same for a screen reader, alt-text judgement, zoom and forms are in development, and are labelled that way in the product.

In the EU. We store crawl results, findings and evidence for your sites; we do not sell data or use your content to train third-party models. Details are in the privacy policy, and a data processing agreement (AVV, Art. 28 GDPR) is part of the contract.

No. A public site needs a URL and nothing else. For a site that is not public, you give the crawler its way in when you add the site: the browser’s password prompt (basic auth), a login page it signs in through, or a token header your gatekeeper accepts. It is stored encrypted and sent to that site’s host and nowhere else. A site on a VPN or a private network is reached through a proxy you run inside that network — the crawler does not join the VPN itself. The free scan on this website reads public pages only.

This website, the free-scan report, the emails and the accessibility statement you publish are available in German. The dashboard itself is in English for now.

Plans start at €149 per month for a single site, and signing in is free: 1 site, up to 100 pages, crawls you start yourself. See pricing — pilot customers get founding-customer terms.