EAA compliance for Joomla: WCAG 2.1 AA checklist & fixes

What the EAA actually requires from a Joomla site

Joomla 4 built an accessibility checker into the editor and ships the reasonably accessible Cassiopeia default template, so under the EAA the residual obligation is concentrated in third-party templates and modules that reintroduce WordPress-style markup soup. EN 301 549 conformance forces you to audit premium templates and any module that emits its own markup outside Joomla's checks, since those are where headings, landmarks, and labels go missing. The requirement is effectively to keep the rendered public site at AA with all your installed extensions active, not just the clean core install.

Joomla is disproportionately used by EU education, government, and non-profit organisations, so many in-scope Joomla sites are public bodies that also fall under the Web Accessibility Directive and EN 301 549 procurement rules layered on top of the EAA. For those public-sector operators the driver is often mandatory compliance reporting rather than a commercial fine, while non-profit and SMB Joomla sites face fixed national penalties at the moderate end. The practical risk is that a branded premium template was chosen for looks and quietly bypasses the accessibility checker the platform provides.

Remediation is handled by a Joomla administrator or developer who sticks to Cassiopeia or an accessibility-tested template and customises through template overrides and CSS rather than editing markup directly. Overriding CSS instead of HTML preserves the accessible structure while allowing branding, and every third-party module should be audited in its production configuration. This is generally a modest engagement for a Joomla-familiar developer, with the built-in Joomla 4 checker used continuously during content editing.

Top WCAG failures we see on Joomla sites

Across hundreds of Joomla scans, the same handful of issues show up over and over. None of them require ripping the theme apart — most are fixable in a few hours by someone comfortable in the platform's editor or template files.

• Third-party templates ignoring the accessibility checker

  Premium templates often add custom modules with their own markup that bypasses Joomla's checks.

  1.3.1 — Level A

Concrete code fixes for Joomla

Below are copy-paste fixes for the most common Joomla issues. They assume you have access to your theme code or the platform's custom-code injection panel. If you cannot edit code directly, share these snippets with whoever maintains the site — every one of them is a ten-minute change.

// System → Templates → Cassiopeia (default).
// Use template overrides for branding without overriding markup.

Tools and plugins worth installing first

• Joomla 4 built-in accessibility checker

How to scan a Joomla site without missing anything

Automated scanners catch about 30–40% of WCAG issues; the rest need manual review. The good news is that the 30–40% includes the most expensive issues to remediate after the fact, so an automated scan is the cheapest way to get unstuck. Run one before you change a line of theme code.

• Audit with all third-party modules enabled in production order.