Free website accessibility test
Check one page for common accessibility issues — no signup required.
Relevant to the European Accessibility Act (EAA) and its German implementation, the Barrierefreiheitsstärkungsgesetz (BFSG).
WCAG 2.2 AA · axe-core, HTML_CodeSniffer & APCA
Automated testing detects common WCAG 2.2 AA failure patterns; it cannot establish conformance, and a clean result only means the rules found nothing. Determining conformance also needs manual review. No automated tool can guarantee legal compliance — treat this as a first signal, not a certificate.
What does the test check?
The free test checks a single page for common WCAG 2.2 AA failure patterns using axe-core and HTML_CodeSniffer, with additional APCA contrast observations. Results include an automated score and severity breakdown. Available finding details identify affected elements and provide remediation guidance.
Automated testing does not detect every accessibility barrier. Conformance evaluation also requires manual testing, including keyboard operation, reading order and usability with screen readers.
What is the EAA (and Germany's BFSG) — and who does it affect?
The European Accessibility Act covers specified products and consumer services. Germany implements it through the BFSG, applicable from 28 June 2025 with transitional provisions and exceptions. Under BFSG § 3(3), microenterprises providing services are exempt: they employ fewer than 10 persons and have annual turnover or an annual balance-sheet total not exceeding €2 million (§ 2(17)). This is not a general exemption for products. Applicability and the wider requirements need a separate legal assessment.
The most common errors — and how to fix them
Common findings include missing text alternatives, insufficient text contrast and form controls without associated labels. Remediation depends on context: describe informative images, give decorative images an empty alt attribute, provide programmatic labels and use native interactive elements where appropriate. Test keyboard operation and visual contrast after changing the code.
Locate automated findings on the selected page, review the affected elements and apply appropriate changes. Run another scan to check the result.
Frequently asked questions
Is the test really free?
Yes. A single-page test requires no account or payment method, subject to free-test usage limits. A free account includes an initial website scan of up to 100 pages. AI fix suggestions require an eligible paid plan.
How long does the test take?
Duration depends on page complexity, loading time and scanner availability. The browser loads your page before running the automated checks.
Does the test cover every WCAG requirement?
No. Automated testing detects common WCAG 2.2 AA failure patterns and cannot establish conformance. Things like logical tab order, real screen-reader usability, and plain-language content still need manual review.
Is this relevant to the EAA or Germany's BFSG?
It can support accessibility work, but it does not establish EAA or BFSG compliance. The test checks selected WCAG 2.2 AA failure patterns; legal applicability and additional product or service requirements need separate assessment.
What happens to my scan data?
We store only the tested URL and the results — no personal data about your site's visitors. Results are cached for 24 hours so re-testing the same page doesn't run twice unnecessarily.
Can I scan my whole site, not just one page?
A free account includes one website, an initial scan of up to 100 pages, then up to 25 pages per scan and automatic monthly rechecks. AI fix suggestions and reporting features require an eligible paid plan.