Accessibility Checker
Short answer
Test the rendered page against the WCAG 2.1 A and AA rules that software can check, colour contrast included. Each issue links its WCAG criterion and the European Accessibility Act requirement.
Tests the rendered page against the WCAG 2.1 Level A and AA rules that software can check.
Page being tested
What It Does
Renders the page in your browser and tests it against the WCAG 2.1 Level A and AA rules that software can check: colour contrast of the rendered text, names of buttons, links and form fields, image alternatives, headings and landmarks, ARIA use and page language, among others. Each issue is rated by impact, shows the affected elements and what to fix, and links the WCAG success criterion and the European Accessibility Act (Directive 2019/882) Annex I requirement it relates to. Checks that need a person are listed separately.
Why It Matters
The European Accessibility Act has applied since 28 June 2025 to many digital products and services sold in the EU, and each member state sets and enforces its own penalties. Beyond the law, accessibility problems shut out real visitors. An automated check is the fastest way to find the obvious failures before a manual review.
How It Works
-
Enter a page URL, or paste the page's HTML
-
RankProof fetches the HTML; your browser renders it with the site's own styles and images, without running the page's scripts
-
An open-source rule engine tests the rendered page against the WCAG 2.1 A and AA rules
-
Issues come back by impact, with the affected elements, what to fix and the WCAG and EAA references
Sample input + output
url: https://rankproof.eu
Accessibility scan (WCAG 2.1 A and AA rules):
3 issues on 7 elements · Critical 1 · Serious 2
Critical Images must have alternative text 1 element
WCAG 1.1.1 · EAA I.2.e
Serious Elements must meet minimum colour contrast 5 elements
WCAG 1.4.3 · EAA I.2.c
Serious Form elements must have labels 1 element
WCAG 4.1.2 · EAA I.2.n
Rules passed: 32 · Need a person to check: 3 Who Uses This
-
EU Business Owner
Run a baseline check now that the EAA applies, and see which WCAG failures to fix first.
-
Accessibility Consultant
Get a quick first pass on a client page, with issues grouped by impact and mapped to EAA requirements, before the manual review.
-
Web Developer
Re-run the check on staging pages before each release to catch accessibility regressions before they reach production.
Frequently Asked Questions
What is WCAG 2.1?
The Web Content Accessibility Guidelines 2.1 are the W3C standard for web accessibility. In the EU, the harmonised standard EN 301 549 v3.2.1 applies WCAG 2.1 Level AA to web content, which is why this checker uses the 2.1 A and AA rules.
What is the European Accessibility Act?
Directive (EU) 2019/882 sets accessibility requirements for many products and services sold in the EU, including e-commerce, banking and e-books. It has applied since 28 June 2025.
What does automated checking miss?
A lot. Automated rules find only part of the problems: whether alt text is meaningful, whether the reading order makes sense, whether captions are accurate. The report lists the items that need a person, and the EAA requirements page has a checklist of manual checks. Treat the scan as the first step, then test with a keyboard and a screen reader.
Does it check colour contrast?
Yes, for text on solid backgrounds in the rendered page. Text over images or gradients cannot be measured automatically and is listed as needing a manual check. For a single pair of colours, use the Color Contrast Checker.
Does it work on sites built with JavaScript?
Only partly. The page's scripts are not run, so content that JavaScript adds after loading is missing from the scan. The report warns you when a page renders with almost no text.
What is the difference between WCAG 2.1 and 2.2?
WCAG 2.2 adds nine success criteria to 2.1 and removes one (4.1.1 Parsing). New Level AA criteria include Focus Not Obscured (2.4.11), Dragging Movements (2.5.7), Target Size (2.5.8) and Accessible Authentication (3.3.8). EU web content is measured against WCAG 2.1 AA through EN 301 549 v3.2.1.