Web Accessibility 2026
The Complete Guide to WCAG 2.2 & EAA Compliance
Since June 28, 2025, accessibility has been mandatory across the EU for many consumer products and services. This guide explains the European Accessibility Act, WCAG 2.2, and how to make your website compliant.
Senorit
Web Design Agency
Summary
Since June 28, 2025, the European Accessibility Act has required accessibility for a defined list of consumer products and services across the EU, such as online shops and online banking. The technical bar is the standard EN 301 549, currently based on WCAG 2.1 AA. In Germany, fines go up to EUR 100,000.
- WCAG 2.2 Level AA includes 55 success criteria: 31 at Level A and 24 at Level AA
- Automated tools find only part of the issues, so you also need manual tests with a keyboard and a screen reader
- Around 87 million people in the EU have some form of disability (European Commission)
- Required color contrast: at least 4.5:1 for normal text and 3:1 for large text
- All functionality must work with the keyboard, which screen reader users depend on
Important notice
The European Accessibility Act (EAA) has applied since June 28, 2025. Transition periods up to 2030 cover only products a service provider already used before that date and existing contracts (Article 32). New offers have to meet the requirements now.
Digital accessibility is now law across the EU. Under the European Accessibility Act (EAA) and its national implementations in the member states, businesses must make certain consumer products and services accessible. This guide covers what the law requires and how to reach WCAG 2.2 compliance.
European Accessibility Act: the rules in force since 2025
The European Accessibility Act (EAA) is an EU directive that sets uniform accessibility requirements for products and services in all member states. It covers a wide range of digital products and services, which must be accessible to people with disabilities.
Affected digital products and services
- E-Commerce: online shops and booking platforms
- Banking Services: online banking, payment terminals
- Telecommunications: websites, apps, messaging services
- Transport: booking systems, schedule information
- E-Books: digital books and reading devices
- Computers & Operating Systems: hardware and software
When your website is covered
A purely informational website usually falls outside the EAA. Once you let consumers buy or sign a contract through the site, the rules can apply. Micro-enterprises that provide services, with fewer than 10 employees and no more than EUR 2 million in annual turnover or balance sheet total, are exempt. Get legal advice on your specific situation.
Timeline and deadlines
| Date | Event |
|---|---|
| April 2019 | European Accessibility Act (Directive (EU) 2019/882) adopted |
| June 2022 | Deadline for national transposition |
| June 28, 2025 | EAA becomes fully applicable |
| From June 28, 2025 | National market surveillance authorities enforce the rules |
| June 28, 2030 | Transition period ends for products already in use and existing contracts |
WCAG 2.2: the international standard for web accessibility
The Web Content Accessibility Guidelines (WCAG) 2.2 are the globally recognized standard for accessible web content. They rest on four principles, known as POUR:
Perceivable
All users must be able to perceive the information, whatever their sensory abilities.
Operable
All functionality must work with different input methods: keyboard, mouse, touch, and voice.
Understandable
Users must be able to understand the content and how to operate it. That means clear language, consistent navigation, and helpful error messages.
Robust
Browsers, screen readers, and other assistive technologies must be able to interpret the content reliably.
WCAG 2.2 conformance levels
WCAG defines three conformance levels. EN 301 549, the standard behind the EAA, requires Level AA:
- Level A: basic accessibility (31 criteria)
- Level AA: standard accessibility (24 additional criteria), required by EN 301 549
- Level AAA: enhanced accessibility (31 additional criteria)
New criteria in WCAG 2.2
WCAG 2.2 (released October 2023) adds new success criteria, including these:
2.4.11 Focus Not Obscured (Minimum)
Keyboard focus must not be completely hidden by other content (e.g., sticky headers, cookie banners).
2.5.7 Dragging Movements
Functions requiring dragging must also be operable with simple pointer gestures.
2.5.8 Target Size (Minimum)
Click targets must be at least 24x24 CSS pixels or have sufficient spacing.
3.3.7 Redundant Entry
Do not ask users again for information they have already entered (except for security purposes).
3.3.8 Accessible Authentication (Minimum)
A login must not depend on a cognitive function test, such as remembering a password or transcribing characters, unless there is an alternative or a helper. Password managers and paste have to work. Recognizing objects in images stays allowed at Level AA as an exception.
Legal requirements and penalties
The member states set the penalties for breaches of the EAA in their national laws.
Potential consequences of non-compliance
Risks of non-compliance
- Fines that vary by member state (in Germany up to EUR 100,000 for non-accessible offers, up to EUR 10,000 for other breaches)
- Orders from market surveillance, up to withdrawing a product or stopping a service
- Legal action from consumer protection organizations
- Reputational damage and loss of customer trust
Documentation requirements
What you have to document depends on whether you provide a service or manufacture a product:
- Service providers: describe how your service meets the requirements and publish that information in an accessible form, for example as a statement on your website.
- Manufacturers: products need an EU declaration of conformity, the CE marking and technical documentation.
- Information on request: market surveillance authorities can ask for the evidence that your offer conforms.
- Feedback option: a contact route for reporting barriers is not required by the EAA, but it helps you find problems early.
WCAG 2.2 checklist for your website
Use this checklist to assess your website's accessibility status:
Perceivable
Operable
Understandable
Robust
Technical implementation: code examples
These practical code examples cover the most important accessibility requirements.
Semantic HTML
Use native HTML elements instead of generic divs:
<!-- Wrong -->
<div class="header">
<div class="nav">...</div>
</div>
<div class="content">...</div>
<div class="footer">...</div>
<!-- Correct -->
<header>
<nav aria-label="Main navigation">...</nav>
</header>
<main>
<article>...</article>
</main>
<footer>...</footer> Accessible images
<!-- Informative image -->
<img
src="team-meeting.jpg"
alt="Five team members discussing a project at a whiteboard"
/>
<!-- Decorative image -->
<img src="decorative-line.svg" alt="" role="presentation" />
<!-- Complex image with detailed description -->
<figure>
<img
src="sales-chart.png"
alt="Sales growth 2024"
aria-describedby="chart-description"
/>
<figcaption id="chart-description">
The chart shows revenue growth from EUR 2.1M in Q1
to EUR 3.4M in Q4, with the strongest growth in
Q3 (+40%).
</figcaption>
</figure> Accessible forms
<form>
<div class="form-group">
<label for="email">
Email Address
<span aria-hidden="true" class="required">*</span>
</label>
<input
type="email"
id="email"
name="email"
required
aria-required="true"
aria-describedby="email-hint email-error"
aria-invalid="false"
/>
<p id="email-hint" class="hint">
We only use your email for this inquiry.
</p>
<p id="email-error" class="error" role="alert" hidden>
Please enter a valid email address.
</p>
</div>
<button type="submit">
Submit
<span class="visually-hidden">contact form</span>
</button>
</form> Skip link for keyboard users
<body>
<a href="#main-content" class="skip-link">
Skip to main content
</a>
<header>...</header>
<div id="main-content" tabindex="-1">
...
</div>
</body>
<style>
.skip-link {
position: absolute;
top: -40px;
left: 0;
padding: 8px 16px;
background: #000;
color: #e9edf3;
z-index: 100;
}
.skip-link:focus {
top: 0;
}
</style> Accessible buttons and links
<!-- Button with icon -->
<button
type="button"
aria-label="Open menu"
aria-expanded="false"
aria-controls="main-menu"
>
<svg aria-hidden="true">...</svg>
</button>
<!-- Link opening in new tab -->
<a
href="https://example.com"
target="_blank"
rel="noopener noreferrer"
>
External Resource
<span class="visually-hidden">(opens in new tab)</span>
</a>
<!-- Ensure minimum click size -->
<style>
button, a {
min-width: 44px;
min-height: 44px;
display: inline-flex;
align-items: center;
justify-content: center;
}
</style> ARIA live regions for dynamic content
<!-- Polite announcement (waits for pause) -->
<div aria-live="polite" aria-atomic="true">
Your search returned 42 results.
</div>
<!-- Immediate announcement (interrupts) -->
<div role="alert" aria-live="assertive">
Error: Connection was interrupted.
</div>
<!-- Status message -->
<div role="status" aria-live="polite">
Item added to cart.
</div> Testing tools and resources
Use these tools to test your website's accessibility:
Automated testing tools
axe DevTools
Browser extension for Chrome/Firefox. Finds WCAG violations directly in DevTools.
FreeWAVE
Web Accessibility Evaluation Tool. Visualizes accessibility issues directly on the page.
FreeLighthouse
Built into Chrome DevTools. Provides accessibility score and improvement suggestions.
FreePa11y
CLI tool for CI/CD integration. Automates accessibility testing in your build process.
Open SourceScreen readers for manual testing
- NVDA (Windows): free, widely used screen reader
- VoiceOver (macOS/iOS): built into Apple devices
- JAWS (Windows): professional screen reader (paid)
- TalkBack (Android): built into Android
Contrast checkers
- WebAIM Contrast Checker: online tool for color contrast testing
- Colour Contrast Analyser: desktop app with eyedropper function
- Stark: Figma/Sketch plugin for designers
Best practices for sustainable accessibility
1. Plan accessibility from the start
Build accessibility into every step of your development process: concept, design, and implementation. Retrofitting it later often costs more money and time.
2. Build a design system with accessible components
Create reusable components that are accessible from the start. That keeps accessibility consistent across all pages.
3. Integrate automated tests in CI/CD
Add tools like axe-core or Pa11y to your build pipeline to catch regressions early.
4. Conduct regular manual audits
Automated tools find only part of the accessibility issues. No tool can reliably judge whether an alt text describes the image or whether the focus order makes sense, so test manually on a regular basis as well, with a screen reader and the keyboard.
5. Involve real users
Run user tests with people who have disabilities. Their experience shows you how accessible your website is in practice.
6. Train your team
Make sure designers, developers, and content creators know the basics of accessibility, and train them regularly.
Professional accessibility audit
We review your website against WCAG 2.2 and deliver a report with recommendations sorted by urgency.
- Complete WCAG 2.2 review
- Screen reader & keyboard testing
- Prioritized action plan
Step by step: making your website accessible
Follow these steps to work toward WCAG 2.2 compliance for your website:
Conduct an accessibility audit
Analyze your website with automated tools such as axe DevTools, WAVE, or Lighthouse. Then test it manually with a screen reader and the keyboard.
Create a prioritized action plan
Sort the issues you found by severity (critical, major, moderate, minor) and set a realistic timeline for fixing them.
Implement semantic HTML
Use native HTML elements correctly: header, nav, main, article, aside, footer. Structure headings hierarchically (h1-h6) and use lists, tables, and forms.
Add ARIA attributes
Add ARIA labels, roles, and states where native HTML is not enough. Native HTML always comes first, and ARIA is only an enhancement.
Fix color contrast and visual design
Use a contrast ratio of at least 4.5:1 for normal text and 3:1 for large text. Do not convey information through color alone.
Ensure keyboard navigation
All interactive elements must be reachable and operable via keyboard. Focus must be visible and follow a logical order.
Make media content accessible
Images need meaningful alt text, and videos need captions and audio descriptions. Avoid media that plays automatically.
Test and improve continuously
Integrate accessibility testing into your development workflow. Conduct user testing with people who have disabilities.
Frequently asked questions (FAQ)
When did the European Accessibility Act come into effect?
Which businesses are affected by the EAA?
What are the penalties for non-compliance?
What does WCAG 2.2 Level AA compliance mean?
How long does it take to make a website accessible?
Do I need to completely rebuild my existing website?
Where to go from here
Where the EAA applies, web accessibility is a legal requirement, and it is good practice everywhere else. Around 87 million people in the EU have some form of disability, according to the European Commission, and accessible websites reach them.
The June 28, 2025 deadline has passed. If your offer falls under the EAA and is not accessible yet, start with an audit and work through the checklist point by point, because a thorough fix takes time.
We can help with the initial analysis, the technical implementation, and the EAA compliance documentation.
Sources & references
We checked and used these sources for this article:
Documentation
- 01
- 02
- 03
- 04
- 05
- 06