BLOG · TYPO3 · BITV · EAA

TYPO3 Accessibility:
Meeting BITV 2.0 and EN 301 549

A practical compliance workflow for agencies running TYPO3 sites for German public-sector clients and EU businesses covered by the EAA.

Start Reading EAA Checklist Blog → →

Updated August 2026 · Reading time: 7 minutes

why-typo3-and-bitv

TYPO3 is heavily used in German-speaking public administration, and that changes what "accessible" means for you as an agency. German public-sector bodies must meet BITV 2.0, which is essentially EN 301 549 — the European ICT accessibility standard that incorporates WCAG 2.1 level AA. Since 28 June 2025, the European Accessibility Act extends similar obligations to private-sector e-commerce and banking services across the EU. A TYPO3 site built without a deliberate accessibility pass will typically fail several EN 301 549 requirements on every page — and public-sector clients increasingly demand a documented accessibility statement before they sign.

where-typo3-sites-fail

Most accessibility defects on TYPO3 sites come from three places: editor-entered content, template markup, and extensions.

📝 Editor Content

Missing alt text on uploaded images is the number one defect. TYPO3 does not enforce alt attributes on FAL file references, so editors routinely skip them. Second place: heading structure pasted from Word with visual formatting instead of real h2/h3 elements.

🧩 Templates & TypoScript

Custom Fluid templates often hardcode link texts like "read more" repeated across a page, skip the lang attribute, or render icon-only buttons without aria-labels. Base templates shipped years ago predate current standards.

🔌 Extensions

Third-party plugins (forms, sliders, lightboxes) frequently inject non-semantic markup, keyboard traps, or missing focus states. Every extension on the site needs its own accessibility review.

editor-level-fixes

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

1. Make alt text mandatory in practice. Configure the image content element workflow so editors must fill the alternative text field. For purely decorative images, an explicit empty alt="" is correct — train editors on the difference between decorative and informative images.

2. Enforce semantic headings. Restrict the header layout options editors can pick, so they choose real h2/h3 rather than styled text. Check Fluid templates render section headers as actual heading elements, not divs.

3. Write meaningful link texts. "More", "here", and repeated identical links pointing at different targets fail WCAG 2.4.4 and are hostile to screen-reader users navigating by link list. Editorial guideline: the link text should describe the destination even read out of context.

4. Language attributes. Set the site language correctly per page tree (TypoScript config.language / htmlTag_langKey or site configuration), and mark foreign-language words inline where practical. This maps directly to EN 301 549 clause 9.3.1.

5. Forms. Every input needs a programmatically associated label — not placeholder text. If you use a forms extension, verify its output markup, because many generate label-less fields by default.

template-and-technical-fixes

Developer-side, work through this list once per project and reuse the checklist everywhere:

Skip links: a visible "skip to content" link as the first focusable element.

Focus visibility: never remove outline globally; style :focus-visible instead.

Contrast: verify theme colours against 4.5:1 for body text and 3:1 for large text and UI components.

Keyboard operability: tab through every interactive component including menus, accordions, sliders and lightboxes. Anything mouse-only is a failure.

ARIA discipline: prefer native HTML elements over ARIA patches. A real button beats a div with role="button".

PDF documents: downloadable PDFs count under EN 301 549 too — tagged, readable PDFs or accessible HTML alternatives.

testing-workflow

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

Step 1 — automated scan. Run a static HTML scanner against your key page types (home, article, form, search results). It catches contrast failures, missing lang, broken heading order, empty buttons, duplicate IDs — roughly 30-50% of typical issues in minutes.

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

Step 3 — screen reader spot-check. Test one representative flow with NVDA or VoiceOver. You are listening for unlabelled controls and confusing structures, not doing a full audit.

Step 4 — document. Publish an accessibility statement listing conformance status, known limitations, and a feedback channel. Public-sector clients in Germany expect this; under the EAA, private services in scope must provide one too.

Going Deeper

Run the free scanner on your TYPO3 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 TYPO3 Site Free → → EAA Checklist Blog → →

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 TYPO3 itself accessible?

The TYPO3 core backend has made significant accessibility improvements in recent versions, and the CMS provides the tools needed (semantic rendering, language handling, FAL metadata). Compliance depends almost entirely on the specific template, extension set, and editorial practice on each site.

Which WCAG version do I target?

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

Do I need a certified audit?

Public-sector clients typically require a self-produced, documented assessment plus an accessibility statement; some procurement processes ask for independent audits. An automated scan plus manual keyboard/screen-reader testing is the accepted minimum internal standard.

How long does remediation take?

For a typical 20-50 page TYPO3 site with a maintained template: 2-5 working days for mechanical fixes plus editor retraining. Sites with old custom templates or heavy third-party extensions take longer — the template refactor usually dominates.