EU Accessibility Act 2026: compliance for non-EU sites

The European Accessibility Act has been in force since June 28, 2025, and enforcement is intensifying throughout 2026 as national market-surveillance authorities staff up. The EAA requires digital accessibility conformance with WCAG 2.2 Level AA across e-commerce, banking, transport, communications, and digital services for any business serving EU consumers — regardless of where the business itself is headquartered. Fines run up to €3 million per member state. French disability advocacy groups filed emergency injunctions against major retailers in November 2025. This is the most aggressively enforced accessibility regulation in history, and most US-based brands are still treating it as a future problem.

This post is the operator’s compliance guide: what the EAA actually requires, who it applies to (including non-EU businesses with EU customers), the practical WCAG 2.2 AA conformance work, and the 60-day audit checklist for a typical SMB marketing site.

Who the EAA applies to (including non-EU companies)

The reach of the EAA is broader than most US operators realize:

Any business selling products or services to EU consumers
Includes e-commerce, banking apps, transport booking, communications platforms, e-readers, and digital services
Applies whether or not you have a physical EU presence
Applies to all 27 member states with shared technical standards

If a US-based DTC brand accepts orders from an EU customer, the EAA applies. The ship-to address is the test, not the company’s HQ. The same applies to SaaS products with EU users, fintech apps available in EU jurisdictions, and media subscription products.

A narrow exemption exists for microenterprises (under 10 employees and under €2 million annual turnover) selling services. The exemption does not apply to e-commerce or to companies above either threshold.

What the EAA actually requires (in operator terms)

The technical foundation is EN 301 549, which currently references WCAG 2.1 Level AA and is being updated to WCAG 2.2 Level AA during 2026. For practical purposes, design and build to WCAG 2.2 AA — that gets you compliant today and stays compliant when the EN 301 549 update lands.

The categories of requirements that hit marketing and product teams:

Perceivable — content presented in ways users can perceive (text alternatives, captions, sufficient contrast)
Operable — interface components users can navigate (keyboard navigation, no seizure-inducing animation, sufficient time to read)
Understandable — content and operation users can comprehend (predictable navigation, clear errors, input assistance)
Robust — content that works with current and future assistive technologies (semantic HTML, ARIA used correctly)

WCAG breaks these into 50+ success criteria. The ones that matter most for typical marketing sites are below.

The high-impact WCAG 2.2 AA criteria for marketing sites

If you have to prioritize, the criteria that most marketing sites fail and that drive the most enforcement action:

Text alternatives and ARIA labels

Every meaningful image needs a text alternative. Every interactive component needs an accessible name. The audit checks:

All product images, icons, and infographics have descriptive alt text (decorative images get alt="")
Form fields have associated labels (not just placeholder text)
Buttons and links have visible text or aria-label when the visible text is unclear
Custom components (carousels, modals, dropdowns) have correct ARIA roles, states, and properties

Color contrast

Text needs sufficient contrast against its background:

Normal text: 4.5:1 minimum
Large text (18pt+ or 14pt+ bold): 3:1 minimum
UI components and graphics: 3:1 minimum

The two biggest violations on marketing sites in 2026: light-gray secondary text on white backgrounds, and brand-colored buttons with insufficient contrast on hover states.

Every interactive component must be operable with the keyboard alone:

Focus order matches visual order
Focus indicators are visible (the dotted outline browsers add by default is the minimum)
No keyboard traps (a user can navigate into and out of every component)
Modal dialogs trap focus while open, return focus to the trigger on close

This is the criterion most React and Webflow sites fail. Custom components built without keyboard handling are the single most common EAA violation.

Heading structure and semantic HTML

Pages need a logical heading hierarchy and meaningful semantic markup:

One <h1> per page
Heading levels do not skip (no <h2> followed directly by <h4>)
<nav>, <main>, <aside>, <footer> used as semantic landmarks
<button> for buttons (not styled <div> or <a>)
Forms use <form> and fields use proper input types

Form errors and instructions

When a form submission fails, errors must be:

Identified clearly in text (not just color)
Associated with the relevant field (via aria-describedby or visible labels)
Suggested fixes, where the error is determinable (e.g., “Email must contain @“)

Media captions and transcripts

Videos with audio require captions. Audio-only content requires a transcript. Live video requires captions in near real-time. The exemption: media used purely for decoration (e.g., a background video loop with no information content) is exempt.

The 60-day SMB compliance plan

For a typical SMB marketing site that has never been audited:

Days 1-14: Discovery and audit

