Web Accessibility Services WCAG 2.2: Audit and Remediation for EAA
The European Accessibility Act (EAA) has applied since June 28, 2025 to consumer digital products and services, e-commerce included. Each member state sets its own penalties: in Germany, the BFSG allows fines of up to €100,000. Overlays are not a solution: the FTC fined accessiBe $1M USD. Only expert manual remediation guarantees real compliance.
- 94.8% Websites Fail WCAG
- 01 · Requirements What the business needs
- 02 · Architecture Documented decisions
- 03 · Code Reviewed and tested
- 04 · Deployment Automated and reversible
- 05 · Performance Core Web Vitals in the green
- 06 · Evolution Your team asks, we deliver
- Every metric sets the next iteration
In numbers
Web Accessibility by the Numbers
Real data that justifies acting now.
- €100K Max Fine (BFSG) Set by Germany; each member state defines its own penalties
- $3.24B Market Size 2034 Up from $1.42B in 2025 (8.6% CAGR)
- 100+ Lawsuits Over Overlays Companies sued for using overlays instead of remediation
What's included
What Our Service Includes
Genuine remediation, not cosmetic patches.
- Full WCAG 2.2 AA audit: automated scanning + expert manual review of every Level A and AA criterion
- Code remediation: fixing semantic HTML, ARIA, contrast, keyboard navigation, and screen reader compatibility
- Continuous monitoring: monthly automated scans + quarterly manual audit to maintain compliance
- Accessibility statement: legal document conforming to EN 301 549 for EAA compliance
- Team training: hands-on workshops for designers, developers, and content creators
- Design system review: accessible components from the ground up: colors, typography, forms, modals
Why
Manual Remediation vs Overlays: Why Shortcuts Don't Work
Accessibility overlays are a proven legal risk.
In January 2025, the FTC fined accessiBe $1 million USD for deceptive advertising. Over 100 companies have been sued for using overlays as a substitute for real remediation. Overlays add a JavaScript layer that tries to "fix" issues on the fly, but: they don't fix broken semantic HTML, they interfere with screen readers like NVDA and JAWS, they create false positives in audit tools, and they add page weight. Automated tools only catch 30-40% of accessibility barriers. The rest requires manual review by experts who navigate with keyboards, screen readers, and real assistive devices.
- 100+ Lawsuits Against Overlays
- $1M USD FTC Fine Against accessiBe
Definition
What Is Web Accessibility and Why the EAA Changes Everything
Web accessibility ensures that all people, including those with disabilities, can perceive, navigate, and interact with websites and web applications. The international standard is WCAG 2.2 Level AA, built on four principles: Perceivable, Operable, Understandable, and Robust (POUR).
Summary
Executive Summary
What you need to know to decide.
The European Accessibility Act (EAA) has applied since June 28, 2025. Penalties are set by each member state in its national transposition: in Germany, the BFSG allows fines of up to €100,000. National authorities are already implementing enforcement and penalty mechanisms.
Beyond legal compliance, accessibility is a competitive advantage: 15% of the population has a disability, accessible sites rank better in search (Google rewards semantic HTML), and usability improvements benefit all users. The accessibility remediation market is growing at 8.6% annually to reach $3.24 billion by 2034.
- €100K Max Fine (BFSG)
- 15% Population With Disability
- 8.6% Market CAGR
For the CTO
Summary for CTO / Technical Team
Implementation requirements and standards.
WCAG 2.2 AA compliance requires: semantic HTML5 (landmarks, hierarchical headings, lists), correctly implemented ARIA (roles, states, properties, no redundant ARIA), full keyboard navigation (visible focus, no focus traps, skip links), and minimum 4.5:1 contrast for normal text (3:1 for large text).
Automated testing with axe-core and Lighthouse covers only 30-40% of WCAG criteria. The remaining 60-70% requires manual testing with screen readers (NVDA, JAWS, VoiceOver), keyboard navigation, and validation with real users with disabilities. We integrate accessibility tests into CI/CD with Playwright and Pa11y, as part of our QA automation service, to prevent regressions.
Technologies
- axe-core
- Lighthouse
- Pa11y
- WAVE
- NVDA
- JAWS
- VoiceOver
- TalkBack
- Playwright
- Cypress
- Semantic HTML5 with correct ARIA landmarks
- Full keyboard navigation without focus traps
- WCAG AA contrast (4.5:1 text / 3:1 large text)
- Accessibility tests integrated into CI/CD (axe + Playwright)
- Continuous monitoring with monthly automated scans
Who it is for
Is It Right for You?
The EAA applies to nearly every company selling digital products or services in the EU.
Who it's for
- E-commerce businesses selling to EU consumers (direct EAA obligation).
- Banking, insurance, and online financial services.
- Telecommunications and communication service providers.
- Public sector entities already required to comply with EN 301 549.
- Any company with a website or app serving European consumers.
- Organizations looking to expand their market to the 15% of the population with disabilities.
Who it's not for
- Micro-enterprises with fewer than 10 employees and revenue under €2M (exempt under the EAA).
- Internal tools without external consumer access.
- Pre-recorded audiovisual content created before the law took effect (legacy content exempt).
Key points
Service Packages
Solutions tailored to every maturity stage.
- 01
Quick WCAG Audit
Analysis of the 5 most visited pages against WCAG 2.2 AA. Report with severity, user impact, and remediation effort estimate. Ideal for establishing your baseline.
- 02
Full Audit + Remediation
Comprehensive site-wide audit (automated + manual). Code remediation by our developers: semantic HTML, ARIA, keyboard, contrast, forms, multimedia content. Includes post-fix re-testing.
- 03
Continuous Monitoring
Monthly automated scans + quarterly manual audit. Early warning on regressions caused by content updates or new features. Compliance report for regulatory audits.
- 04
Accessibility Training
Hands-on workshops for design, development, and content teams. How to build accessible components from scratch, write effective alt text, and test with screen readers.
- 05
Design System Review
Audit of your component library (Storybook, Figma). We ensure every component (buttons, modals, forms, navigation) is accessible by default before it reaches production.
How we work
Work Process
From diagnosis to verified compliance.
- 01
Audit
Automated scanning with axe-core, Lighthouse, and Pa11y + expert manual review with screen readers (NVDA, JAWS, VoiceOver), keyboard navigation, and contrast validation. Report detailing each barrier, WCAG severity, and affected users.
- 02
Prioritization
We classify each barrier by user impact + legal risk + remediation effort. Level A barriers (basic perceivability, keyboard navigation) come first. We deliver a prioritized roadmap.
- 03
Remediation
Our developers fix the code: semantic HTML, ARIA attributes, focus management, contrast, alt text, captions. Re-testing after each sprint to validate corrections.
- 04
Monitoring
Automated tests integrated into CI/CD to prevent regressions. Monthly scans + quarterly manual audit. Accessibility statement updated per EN 301 549.
Risks and how we cover them
Risks We Mitigate
From legal exposure to verified conformance.
- 01
EAA non-compliance fines (up to €100,000 in Germany)
MitigationFull WCAG 2.2 AA audit + remediation + accessibility statement per EN 301 549. Compliance documentation for regulatory audits.
- 02
Overlay dependency (lawsuit risk)
MitigationOverlay removal and genuine source code remediation. Fixing semantic HTML, ARIA, and navigation that automated tools cannot patch.
- 03
Regressions after updates
MitigationAccessibility tests integrated into CI/CD with axe-core and Playwright. Monthly automated scans + quarterly manual audit to catch new barriers.
- 04
Team lacks accessibility knowledge
MitigationHands-on training for designers, developers, and content creators. Accessible component guidelines integrated into the design system.
Technologies
Tools and Standards
Professional accessibility technology.
- axe-core
- Lighthouse
- Pa11y
- WAVE
- NVDA
- JAWS
- VoiceOver
- TalkBack
- Playwright
- Cypress
- WAI-ARIA
- Semantic HTML5
- WCAG 2.2
- EN 301 549
- Siteimprove
- Color Contrast Analyzer
The proof
Real Web Accessibility Experience
Since 2009 we've been building websites with accessibility standards. Our development team has deep expertise in semantic HTML, ARIA, and testing with assistive technology. We're not consultants who deliver PDFs: we're developers who fix the code and verify with real screen readers.
- 15+ Years in Software Development
Why
Accessibility and SEO: Two Sides of the Same Coin
An accessible website ranks better in Google.
Google rewards semantic HTML, correct heading structure, image alt text, and fast load times: exactly what WCAG demands. Accessible sites score higher on Core Web Vitals, have lower bounce rates, and achieve greater time on site. A Semrush study found that WCAG AA-compliant websites receive an average of 12% more organic traffic than their non-compliant competitors. If you are redesigning your site, our web design team applies WCAG from the first wireframe.
- AA WCAG 2.2
- +12% SEO
- Pass Keyboard
FAQ
Frequently Asked Questions
What companies ask about web accessibility and the EAA.
What is the European Accessibility Act (EAA)?
The EAA (Directive 2019/882) is the European accessibility law, applicable since June 28, 2025. It requires companies offering digital products or services to EU consumers to meet harmonized accessibility requirements based on EN 301 549 (which references WCAG 2.1 AA as a minimum). It applies to e-commerce, banking, telecommunications, transport, and audiovisual services.
Who needs to comply with the EAA?
Any company that offers digital products or services to EU consumers, regardless of where the company is headquartered. This includes: online stores, digital banking, telecommunications platforms, transport services, and audiovisual services. Micro-enterprises (fewer than 10 employees and under €2M revenue) are exempt.
What is WCAG 2.2 and what level do I need?
WCAG 2.2 (Web Content Accessibility Guidelines) is the W3C international standard with 86 success criteria organized into three levels: A (minimum), AA (recommended), and AAA (optimal). Level AA is the legal reference in the EU: the EN 301 549 standard formally cites WCAG 2.1 AA, and auditing against WCAG 2.2 AA covers those criteria plus the 9 new ones added in 2.2. It covers four principles: Perceivable, Operable, Understandable, and Robust.
How is the EAA enforced in each EU country?
The EAA is a directive, so each member state transposes it into national law and sets its own penalties. Germany enforces it through the BFSG (fines of up to €100,000), France audits against the RGAA 4 framework, and Spain transposed it with Law 11/2023. EU digital regulation moves in parallel: if your company uses AI, see our EU AI Act compliance service.
Why shouldn't I use accessibility overlays?
Overlays (accessiBe, UserWay, AudioEye) are JavaScript layers that try to "fix" barriers on the fly, but: they don't fix broken semantic HTML, they interfere with screen readers, they create false positives in audits, and they add page weight. The FTC fined accessiBe $1M USD in January 2025 for deceptive advertising. Over 100 companies have been sued for using overlays as a substitute for real remediation.
How long does remediation take?
It depends on site size and complexity. A quick audit of 5 pages: 1-2 weeks. Full audit + remediation of a mid-sized site (50-100 pages): 6-10 weeks. Large sites or complex web applications: 3-6 months. We start with Level A barriers (the most critical) to reduce legal risk from the first sprint.
How much does it cost to make my website accessible?
Quick WCAG audit (5 pages): from €1,500. Full audit + remediation: from €5,000. Cost depends on site size, severity of existing barriers, and whether team training is included. Continuous monitoring: from €500/month. A significantly smaller investment than an EAA non-compliance penalty.
Do I need continuous monitoring?
Yes. Accessibility is not a one-time project. Every content update, new feature, or design change can introduce regressions. The EAA requires ongoing compliance, not just an initial audit. We recommend monthly automated scans + quarterly manual audit + CI/CD tests.
Does web accessibility affect SEO?
Yes, positively. Google rewards semantic HTML, correct headings, alt text, and load speed: the same elements WCAG requires. Accessible sites score higher on Core Web Vitals, have lower bounce rates, and achieve greater engagement. Studies show up to 12% more organic traffic for WCAG AA-compliant sites.
What about mobile app accessibility?
The EAA also covers mobile applications. The principles are the same (WCAG + mobile-specific requirements from EN 301 549): alternative gestures, minimum 44x44 px touch target size, VoiceOver (iOS) and TalkBack (Android) compatibility, and flexible screen orientation. We audit and remediate web, native, and hybrid apps.
What's included
Investment
Proposal tailored to your current compliance level.
- Quick WCAG audit (5 pages): from €1,500
- Full audit + remediation: from €5,000
- Continuous monitoring: from €500/month
- No lock-in: cancel with 30 days notice
Next step
The EAA Has Applied Since June 28, 2025: Catch Up Now
94.8% of websites fail WCAG. Overlays are not a solution. Request an accessibility audit and find out where your site really stands.
- No commitment
- Response in 24h
- Custom proposal
Case studies
Projects where we put it to work
Teatre Nacional de Catalunya
Institut de Cultura de Barcelona
Fundació Ampans
Let's talk.
Initial technical consultation
AI, security and performance. Diagnosis with phased proposal.
- NDA available
- Response <24h
- Phased proposal
Your first meeting is with a Solutions Architect, not a salesperson.
Request diagnosis