Accessibility Scan: WCAG 2.2 & the European Accessibility Act
Find the barriers that block people using screen readers, keyboards and zoom — in about 20 seconds. Every finding comes with its WCAG 2.2 criterion, the pages where it occurs and the fix.
Scan my site
Free · no signup · up to 10 pages · about 20 seconds · Not sure the EAA applies to you? Take the 5-question check ↓
We read the public HTML of up to 10 pages of your site. The report is kept for one hour so we can send it to you. This is an automated baseline, not a conformance audit.
- Fetching pages
- Checking WCAG criteria
- Looking for an accessibility statement
- Computing the index
What the result looks like
shop-example.com
Gaps in the automated baseline
- CriticalForm fields without a label — 6 of 10 pages
- CriticalImages without a text alternative — 3 of 10 pages
- ModerateNo skip link and no landmarks — 10 of 10 pages
Example for a made-up site. Your result appears here in about 20 seconds.
Accessibility baseline
The most serious barriers
Leave your email to open the full report and get it as a PDF.
What automation can't check
These points need a person and a browser. They are part of every manual audit.
1.4.3Text contrastMeasure text against its real background: 4.5:1, or 3:1 for large text.1.4.11Non-text contrastCheck borders of fields, icons and focus rings against the background: 3:1.1.4.10Reflow at 320 pxSet the window to 320 CSS px wide: no horizontal scrolling, nothing cut off.2.1.1Everything works with a keyboardUnplug the mouse and complete your main journey with Tab, Enter, Space and arrows.2.4.7 / 2.4.11Focus visible and not hiddenTab through the page: the focus ring is always visible and never under a sticky header.2.5.7Alternative to draggingEvery slider, carousel or drag-and-drop also works with single clicks.2.5.8Target size of at least 24×24 pxMeasure small icons and links on a phone-sized screen.3.2.6Help in the same placeContact or help links sit in the same place on every page.3.3.7No re-entering dataMulti-step forms don't ask twice for what the user has already entered.1.2.xCaptions and audio descriptionVideos have captions; where needed, a transcript or audio description.—Screen reader walkthroughComplete your main journeys with NVDA (Windows) or VoiceOver (macOS, iOS).
Full report + PDF by email
Every barrier, every page, code samples and a prioritised fix plan you can forward to your developers.
Manual audit & remediation plan
A YuSMP engineer tests your key user journeys with a keyboard and screen readers against WCAG 2.2 AA, then fixes the issues in your code or design system.
- Keyboard and screen reader testing (NVDA, VoiceOver) of your main journeys
- Contrast, focus and reflow measured in a real browser
- A remediation plan ranked by impact, mapped to WCAG 2.2
- Fixes in shared components, so they apply site-wide
Looking at UX rather than WCAG criteria? Try the Website Usability Check.
Does the EAA apply to you?
Five questions, answered in your browser — nothing is sent until you request the report. A first orientation, not legal advice.
What the scan checks
25 rules: 19 are scored from the markup, 6 are signals that need a browser or a human. The confidence column says how sure an automated check can be.
| Rule | WCAG criterion | Level | Confidence |
|---|---|---|---|
| Page language is not declared | 3.1.1 | A | Confirmed in the markup |
| Page has no meaningful title | 2.4.2 | A | Confirmed in the markup |
| Images without a text alternative | 1.1.1 | A | Confirmed in the markup |
| Form fields without a label | 3.3.2 | A | Confirmed in the markup |
| Buttons without an accessible name | 4.1.2 | A | Confirmed in the markup |
| Links without an accessible name | 2.4.4 | A | Confirmed in the markup |
| Embedded frames without a title | 4.1.2 | A | Confirmed in the markup |
| Zoom is blocked on mobile | 1.4.4 | AA | Confirmed in the markup |
| Empty headings | 1.3.1 | A | Confirmed in the markup |
| Media starts by itself with sound | 1.4.2 | A | Confirmed in the markup |
| Heading levels are skipped | 1.3.1 | A | Very likely — confirm manually |
| Page has no main heading (H1) | 1.3.1, 2.4.6 | Best practice | Very likely — confirm manually |
| Data tables without header cells | 1.3.1 | A | Very likely — confirm manually |
| Broken list markup | 1.3.1 | A | Very likely — confirm manually |
| Positive tabindex values | 2.4.3 | A | Very likely — confirm manually |
| ARIA used incorrectly | 4.1.2 | A | Very likely — confirm manually |
| Personal-data fields without autocomplete | 1.3.5 | AA | Very likely — confirm manually |
| No skip link and no landmarks | 2.4.1 | A | Very likely — confirm manually |
| Links with generic text | 2.4.4 | A | Very likely — confirm manually |
| Text contrast (needs a browser render) | 1.4.3 | AA | Needs a manual check |
| Touch target size (needs a browser render) | 2.5.8 | AA | Needs a manual check |
| Keyboard focus visibility (needs a browser render) | 2.4.7, 2.4.11 | AA | Needs a manual check |
| Video and audio: captions and transcript | 1.2.2 | A | Needs a manual check |
| Accessibility statement and feedback channel | EAA | EAA | Needs a manual check |
| Linked PDF documents | — | Info | Needs a manual check |
How it works
Crawl
We open your page and follow internal links until we have up to 10 pages, the way a visitor would.
Check
Each page is checked against 19 markup rules mapped to WCAG 2.2 A/AA criteria, plus 6 signals for a manual review.
Score
The index weighs every barrier by severity and by how many pages it affects. Unproven findings count at 70%.
Fix
Every finding comes with who it hurts, the fix and a sample of your markup to hand to a developer.
Automated vs manual audit
This automated scan
- Reads the HTML the server delivers
- Finds missing names, labels, alternatives and structure errors
- Takes about 20 seconds and costs nothing
- Good for a baseline and for regression checks
A manual audit
- Tests the rendered page in real browsers
- Covers contrast, keyboard use, focus, reflow and media
- Walks through your key journeys with NVDA and VoiceOver
- Ends with a remediation plan you can act on
FAQ
What is the European Accessibility Act and since when does it apply?
The European Accessibility Act is Directive (EU) 2019/882. It has applied since 28 June 2025 through national law: in Germany through the BFSG (Barrierefreiheitsstärkungsgesetz), in France and Italy through their national transposition acts. It covers a list of consumer products and services, such as e-commerce, consumer banking, passenger transport, e-books and telecom.
Does the EAA apply to my business?
It covers the listed sectors when you serve consumers in the EU, no matter where your company is based. Micro-enterprises that provide services are exempt. Our five-question check gives a first orientation. This is not legal advice.
WCAG 2.1 or 2.2 — which one matters?
The harmonised standard EN 301 549 currently references WCAG 2.1 AA. WCAG 2.2 adds six A/AA criteria (2.4.11, 2.5.7, 2.5.8, 3.2.6, 3.3.7, 3.3.8) and keeps everything else. We scan against 2.2 because it includes 2.1.
Can an automated scan confirm that my site meets the EAA?
No. Automated tools detect only part of the barriers. The result is a baseline for planning, not a statement of conformance.
What does this scan not check?
Contrast, keyboard operation, focus, reflow, media alternatives, how clear the content is, PDF documents, pages behind a login and content that only JavaScript renders in the browser.
What is an accessibility statement and do I need one?
It is information on how your service meets the accessibility requirements (Annex V of the EAA). The format differs by country: in Germany the information goes into the general terms and conditions or is published in another clearly perceivable way, for example on the website, in France it is the «déclaration d'accessibilité», in Italy the «dichiarazione di accessibilità». Check the wording for your countries with counsel.
How do we fix the issues, and how long does it take?
Most markup barriers are fixed once, in shared components or the design system, and the fix then applies to every page. A manual audit adds the issues automation can't see and ranks everything by impact. Request an audit and remediation plan.
Do you store my data or my site's content?
The report is kept for one hour so we can send it to you, then it is deleted. Your contact details reach us only if you send a form. Our crawler identifies itself as YuSMP-AccessibilityScan.
Keep going
- WCAG 2.2 guide for web appsWhat changed in WCAG 2.2, how the EAA uses it and how to test.
- Website Usability CheckButtons, forms and mobile layout from the visitor's point of view.
- Also preparing for the EU AI Act?Classify your AI system by risk level in a few minutes.
- Web application developmentAccessible web apps built by YuSMP engineers.