European Accessibility Act Compliance in Ireland — The 2026 Catch-Up Guide

What the EAA actually requires

The EAA — EU Directive 2019/882, transposed in Ireland in 2023 — sets accessibility requirements for a defined list of products and services. For digital services, the technical standard is the Web Content Accessibility Guidelines (WCAG) 2.1 at conformance level AA. In plain language: most B2C websites and apps that fall in scope must be navigable by keyboard, compatible with screen-readers, readable at 200% zoom, sufficiently colour-contrasted, and properly structured for assistive technology.

Who's in scope

The EAA applies to:

• E-commerce websites and apps — anywhere a consumer can buy a product or service online.
• Banking services — consumer banking, including mobile banking apps.
• Telecoms — phone and internet service providers' customer-facing digital services.
• Transport ticketing — air, rail, bus and ferry booking sites.
• Audio-visual media services — streaming platforms and broadcaster on-demand services.
• E-books and e-readers.
• Self-service terminals — ATMs, ticket machines, check-in kiosks.
• Some hardware products — computers, smartphones, smart-TVs sold to consumers.

Who's exempt

• Microenterprises providing services — fewer than 10 employees AND turnover or balance-sheet under €2 million. (Note: micro-enterprises selling in-scope products are not exempt — only services.)
• Disproportionate-burden defence — businesses can argue compliance would impose a disproportionate burden, but this requires documented justification and the burden is on the business to prove.
• Pure B2B services — the EAA targets services for consumers; pure-B2B services are outside scope (though sector-specific accessibility rules may still apply).

Enforcement in Ireland

Multiple regulators carry enforcement responsibilities depending on the sector:

• Competition and Consumer Protection Commission (CCPC) — market surveillance for in-scope products, and the lead authority for general service compliance.
• ComReg — telecoms.
• Central Bank of Ireland — banking and financial services.
• National Transport Authority — passenger transport ticketing.
• Coimisiún na Meán — broadcast and audio-visual media.

Penalties scale with seriousness; the headline figures (€100,000 or 4% of annual revenue) are the upper bracket. Smaller breaches attract proportionate response.

What WCAG 2.1 AA actually means in practice

WCAG 2.1 AA covers approximately 50 success criteria. The most commonly-failed-on-Irish-websites criteria, in our experience, are:

• 1.4.3 Contrast (Minimum) — body text needs 4.5:1 contrast ratio against its background. Light-grey-on-white body text fails routinely.
• 1.4.11 Non-text Contrast — UI components (buttons, form fields) need 3:1 minimum against adjacent colours. Pale buttons fail this.
• 2.4.7 Focus Visible — keyboard focus needs to be visually apparent. CSS resets that strip focus styles fail.
• 3.3.2 Labels or Instructions — form fields need persistent labels (not just placeholder text). Many modern designs use placeholder-only fields and fail.
• 2.1.1 Keyboard — everything must be operable via keyboard. Hover-only menus fail.
• 4.1.2 Name, Role, Value — custom components (carousels, accordions, modals) must be exposed correctly to assistive technology. ARIA misuse is the most common failure here.
• 1.3.1 Info and Relationships — semantic structure must be machine-readable. Sites using divs everywhere instead of headings, lists, and landmarks fail.
• 1.4.4 Resize text — text must reflow at 200% zoom without loss of functionality.

The catch-up sequence (10 months past deadline)

1. Audit now. A WCAG 2.1 AA audit takes 2-3 weeks. The longer you defer, the longer your exposure window. Our accessibility audit service handles this.
2. Publish an Accessibility Statement. The EAA expects in-scope businesses to publish a statement on their website outlining the standard they conform to, where they fall short, and how to contact them about issues. We provide a template ready to publish as part of the audit deliverable.
3. Triage and remediate. Critical-severity issues first (anything blocking access), serious next (anything causing significant difficulty), moderate after (degraded experience), cosmetic last. Most sites have 5-10 critical issues, 15-30 serious, and a long tail of moderate.
4. Document the work. Keep a remediation log: finding, severity, fix shipped, date. This is the evidence that demonstrates reasonable effort if the CCPC ever enquires.
5. Build accessibility into your release process. One-off audits get expensive if you don't change how you build. We recommend automated WCAG checks in CI, plus a manual review checklist for new templates.

Common false reassurances we see

• "We ran an automated scanner and got 95% — we're fine." Automated tooling reliably catches about 30% of WCAG 2.1 AA criteria. The remaining 70% require human evaluation.
• "Our agency said it's accessible." Sometimes true. Often "accessible" means "looks fine to the agency," not "tested with assistive technology against the standard." Ask for the audit report.
• "We'll add an overlay widget." Accessibility overlays do not bring sites into compliance with WCAG. Several have been the subject of legal action in the US for the opposite reason. Don't rely on them.
• "Our site is mostly text — accessibility doesn't really apply." WCAG covers far more than alt text. Keyboard navigation, focus management, semantic structure, contrast, error messaging, form labelling — all apply to text-heavy sites.

How to commission an audit

Our accessibility audit service covers WCAG 2.1 AA evaluation, an Accessibility Statement template, and a 30-day Q&A window with the auditor. Engagement runs 2-3 weeks for typical SMB sites; €1,500-€4,500 depending on scope. Where remediation requires design or development changes, our sister studio digitaldesign.ie handles implementation under a continuation engagement.

Read next

• Accessibility audit service details
• Heuristic audit vs usability testing — sequencing UX evaluations
• Eight UX patterns that quietly kill conversion

← All insights