Not sure if your website meets EAA accessibility requirements? With the June 2025 deadline approaching, now’s the time to check and fix what’s missing – otherwise, you could face hefty fines and legal consequences.
In this guide, you’ll learn what makes a website EAA compliant – and how to check yours using both automated tools and manual testing.
A website is EAA compliant if it meets the WCAG 2.2 AA accessibility standards, as required by the European Accessibility Act (EAA). For the uninitiated, WCAG is a globally recognised set of standards that ensure websites are usable by people with disabilities.
An EAA-compliant website should meet requirements like the following, among others:
ℹ️ Note: The EAA references the EN 301 549 standard, which currently points to WCAG 2.1 Level AA. However, EN 301 549 is being updated, and the next version is expected to reference WCAG 2.2 Level AA. That’s why we recommend aligning with WCAG 2.2 now to stay ahead.
If you’re wondering whether your website is EAA compliant, the answer starts with testing.
To check for EAA compliance: run an automated scan + perform manual testing
💡 Tip: Use WebYes for automated checks and Accessibility Insights for guided manual testing.
Start by using the free online EAA compliance checker from WebYes (given below). Just enter your website URL – the tool will scan your site for common accessibility issues like missing alt text, low contrast, and more. If no major issues are found, that’s a strong first step.
However, keep in mind that automated tools can’t catch everything. Some issues – like focus states, screen reader behaviour, and usability – require human review. After fixing automated findings, follow up with manual testing to ensure full compliance.
For manual testing, you can use Microsoft’s Accessibility Insights browser extension. It provides step-by-step guidance for testing accessibility issues manually. Alternatively, consider working with agencies that offer manual audits, such as Sweans.
To make your website EAA compliant, it needs to meet the WCAG 2.2 Level AA accessibility standards. By checking where your website currently stands – through automated scans and manual testing – you’ve already taken the first step toward compliance.
Now, follow these steps to bring your website into EAA compliance:
Now, let’s go through each step in detail.
Start by resolving all issues found during your automated and manual audits. This includes common problems like missing alt text, poor colour contrast, inaccessible forms, and broken keyboard navigation. Fix both technical barriers and content-related issues.
💡 Tip: Fix high-impact issues first – like missing alt text, low contrast, and broken navigation.
After applying fixes, re-scan your site using tools like WebYes and revisit key manual testing steps. This ensures all issues are resolved and nothing new has been introduced during the process. It helps catch any missed issues before they impact users.
Add a public-facing accessibility statement to your website. It should include your accessibility efforts, any known limitations, and contact information for users needing assistance. This is not only helpful for users – it’s also part of EAA requirements.
💡 Tip: You can use the W3C accessibility statement generator to create a statement quickly. Or check out our guide: How to Write an EAA Accessibility Statement
Accessibility is not a one-time task. Set up regular scans and schedule periodic manual reviews – especially after site updates or new content launches. Tools like WebYes can help you monitor changes and maintain compliance over time.
We recommend you check out our “How to Make Your Website EAA Compliant” guide for detailed steps.
WebYes helps you meet EAA compliance requirements by guiding you through the process of identifying and fixing accessibility issues on your website. You don’t need to be an expert in WCAG or EN 301 549 – WebYes handles the heavy lifting.
Here’s how WebYes supports your EAA compliance efforts:
The EAA deadline is fast approaching – now’s the time to take action. Your website is often the first impression of your brand, and accessibility is no longer optional – it’s necessary. WebYes gives you the tools to get it right, from your first audit to ongoing compliance.
Yes, you can face fines or legal issues if your website doesn’t meet EAA standards.
The EAA is the law, and it references WCAG 2.1 AA as the standard to follow.
Not fully. While accessibility widgets and automated tools can help identify or fix some issues, they don’t guarantee full compliance.
Yes, to some extent. You must make your website as accessible as possible, and clearly list any inaccessible parts in your accessibility statement, along with your plan and timeline to fix them.
How do you create web content that drives action, not just fills space? The kind where every word earns its place, serves a purpose, and leads people to what they need. In this edition of The Better Web Dialogues, we talk with Kavya R, Content Designer at CookieYes, to unpack the craft of writing web […]
Not every organisation or service is covered by the European Accessibility Act (EAA). While the EAA sets out broad accessibility requirements for products and services across the EU, it also outlines specific exemptions – some permanent, some limited in scope. This section breaks down who and what is fully exempt from the EAA, so you […]
Because the European Accessibility Act (EAA) is transposed into national law by each EU member state, the exact rules can vary slightly from country to country. If you’re a business operating in Ireland and working on EAA compliance, we’re here to help you understand what’s required. In this post, we break down everything you need to know about the […]
The European Accessibility Act (EAA) requires businesses to meet accessibility standards by June 28, 2025. Companies that fail to meet the EAA requirements by this compliance deadline risk facing significant fines and penalties. So, what kinds of penalties can you expect for non-compliance? And how can your business avoid them? In this guide, we’ll break […]