The European Accessibility Act (EAA) deadline of June 28, 2025 has come and gone. If you run a website that serves EU customers, the grace period is over. Enforcement agencies across all 27 member states are now actively investigating complaints, issuing warnings, and in some countries, handing out fines. This is not a future problem anymore. It is a right-now problem. This guide covers everything website owners need to know: what the EAA actually requires, how enforcement works in practice, the WCAG 2.1 AA standard you need to meet, penalties you face by country, and a step-by-step compliance checklist you can start working through today.
What Is the European Accessibility Act and Why Does It Matter Now
The European Accessibility Act (Directive 2019/882) is an EU-wide law that requires digital products and services to be accessible to people with disabilities. It was adopted in 2019, member states had until June 28, 2025 to transpose it into national law, and now it is fully enforceable.
Why should website owners care? Because the EAA is not limited to government websites or massive corporations. It applies to any business that provides digital services to EU consumers. That includes e-commerce stores, SaaS platforms, banking portals, booking systems, media services, and transport ticketing. If someone in the EU can access your website and make a purchase or use a service, the EAA likely applies to you.
The scope is deliberately broad. Previous EU accessibility directives only covered public sector websites. The EAA extends this to the private sector. And unlike some regulations that come with years of soft enforcement, several member states started issuing formal warnings within weeks of the June 2025 deadline.
Here is the part that catches many businesses off guard: you do not need to be based in the EU. A US-based e-commerce company selling to German customers falls under the EAA just as much as a company headquartered in Berlin. The law follows the customer, not the company.
The June 2025 Deadline Has Passed: Where We Are Now
As of March 2026, we are nine months past the EAA enforcement date. What has actually happened since June 2025?
The short answer: enforcement is real, but uneven. Some countries moved fast. France's DGCCRF issued formal notices to major retailers before the end of 2025. Germany's Bundesnetzagentur has been investigating complaints filed through its portal. The Netherlands' ACM publicly stated it would prioritize e-commerce and banking platforms for early enforcement.
Other countries have been slower. Several Eastern European member states are still building out their enforcement infrastructure. But that is changing month by month. The EU's market surveillance framework means findings in one country can trigger investigations elsewhere, creating a domino effect.
What we are seeing on the ground is a complaint-driven enforcement pattern. Regulators are not systematically auditing every website. Instead, they are responding to complaints from users with disabilities and advocacy organizations. These organizations have been preparing for the EAA for years, and they are filing complaints strategically, targeting high-profile businesses to establish precedents.
The practical takeaway? If your website has obvious accessibility barriers, like missing alt text, no keyboard navigation, or poor color contrast, you are a complaint waiting to happen. And once a complaint lands on a regulator's desk, you are on a clock.
What WCAG 2.1 AA Actually Requires for Your Website
The EAA references the European standard EN 301 549, which in turn maps to WCAG 2.1 Level AA. This is the technical benchmark enforcement agencies use. You need to understand what it actually means for your website.
WCAG 2.1 AA is organized around four principles, often called POUR: Perceivable, Operable, Understandable, and Robust. Each principle contains specific success criteria. There are 50 success criteria at Level AA. Here are the ones that trip up the most websites.
Perceivable: Can Users See and Hear Your Content
Every non-text element needs a text alternative. Images need alt text. Videos need captions and audio descriptions. Decorative images should have empty alt attributes so screen readers skip them. This sounds basic, but a 2025 WebAIM study found that 22% of homepage images across the top one million websites still lacked appropriate alt text.
Color contrast is another major area. Text must have a contrast ratio of at least 4.5:1 against its background (3:1 for large text). That trendy light gray text on a white background? It fails. And it is one of the first things automated scanners flag.
Content must be resizable up to 200% without losing information or functionality. Users who zoom in should not have to scroll horizontally. This affects layout decisions, particularly for sites that use fixed-width elements or absolute positioning.
Operable: Can Users Navigate and Interact
Every interactive element must be accessible via keyboard alone. That means links, buttons, form fields, menus, and custom widgets all need to work without a mouse. Tab order must follow a logical sequence. Focus indicators must be visible so keyboard users know where they are on the page.
Dropdown menus, modal dialogs, carousels, and accordion panels need proper keyboard support and ARIA attributes. Many JavaScript-heavy interfaces fail here because developers build for mouse interaction and forget keyboard users entirely.
Users must have enough time to read and interact with content. Auto-playing carousels, session timeouts, and timed form submissions all need pause, stop, or extend mechanisms. Flashing content that could trigger seizures must be avoided.
Navigation must be consistent. Users need multiple ways to find pages, like a search function and a site map in addition to the main navigation. Headings and labels must be descriptive. Link text like "click here" or "read more" fails because it provides no context when read out of sequence by a screen reader.
Understandable: Can Users Comprehend Your Content
The language of the page must be declared in the HTML lang attribute. If you switch languages within the page, those sections need their own lang attributes. This lets screen readers switch pronunciation rules automatically.
Navigation must appear in the same location across pages. Components that have the same function must be labeled consistently. If your search box is labeled "Search" on the homepage, it should not be labeled "Find" on another page.
Form inputs need proper labels and instructions. Error messages must identify the problem and suggest corrections. Required fields must be clearly indicated before the user submits the form, not after.
Robust: Does Your Code Work with Assistive Technology
Your HTML must be valid and well-structured. Elements need proper opening and closing tags. IDs must be unique. ARIA roles, states, and properties must be used correctly. Screen readers rely on the DOM structure to interpret and announce content, so messy markup causes real problems.
Custom interactive components, anything beyond native HTML elements, need appropriate ARIA labels and roles. A custom dropdown built with div elements needs role="listbox", aria-expanded, and keyboard event handlers to be accessible. Native HTML select elements get this for free.
Status messages, like form validation errors or shopping cart updates, must be announced to screen readers without requiring focus changes. This typically requires aria-live regions.
Penalties by Country: What You Risk
EAA penalties vary dramatically across EU member states. Here is a snapshot of the enforcement landscape as of early 2026:
| Country | Maximum Fine | Enforcement Agency | Notable Details |
|---|---|---|---|
| Spain | Up to 1,000,000 EUR | Ministry of Social Rights | Three-tier system; minor starts at 30,000 EUR |
| Netherlands | 900,000 EUR or 10% revenue | ACM | Whichever is higher; active complaint portal |
| Sweden | ~900,000 EUR (SEK 10M) | PTS / Konsumentverket | Can ban products from market |
| France | 250,000 EUR (repeat) | DGCCRF / ARCOM / ARCEP | Already issuing formal notices to retailers |
| Belgium | 200,000 EUR per breach | SPF Economie | Can suspend business operations |
| Finland | 150,000 EUR | Traficom / Tukes | Daily penalties for delayed remediation |
| Germany | 100,000 EUR per violation | Bundesnetzagentur | Per-violation; can multiply fast |
| Austria | 80,000 EUR per violation | Federal Ministry | 14-day complaint response window |
| Ireland | 60,000 EUR + prison | CCPC | Only country with criminal sanctions |
| Italy | 5% of annual turnover | AgID | 90-day cure period; turnover-based |
| Portugal | ~45,000 EUR | INCODE | Can suspend non-compliant services |
| Poland | ~25,000 EUR | Ministry of Digital Affairs | Mandatory paid audits at company expense |
These are maximum amounts. Actual fines depend on severity, company size, duration of non-compliance, and whether you made genuine efforts to fix things. But the trend is clear: regulators across Europe are treating web accessibility as a consumer rights issue, not an optional nice-to-have.
For businesses operating across multiple EU markets, the risk multiplies. A non-compliant website serving customers in five countries could face parallel enforcement actions from five separate regulators. There is no single-penalty cap across borders.
For the full country-by-country breakdown with enforcement details, read our complete guide to EAA fines by country.
Your Practical Compliance Checklist: 10 Steps to Take Now
Stop reading about compliance theory and start doing something. Here are ten concrete steps, ordered by impact and urgency.
- Run an automated accessibility scan today. Use our free accessibility checker to get a baseline score. Automated tools catch roughly 30-40% of accessibility issues, but they catch the obvious ones fast: missing alt text, contrast failures, missing form labels, broken ARIA. Fix these first.
- Test keyboard navigation manually. Put your mouse in a drawer. Tab through your entire website. Can you reach every link, button, and form field? Can you see where focus is? Can you operate dropdown menus and modal dialogs? If you get stuck anywhere, that is a WCAG failure.
- Check your heading structure. Headings should follow a logical hierarchy: one H1 per page, then H2s for main sections, H3s for subsections. Skipping levels (H1 to H3) or using headings purely for styling breaks the document outline that screen readers rely on.
- Fix color contrast failures. Use a color contrast checker on your primary text, buttons, links, and form elements. Anything below 4.5:1 for normal text needs to change. This is usually one of the quickest fixes, just darken your grays and lighten your backgrounds.
- Add alt text to every meaningful image. Every image that conveys information needs descriptive alt text. Product photos, infographics, charts, and diagrams all need it. Decorative images get
alt="". Icons that serve as links or buttons need alt text describing their function, not their appearance. - Label all form inputs. Every form field needs a visible, associated label using the
forattribute or by wrapping the input in alabelelement. Placeholder text does not count as a label. Error messages must identify which field has the problem and what to do about it. - Declare your page language. Add
lang="en"(or your appropriate language code) to thehtmlelement. If your page contains content in multiple languages, wrap those sections in elements with the correctlangattribute. - Ensure all videos have captions. Pre-recorded video content needs synchronized captions. This is not just for hearing-impaired users. It is an explicit WCAG requirement. Auto-generated captions are a starting point, but they need human review for accuracy.
- Publish an accessibility statement. Most EU countries require this. Your statement should describe your compliance level, known limitations, remediation plans, and contact information for reporting barriers. Use the accessibility statement template as a starting point.
- Set up ongoing monitoring. Accessibility is not a one-time fix. Content updates, design changes, and new features can introduce new barriers. Set up automated monitoring to catch regressions. Our monitoring plans run weekly or daily scans and alert you when issues appear.
Who Is Exempt from the EAA
The EAA does include exemptions, but they are narrower than most people assume.
Microenterprises are exempt from the service requirements. A microenterprise is defined as having fewer than 10 employees AND annual turnover or balance sheet total under 2 million euros. Both conditions must apply. A 9-person company with 5 million euros in revenue does not qualify. And even microenterprises are still covered for product requirements.
There is also a disproportionate burden defense. If making a specific element accessible would fundamentally alter the nature of the product or service, or would impose costs that are demonstrably disproportionate, a company can claim exemption for that specific element. But this requires documented evidence: a formal cost analysis, assessment of alternatives, and ongoing review. Simply saying "it costs too much" does not work. Regulators expect you to have explored less costly alternatives first.
Businesses that only serve domestic customers outside the EU are not affected. But if even one EU-based customer can use your digital service, you are potentially in scope. This is particularly relevant for e-commerce and SaaS businesses with global reach.
Content published before June 28, 2025 has some transitional provisions in certain member states, but new content and significant updates to existing content must comply from day one.
Common Accessibility Mistakes That Trigger Complaints
After nine months of EAA enforcement, patterns are emerging in the types of complaints regulators are receiving. Understanding these patterns helps you prioritize your remediation efforts.
The number one complaint category is inaccessible forms. Checkout processes, registration forms, contact forms, and search filters that cannot be completed with a keyboard or screen reader generate the most user frustration. When someone cannot complete a purchase because the payment form lacks labels or the address dropdown does not work with keyboard, that is both a lost customer and a potential complaint.
The second most common category is missing or inadequate alternative text. Users who rely on screen readers encounter images described as "IMG_3847.jpg" or "image" or no alt text at all. Product images without descriptions mean a blind user literally cannot tell what is being sold.
Third: inaccessible navigation. Mega-menus that only open on hover, hamburger menus that cannot be activated by keyboard, and mobile navigation patterns that lack ARIA attributes create barriers for millions of users.
Fourth: auto-playing media without controls. Video backgrounds, auto-playing carousels, and animated content that cannot be paused affect users with cognitive disabilities, vestibular disorders, and photosensitive epilepsy.
Fifth: insufficient color contrast and text resizing issues. Users with low vision who increase browser zoom to 200% find layouts breaking, text overlapping, or content disappearing entirely. Combined with low contrast text, the experience becomes unusable.
How Web Accessibility Checker Helps You Comply
We built Web Accessibility Checker specifically to help website owners navigate the EAA compliance landscape. Here is how the tool works and what it catches.
Our free scanner runs a comprehensive DOM analysis in under a second and produces an accessibility score based on WCAG 2.1 AA criteria. It checks for the most common violations: missing alt text, contrast issues, form label problems, heading hierarchy errors, missing language declarations, keyboard traps, and ARIA misuse. You get a prioritized list of issues with specific guidance on how to fix each one.
For a deeper analysis, our PageSpeed Insights integration evaluates your site's performance and accessibility from Google's perspective. Since Core Web Vitals and accessibility overlap significantly (both care about responsiveness, readability, and usability), this gives you a holistic view of your site's health.
Paid plans add monitoring. Instead of running one-off scans and hoping nothing breaks, you get weekly or daily automated checks. When a new content update introduces an accessibility regression, you know about it before your users file a complaint with a regulator.
The Pro and Agency plans also include a compliance widget you can embed on your site. It provides an accessibility statement page and demonstrates to both users and regulators that you are actively monitoring and maintaining compliance.
Run your first scan now. It takes 30 seconds and costs nothing. You will know exactly where you stand before you finish reading this article.
What Happens If You Do Nothing
Let us be direct. If you have read this far and are considering ignoring the EAA, here is what that path looks like.
A user with a disability tries to use your website and cannot. They file a complaint with their national enforcement agency. The agency investigates and finds your site non-compliant. You receive a formal notification with a remediation deadline, typically 30 to 90 days depending on the country.
If you fix the issues within that window, you may avoid a fine entirely. Many countries offer this grace period for first-time violations. But the clock starts when you receive the notification, not when you start working on fixes. If your site has dozens of accessibility issues, 30 days may not be enough.
If you miss the deadline, fines follow. And remember, these are per-violation fines in many countries. A site with 20 distinct accessibility failures could face 20 separate penalties.
Beyond fines, some countries can order your service suspended in their market. The Netherlands, Belgium, and Sweden all have this power. Being locked out of an entire national market even temporarily represents far more revenue loss than the fines themselves.
There is also the reputational dimension. Enforcement actions are typically public. Your competitors will know. Your customers will know. In a market where consumers increasingly care about inclusivity, being publicly called out for excluding people with disabilities is a brand problem that money cannot easily fix.
The alternative is simpler: start fixing things now. Run a scan, address the critical issues, publish an accessibility statement, and set up monitoring. That is the difference between a company making genuine efforts and one ignoring the problem. Regulators care about that distinction.