BLOG · JOOMLA · BITV · EAA

Joomla Accessibility:
Meeting BITV 2.0 and EN 301 549

Template overrides, editor habits and extension checks that bring a Joomla site up to WCAG 2.1 AA — for German public-sector clients and EAA-covered businesses.

Start Reading Joomla Guide → →

Updated August 2026 · Reading time: 7 minutes

why-joomla-and-bitv

Joomla remains widely deployed in German public administration, education associations and Mittelstand websites — audiences governed by BITV 2.0 in Germany and, since June 2025, by the European Accessibility Act across the EU. BITV 2.0 is essentially EN 301 549, the European ICT accessibility standard incorporating WCAG 2.1 level AA. A Joomla site built without a deliberate accessibility pass will typically fail several EN 301 549 requirements on every page — and German public-sector clients increasingly require a documented accessibility statement before signing a contract.

🏛️ Public-Sector Clients

German public bodies must meet BITV 2.0. Agencies serving them need documented conformance, not good intentions.

📜 BFSG for Private Sites

Private-sector services fall under the BFSG (the German EAA implementation) — same technical standard, different legal route.

🧱 Template Inheritance

Most Joomla sites run heavily customised descendants of old Protostar-based templates — decade-old markup patterns replicate site-wide.

where-joomla-sites-fail

Most accessibility defects on Joomla sites come from three places:

📝 Editor Content

Missing alt text is the number one defect — Joomla does not enforce the alt field on media. Second: headings pasted from Word as visual formatting instead of real h2/h3 elements.

🧩 Templates & Overrides

Old templates skip landmark elements, render icon-only buttons without aria-labels, and repeat identical "read more" link texts across every article teaser.

🔌 Extensions

Forms, galleries, sliders and forum extensions frequently inject non-semantic markup, keyboard traps or missing focus states. Every extension needs its own review.

editor-and-config-fixes

These fixes need no developer and cover much of your defect volume:

1. Alt text discipline. Train editors: informative images get descriptive alt text, decorative images get explicit empty alt="". Joomla's media manager allows both — it just does not require them.

2. Semantic headings. Restrict the editor's allowed formats so articles use real Heading 2/3 styles, not bold paragraph text. Check the article view's template override renders titles as actual heading elements.

3. Meaningful "Read more" links. Configure the global Read More text to include the article title ("Read more: {title}") — repeated identical links fail WCAG 2.4.4 and wreck screen-reader link lists.

4. Language attributes. Set the content language correctly per site/multilingual association so matches the page. This maps directly to EN 301 549 clause 9.3.1.

5. Forms. Every field needs a programmatically associated label — verify whatever form extension you use outputs real label elements, not placeholder-only fields.

template-and-extension-fixes

Developer-side work, once per project and reused everywhere:

Modernise the base: if the template still descends from Protostar-era markup, migrate to a current bootstrap-based or custom template with proper landmarks (header, nav, main, footer).

Skip links and focus: a visible "skip to content" link as the first focusable element; never remove outlines globally — style :focus-visible instead.

Keyboard operability: tab through menus, accordions, sliders and lightboxes. Anything mouse-only is a failure under EN 301 549.

Extension audit: test each third-party extension's widgets individually; replace or wrap the ones that fail rather than shipping known-broken components.

Contrast and documents: verify theme colours against 4.5:1 body-text minimum, and treat downloadable PDFs as in scope — tagged, readable PDFs or accessible HTML alternatives.

testing-and-documentation

A realistic verification loop for a Joomla project takes one afternoon:

Step 1 — automated scan. Run a static scanner against key page types (home, article, contact form, category listing). It catches contrast failures, missing lang, broken heading order, empty buttons and duplicate IDs in minutes.

Step 2 — keyboard walkthrough. Unplug the mouse and navigate every flow a user would. Note anything unreachable, trapped, or with invisible focus.

Step 3 — screen reader spot-check. One representative flow with NVDA — listening for unlabelled controls and confusing structure, not doing a full audit.

Step 4 — document. Publish an accessibility statement listing conformance status, known limitations and a feedback channel. BITV public-sector clients expect it; the BFSG requires it for private services in scope.

Going Deeper

Run the free scanner on your Joomla site first — it catches the mechanical WCAG issues (contrast, lang, headings, labels) in seconds so you can spend expert time on the judgement calls.

Scan Your Joomla Site Free → →    Joomla Guide → →

Frequently Asked Questions

Does BITV 2.0 apply to my commercial client?

BITV 2.0 binds German public-sector bodies. Private companies fall under the Barrierefreiheitsstärkungsgesetz (BFSG), which implements the EAA — but both reference EN 301 549 / WCAG-based requirements, so the same technical work satisfies both frameworks.

Is Joomla itself accessible?

The Joomla core backend has improved significantly, and the CMS provides the tools (semantic rendering, multilingual associations, media metadata). Actual compliance depends almost entirely on the specific template, extension set and editorial practice on each site.

Which WCAG version should we target?

EN 301 549 currently references WCAG 2.1 Level AA. Building toward WCAG 2.2 AA gives headroom — its additions mostly concern focus appearance, dragging alternatives and consistent help.

We use a popular forms extension — are we fine?

Not automatically. Several widely-used form extensions output placeholder-only fields or custom select widgets without keyboard support. Audit your exact installed version's rendered markup on staging.

How long does a Joomla remediation take?

For a typical 20-50 page site on a maintained template: 2-5 working days for mechanical fixes plus editor training. Sites still on Protostar-era templates take longer — the template migration dominates.

Scan Your Joomla Site Free → →    Joomla Guide → →

Related Guides

TYPO3 · BITV

TYPO3 Accessibility: Meeting BITV 2.0 and EN 301 549

DRUPAL · WCAG

Drupal Accessibility: WCAG and EAA Compliance Guide

EAA CHECKLIST

EAA Accessibility Checklist for Agency Websites