European Accessibility Act
EAA compliance for Joomla: WCAG 2.1 AA checklist & fixes
Joomla 4 introduced an accessibility checker into the editor, and the default Cassiopeia template is reasonably accessible. Most remaining failures come from third-party templates and modules that replicate WordPress-style markup soup. ~2.5% of CMS market; common in EU education and government sites under EAA + EN 301 549.
- Category
- Content management system
- Standard
- WCAG 2.1 Level AA via EN 301 549
- Deadline
- 28 June 2025 (EU consumer services)
- Risk for B2C
- High — public-facing, consumer-billed
What the EAA actually requires from a Joomla site
The European Accessibility Act (Directive 2019/882) applies to consumer-facing online services from 28 June 2025. For a Joomla site selling to EU consumers, that means the storefront, checkout, account area, and any embedded payment flow have to meet WCAG 2.1 Level AA via the harmonised standard EN 301 549. Microenterprises with under 10 employees and below €2 million in turnover are exempt for services, but not for products.
Fines vary by member state. Germany caps individual penalties at €100,000; France can fine up to 4% of group turnover; Spain reaches €600,000 for serious or repeated breaches. None of those numbers are theoretical — market surveillance authorities have already started auditing storefronts in Germany and France in the run-up to enforcement.
In practice, the work breaks down into three buckets: theme-level fixes (focus styles, contrast, semantics), interaction-level fixes (carousels, modals, drawers, gallery widgets), and content-level fixes (alt text, headings, descriptive link text). The list below covers the Joomla-specific failure points we see most often during scans.
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.
Stick to Cassiopeia or accessibility-tested templates
// System → Templates → Cassiopeia (default).
// Use template overrides for branding without overriding markup.Override CSS instead of HTML; you keep the accessibility while customizing the look.
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.
Run a free public scan against any Joomla URL right now — no signup, results in 60 seconds.
Frequently asked questions
Is the default Joomla template (Cassiopeia) WCAG 2.1 AA?
Largely yes. Customize via CSS, not HTML overrides.
Other content management system platforms
EAA compliance for WordPress
Powers ~43% of the entire web; the largest single platform under EAA scope.
EAA compliance for Drupal
Powers ~1.5% of all websites; very popular in EU public sector and higher education under
EAA compliance for Ghost
A focused publishing CMS used by independent newsletters and media brands.
Find every accessibility issue on your site in 60 seconds.
Free public scan. No card. AI-generated fixes for every issue we find.