Does TYPO3 meet EN 301 549 out of the box?

The core aims to, but your site package, templates and extensions determine the final result. Only a test of the rendered pages tells you where you stand.

We run a public-sector TYPO3 site. What applies to us?

In the EU, Directive (EU) 2016/2102 requires WCAG 2.1 AA conformity, a published accessibility statement and a feedback mechanism. In Germany this is implemented via BITV 2.0.

How do I restrict editors to accessible heading levels?

Use page TSconfig to limit the header types available in content elements so editors can only pick H2–H4 below the automatic H1.

Can I scan without installing anything on our server?

Yes. The scanner fetches your public pages like any visitor — no extension, no server access, no data stored beyond the scan result.

What does the EAA change for private TYPO3 operators?

From 28 June 2025 e-commerce and consumer-facing digital services in the EU must be perceivable, operable, understandable and robust — in practice WCAG-aligned. Scanning is the fastest first check.

Free TYPO3 Accessibility Check (WCAG/EAA/BITV)

Why TYPO3 accessibility matters in the EU

TYPO3 powers a large share of German-speaking public-sector and enterprise websites, and BITV 2.0 / EN 301 549 obligations already bind many of its operators. TYPO3 has solid accessibility foundations (accessible backend, fluid-based templates), but real-world output depends on the integrator: content elements, custom Fluid templates and extensions frequently introduce missing labels, weak contrast and broken heading hierarchies. With the EAA extending duties to more private operators from June 2025, verification matters.

What gets checked

16 automated rules covering images, links, forms, headings, language, viewport, contrast, ARIA misuse, and more — mapped to real WCAG success criteria.

Instant results

Paste your URL, get a letter grade with every issue listed by severity. No account, no email, no waiting for an audit report.

Built for the EAA

The rule set targets what EU enforcement and enterprise procurement actually look at: WCAG 2.1 AA basics you can document today.

How to check your TYPO3 site

Open the free EAA/WCAG scanner.
Paste your TYPO3 URL — any published page: homepage, a product page, or a category listing.
Read your grade. Each finding shows the exact element and why it matters, so fixes are concrete, not vague advice.
Fix and re-scan. Most image-alt, heading, and form-label issues are fixed right inside TYPO3's editor or theme settings. Re-run the scan to confirm.
Copy the shareable link from the result page — useful when a client or colleague needs to see the findings.

Scan Your TYPO3 Site Now — Free

Common fixes in TYPO3

When your scan flags a failing rule, here is where to fix it:

Issue	Where to fix in TYPO3
Missing alt text on images	Every FAL image reference has an alt-text field in the media adjustment — fill it per language. For content images set it in the image properties of the content element.
Low contrast text	Fix in your site package's TypoScript constants / SCSS variables, then clear cache. Do not patch contrast inline per element — fix the variable once.
Missing heading structure	Header type is chosen per content element (Type dropdown). Audit pages where editors picked "Layout" headings instead of real H2/H3, and constrain choices in your pageTSconfig.
Missing form labels	EXT:form labels are configured in the form YAML definition — every field needs a label element, not just a placeholder.
Generic link text ("read more", "click here")	Replace hardcoded "more" links in Fluid templates with aria-label or visually hidden text carrying the page/item title.
Missing page language	Language is derived from the site configuration (sites.yaml). Verify each language tree sets the correct hreflang/lang value.
Skip link / keyboard navigation	Ensure your base Fluid layout includes a skip-to-content link and that extension output (news lists, menus) is reachable by keyboard in DOM order.

TYPO3-specific tools & resources

TYPO3 ships with useful foundations — these approaches take you further:

T3C / agency audits

Most TYPO3 agencies offer BITV tests based on EN 301 549 — useful for public-sector BIK compliance.

Lighthouse + WAVE

Free first-pass checks that cover roughly a third of WCAG issues on rendered TYPO3 pages.

Editor training

Most recurring TYPO3 issues come from editor choices (headings, alt text). A short style guide reduces them permanently.

Maintaining EAA compliance on TYPO3

Accessibility is not a one-time fix — sites change through content edits, theme updates and new pages. Keep compliance sustainable:

Re-test after major core or extension upgrades — output markup can change between LTS versions.
Add accessibility rules to your review process for new content elements and extensions.
Keep an up-to-date accessibility statement if you are under BITV/EN 301 549 — it is legally required.

Dig deeper into the compliance work that comes after the scan:

Go deeper

Automated scanning catches roughly a third of accessibility issues — but it catches the ones that are cheapest to fix first. For the complete picture, our e-book covers the full checklist plus a 14-day fix plan.

Free Statement Generator All Compliance Guides Free Scanner