The European Accessibility Act went into full effect in June 2025. If your website serves users in the EU, and if you’re doing e-commerce, SaaS, or digital services, it almost certainly does, you’re already on the clock.
This isn’t hypothetical. It’s law. And unlike most regulatory deadlines that come with extended grace periods and soft enforcement, the EAA has teeth. Member states can impose fines, require mandatory remediation, and allow individuals to file complaints directly against non-compliant businesses.
If you’ve been treating web accessibility as a “nice-to-have”, something you’ll get to eventually, after the redesign, after the launch, after Q3–2026 is the year that approach stops working.
What the European Accessibility Act Actually Requires
The EAA mandates that digital products and services meet WCAG 2.1 Level AA standards as a minimum. WCAG, the Web Content Accessibility Guidelines, is the international benchmark for accessible web design, maintained by the W3C.
Level AA compliance covers a broad range of requirements:
- Text contrast ratios of at least 4.5:1 for body copy, 3:1 for large text
- Full keyboard navigability, every interaction accessible without a mouse
- Screen reader compatibility, proper semantic HTML, ARIA labels, logical heading structure
- Captions for all pre-recorded video content
- No content that flashes more than three times per second (seizure risk)
- Clear focus indicators for interactive elements
- Form inputs with descriptive, programmatically associated labels
If you’re looking at that list and thinking “I don’t know if our site does half of those”, that’s exactly the problem.
This Isn’t Just a European Problem
The US has its own accessibility framework: the ADA (Americans with Disabilities Act). Courts have consistently ruled that websites are “places of public accommodation” under Title III, and accessibility lawsuits have been increasing year over year for nearly a decade.
According to the UsableNet 2024 ADA Digital Accessibility Lawsuit Report, over 4,000 web accessibility lawsuits were filed in federal court in 2023 alone, a number that’s been climbing steadily. Retailers, restaurants, banks, and SaaS companies are all targets. Small businesses aren’t exempt.
The Department of Justice finalized its rule in April 2024 requiring state and local government websites to meet WCAG 2.1 Level AA. Private sector pressure follows public sector mandates. It always does.
WCAG compliance for business isn’t about regulatory checkbox-ticking. It’s about building sites that work for the 1.3 billion people globally who live with some form of disability, and protecting yourself legally in the process.
The Business Case (Beyond Compliance)
Compliance tends to get all the attention because it’s the stick. But there’s also a significant carrot.
Accessible Sites Rank Better
Google’s crawlers are, functionally, the world’s most sophisticated screen reader. Semantic HTML, proper heading hierarchy, descriptive alt text, labeled form fields, everything that helps a screen reader user navigate your site also helps Googlebot understand and rank your content. Accessibility and SEO share a foundation.
Accessible Sites Convert Better
Faster load times (a byproduct of clean, semantic code). Clearer navigation. Logical content hierarchy. Readable type. These aren’t accommodations, they’re good UX principles that benefit every user. The “curb cut effect” is real: features designed for people with disabilities consistently improve the experience for everyone.
Accessible Sites Expand Your Market
People with disabilities control an estimated $490 billion in disposable income in the US alone, according to the American Institutes for Research. If your site doesn’t work for them, they’re buying from someone whose site does. Accessibility is a market segment, not a charity initiative.
The Most Common Accessibility Failures We See
After auditing a lot of business websites, the same problems keep showing up. Here’s what you’re probably dealing with:
Low Contrast Text
Light gray text on a white background looks clean in a Figma mockup. It fails contrast requirements and it’s genuinely hard to read, for users with low vision and for anyone trying to read on a phone in sunlight. Your brand colors might need to be adjusted for web use.
Images Without Alt Text
Screen readers hit an image with no alt text and either skip it silently or read out the filename. “IMG_4892.jpg” is not a meaningful brand experience. Every image needs descriptive alt text, decorative images get an empty alt attribute to tell screen readers to skip them intentionally.
Keyboard Traps
Modal dialogs, custom dropdown menus, and video players that can’t be controlled with a keyboard lock out users who can’t use a mouse. This is one of the most common failures in modern JavaScript-heavy sites.
Auto-Playing Video with No Controls
Autoplay video with sound on page load is a WCAG failure. It’s also annoying. This one’s easy to fix and a surprisingly common problem on agency-built hero sections.
Forms With No Labels
Placeholder text is not a label. When the placeholder disappears on click, users with cognitive disabilities, and users who just paused to think, lose the context for what they’re filling in. Every input needs a persistent, programmatically associated label.
How to Approach a WCAG Compliance Audit
An accessibility audit has two layers: automated and manual. Automated tools (WAVE, axe, Lighthouse) catch about 30-40% of WCAG issues. The rest require human testing, keyboard navigation, screen reader testing (NVDA on Windows, VoiceOver on Mac/iOS), and judgment calls about cognitive clarity.
Here’s a realistic process:
- Run automated tools across your highest-traffic pages. Fix the obvious failures first.
- Audit manually using just a keyboard. Can you reach and activate every interactive element?
- Test with a screen reader. Is the reading order logical? Are interactive elements announced correctly?
- Review content for reading level, clarity, and plain language where appropriate.
- Document your conformance. An accessibility statement on your site demonstrates good faith and is required under the EAA.
Our web design and development work builds WCAG compliance in from the start, not as a retrofit. If you’re planning a redesign, this is the right moment to get it right. And if you’re not planning one, our full service offering includes accessibility audits as a standalone engagement.
For the full picture on what modern web design requires, our complete guide to web design covers the technical and creative standards we build to in 2026.
The Overlay Widget Problem
You’ve probably seen the pitch: install our widget, add one line of JavaScript, and your site is instantly WCAG compliant. These tools, AccessiBe, UserWay, and a dozen competitors, are everywhere, and they don’t work the way they claim.
The National Federation of the Blind, the American Council of the Blind, and over 700 disability rights organizations signed an open letter explicitly opposing these tools. Automated overlays can’t fix structural HTML problems, can’t create accurate alt text, and can actively interfere with the assistive technology users already rely on.
Overlay widgets are also not a legal defense. Courts and regulators have not accepted them as proof of compliance. Don’t waste the money.
Frequently Asked Questions
Does my small business website need to be WCAG compliant?
If you operate in the EU or serve EU customers, the European Accessibility Act applies to you, with some size-based exceptions for micro-enterprises (under 10 employees and under €2M in revenue). In the US, ADA risk applies to businesses open to the public, and courts have broad latitude in how they define that. The short answer: if your site generates revenue, it’s worth getting compliant.
How long does it take to make a website WCAG compliant?
It depends heavily on how inaccessible the site currently is. A well-structured site with minor issues might take two to four weeks of remediation. A site built with inaccessible patterns baked in, poorly structured templates, custom JavaScript components, no semantic HTML, can take significantly longer, or warrant a rebuild rather than a retrofit.
What’s the difference between WCAG 2.1 and WCAG 2.2?
WCAG 2.2 was published in October 2023 and adds nine new success criteria, with a focus on cognitive accessibility and mobile usability. The EAA currently references WCAG 2.1 AA as the minimum standard, but WCAG 2.2 is the current version and building to it future-proofs your compliance posture. We build to 2.2 by default.
Accessibility isn’t a feature. It’s a foundation. If your site was built without it, you’re not running a website, you’re running a liability. Let’s talk about what compliance actually looks like for your business and what it takes to get there properly.