Run automated audits with axe DevTools, WAVE, or Lighthouse accessibility
Manual keyboard navigation test of every primary user flow
Screen reader test with NVDA (free, Windows) or VoiceOver (built into macOS)
Document violations by severity and page count

Days 15-35: Implementation — high-impact fixes

Add alt text to every meaningful image (auto-tools can suggest; humans must verify)
Fix color contrast violations in the design system (paint colors, not page-by-page patches)
Replace styled <div> buttons with <button> elements
Add labels to form fields that only have placeholders
Ensure keyboard focus indicators are visible (do not remove the default outline)

Days 36-50: Implementation — structural fixes

Restructure heading hierarchy where it’s inconsistent
Add <nav>, <main>, <aside>, <footer> landmarks
Add captions to video content (or remove video that cannot be captioned)
Make modals, carousels, dropdowns keyboard-accessible

Days 51-60: Verification and disclosure

Re-run automated audits, expect 80-95% improvement
Manual re-test of primary user flows with keyboard and screen reader
Publish an accessibility statement on your site (required by the EAA)
Document the audit process and remediation work for your compliance file

Most SMBs complete this work in 60 days for €5,000-25,000 of development time, depending on starting state. The cost is dramatically lower than the potential €3M-per-state fine exposure, even before considering the SEO and conversion benefits.

How accessibility connects to broader marketing performance

Accessibility work is not just a compliance cost. It correlates strongly with SEO and conversion improvements because the same technical practices that produce accessible sites also produce sites that search engines and AI models can parse:

Semantic HTML is read by Google’s crawler the same way it’s read by screen readers
Image alt text is one of the strongest visual search ranking signals
Clear heading hierarchy improves content extraction by AI search engines
Form labels improve conversion rates by reducing user error
Keyboard navigation improves the experience for the 15-20% of users with motor or temporary impairments

Brands that ship accessibility-first design typically see 5-15% organic traffic lift over 6-12 months as a side benefit. The compliance work pays for itself before the fines.

Common 2026 mistakes

The patterns that fail in EAA compliance:

Treating it as a US ADA issue. The ADA is similar in spirit but the enforcement mechanism is different. EAA fines are larger and apply automatically to EU-facing sites.
Adding an “accessibility widget” as a fix. Overlay widgets (the floating accessibility menus that “fix” the site dynamically) are insufficient under the EAA and have been explicitly criticized by EU regulators.
Relying on automated audits alone. Automated tools catch 30-40% of violations. The other 60-70% require manual testing.
Auditing once and stopping. WCAG conformance is ongoing — every site change can introduce new violations. Build accessibility checks into the dev workflow.
Ignoring video and audio content. Captions and transcripts are often skipped because they are tedious. They are also frequently cited in enforcement actions.

FAQ

Does the EAA apply to my US-based business? Yes, if you sell products or services to EU consumers. The ship-to address determines applicability, not your HQ.

What if I block EU traffic entirely? That is the cleanest exemption. Geo-block by IP, do not accept EU billing addresses, and document the geo-block. This is what some smaller US e-commerce brands have chosen rather than remediate.

Does the EAA apply to my marketing site if I only ship physical products? The marketing site itself (any page that supports the e-commerce flow) is in scope. A purely informational site that does not transact is in a grayer area; the safer position is to assume conformance is required if you have any EU-facing user interaction.

How does this connect to the CPPA? They are separate regimes. CPPA is California privacy; EAA is EU accessibility. Compliance with one does not imply compliance with the other. Both apply concurrently to a US-based brand selling to EU and California consumers, which is most DTC brands.

Are there exemptions for static marketing sites? Limited exemptions for pre-2025 published content (e.g., a 2019 blog post) under “disproportionate burden” arguments, but the exemption is narrow and requires documentation. New content published after June 28, 2025 must conform.

How do I find a qualified accessibility auditor? Look for IAAP certifications (CPACC, WAS) and accessibility-specific consultancies. The major players (Deque, Level Access, AccessibleWeb, Siteimprove) all serve the SMB market. Expect $5,000-25,000 for an initial audit and remediation guidance on an SMB-sized site.

The honest 2026 framing

The EAA is the first accessibility regulation with teeth, and enforcement is real and accelerating. The good news: the technical work is well-defined (WCAG 2.2 AA), reasonably scoped (60-day audit for typical SMB sites), and produces collateral benefits in SEO and conversion. The bad news: most US-based brands have not yet started, and the enforcement window is closing fast — French and German regulators are auditing actively in 2026, and lawsuits are accumulating.

Treat this as a Q2 priority. Run the audit. Fix the high-impact items in the design system. Publish the accessibility statement. The cost is bounded; the exposure of not doing it is not.