Get Basic Free
Home / Blog / EAA & WCAG 2.2 Compliance

European Accessibility Act (EAA) & WCAG 2.2 Compliance Checklist for Joomla & WordPress Stores

A practical, legally sound roadmap for meeting mandatory EU accessibility directives, eliminating non-compliant HTML in TinyMCE, and automating your Accessibility Statement.

By FlexExt Architecture Team • Published Oct 26, 2026 • 8 min read • EU Directive 2019/882
🎬 Video Walkthrough: FlexExt EAA Guard & WCAG 2.2 AA Pro for Joomla & WordPress Watch Full Playlist on YouTube →
Also watch the WordPress & WooCommerce EAA Guard walkthrough: https://youtu.be/SUBoqBBA9hA • Open on YouTube (EN & PL Subtitles)

Under the European Accessibility Act (Directive 2019/882), all online commerce websites and digital services serving EU citizens must strictly adhere to WCAG 2.2 Level AA standards. Failure to comply can result in administrative fines reaching €100,000 or complete injunctions against operating storefronts.

The "Overlay Trap": Why Quick Widgets Fail Legal Audits Many merchants rely on client-side JavaScript overlay widgets that claim "1-click compliance". National enforcement authorities across the EU (such as DIN in Germany and PFRON/Ministerstwo Cyfryzacji in Poland) have clarified that overlays do not fix structural document deficiencies, broken keyboard navigation, or inaccessible downloadable PDF invoices.

The 6 Mandatory Steps for EAA Compliance

1. Pre-Publish Validation in the CMS Editor

Preventing inaccessible content is exponentially cheaper than remediating legacy catalog databases. By utilizing a Pre-Publish Gatekeeper in TinyMCE (Joomla) or Gutenberg (WordPress), content creators are immediately notified if:

  • Images lack descriptive, contextual alt text.
  • Color contrast ratio falls below 4.5:1 for normal text or 3.0:1 for interface components.
  • Heading hierarchy skips levels (e.g. jumping from <h2> to <h4>).
  • Tables lack proper <th scope="col"> semantic row and column headers.

2. Fully Accessible Checkout & Form Fields

Every input in the checkout flow must have an explicitly paired <label for="..."> or aria-labelledby. Avoid floating labels that vanish when focused, and ensure clear, persistent error messaging that screen readers announce immediately via aria-live="polite".

3. Structural PDF Invoice Accessibility (PDF/UA)

E-commerce receipts, downloadable product manuals, and automated tax invoices fall under the EAA's digital product scope. PDFs must feature tagged structure trees, document titles, language declarations, and accessible font embedding.

4. Automated Accessibility Statement (Deklaracja Dostępności)

The law mandates a publicly accessible statement detailing compliance status, contact information for feedback, and formal enforcement escalation channels.

Frequently Asked Questions

Who must comply with the European Accessibility Act (EAA)? ▼

Any e-commerce store operating within or selling to consumers in the European Union with 10 or more employees or annual revenue exceeding €2 million must comply with the EAA (Directive 2019/882) under WCAG 2.2 Level AA standards.

Why are superficial JavaScript accessibility overlay widgets insufficient? ▼

Third-party JS overlay widgets do not fix underlying HTML semantic issues, missing alt attributes in database tables, broken form labels, or inaccessible downloadable PDF invoices, and are specifically criticized by European accessibility regulatory bodies.

How does a Pre-Publish Gatekeeper solve the accessibility problem? ▼

A Pre-Publish Gatekeeper inspects WYSIWYG editor content in real time before article or product saving. It blocks inaccessible contrast, missing table headers, empty link anchors, and missing alt text before invalid HTML ever reaches the database.