TYPO3 Accessibility: Requirements, Implementation and Testing

In short: TYPO3 provides a good technical foundation but does not make a website accessible by itself. Templates, extensions and editorial work decide. Legally, the BFSG has applied since 28 June 2025 to private providers of certain consumer products and services, and BITV 2.0 applies to federal public bodies. In practice, WCAG 2.1 Level AA is the technical benchmark; WCAG 2.2 is already a W3C Recommendation.

To tackle the requirements in a structured way, see our guide with checklist.

The WebAIM Million 2026 automatically tested the home pages of one million websites in February 2026. On sites running TYPO3 CMS, an average of 38.5 accessibility errors per home page were detected. For comparison: Drupal 41.2, Joomla 45.7, WordPress 52.8 and 56.1 across all pages analyzed.

Read these numbers with care. An automated test covers only part of the possible problems and says nothing about your specific website. WCAG failures were detected on 95.9% of the home pages analyzed. So accessibility remains an open task for almost every website, regardless of the CMS.

TYPO3 offers features and tools that support developers and every TYPO3 agency in building accessible websites. Whether your website is accessible in the end depends on templates, extensions and content.

In Germany and the EU, several legal frameworks refer to WCAG or to the standard EN 301 549. The most important ones at a glance:

1. BFSG (Barrierefreiheitsstärkungsgesetz)

The BFSG of 16 July 2021 (Federal Law Gazette I p. 2970) transposes European Directive (EU) 2019/882 (European Accessibility Act, EAA) into German law and has applied since 28 June 2025. It covers certain consumer products and services, such as online shops (e-commerce), consumer banking services, telecommunications services, elements of passenger transport services and e-books. Micro-enterprises providing services (fewer than 10 employees and no more than €2 million annual turnover or balance sheet total) are exempt.

2. EN 301 549

The European standard for the accessibility of ICT products and services, including websites and mobile applications. For web content it adopts the criteria of WCAG 2.1 (Level AA). The version cited so far in the EU Official Journal, V3.2.1 (2021), is the technical basis of BITV 2.0. For the BFSG, neither the law nor the BFSG ordinance (BFSGV) names a specific standard. A presumption of conformity under section 4 BFSG requires that a harmonised standard is cited in the Official Journal. According to Barrierewerk and Deque (October 2026), this has not yet happened for EN 301 549 and Directive (EU) 2019/882; it is nevertheless often used as orientation.

3. BITV 2.0 (Barrierefreie-Informationstechnik-Verordnung)

BITV 2.0 (ordinance of 12 September 2011, last amended on 24 October 2023) is an ordinance under the Disability Equality Act (BGG). It applies to websites and mobile apps of federal public bodies. Federal states and municipalities have their own state-level rules. In substance it refers to the harmonised standards cited in the EU Official Journal, currently EN 301 549 and thus WCAG 2.1 AA.

4. European Accessibility Act (EAA)

The EAA is EU Directive 2019/882 of 17 April 2019. It harmonises accessibility requirements for certain products and services in the internal market. Member states implement it nationally, in Germany through the BFSG.

Status: October 2026. General information, not legal advice.

The BFSG (Barrierefreiheitsstärkungsgesetz) transposes the EAA into German law and has applied since 28 June 2025 to certain consumer products and services.

What the BFSG can mean for your company:

• Scope: The law concerns economic operators offering certain products and services to consumers, for example online shops (section 1 BFSG). Pure B2B offerings are generally not covered.
• Exemption: Micro-enterprises providing services (fewer than 10 employees and no more than €2 million annual turnover or balance sheet total) are exempt (section 3(3) BFSG).
• Transition period: Service contracts concluded before 28 June 2025 may continue unchanged until the end of the contract term, at most until 27 June 2030 (section 38 BFSG).
• Better usability: Accessible offerings reach more people and improve the overall user experience.
• Enforcement: Market surveillance lies with the federal states; for services, the joint market surveillance body of the states for the accessibility of products and services (MLBF) in Magdeburg is responsible. Violations can be fined up to €100,000 (section 37(2) BFSG).

Whether your offering falls under the BFSG should be assessed legally on a case-by-case basis. The MLBF explains its remit on the page of the Bavarian trade supervisory authority (in German).

Here are some points you should consider when implementing:

1. Select an Accessible Template

Start with a template designed for accessibility. The Bootstrap package for TYPO3 is a good choice. Still check your own customizations, because every change to the template can alter the result. The package offers:

• Logical arrangement of headings.
• Helpful roles and landmarks for screen readers.
• Simple keyboard navigation.
• Clear, visible labels on forms and error messages.

2. Add Helpful Extensions

Extensions are like add-ons that add new functionality to your TYPO3 website. Some extensions can support the work on accessible content:

• Accessible CAPTCHA alternatives: Make forms easier to use for everyone.
• T3AI and T3AA (products of T3Planet, a brand of NITSAN GmbH): Support metadata and alternative texts. Editors should review and approve AI suggestions.
• Mask or container: Building blocks for structured, reusable layouts. The accessibility of the output depends on your templates.

3. Organize Your Content Clearly

Accessible websites not only look good, they are also well organized:

• Use TYPO3's content tools to add headings, lists and tables.
• Always add descriptive alt text for images, captions for videos and clear labels for links.
• Keep your web pages consistent so visitors know what to expect.
• Use TYPO3's "Text & Media" to display words and images together that make sense to screen readers.

4. Fix common Accessibility Errors

TYPO3 gives you the ability to control your content, but that also means you need to watch out for errors:

• Don't forget to add alt text to images.
• Make sure your headings are clearly structured (don't jump from a heading to a subheading without an intermediate step).
• Avoid links that just say "click here"; instead, describe what the link does.
• Don't overload your pages with too many moving elements or auto-playing videos.

The front end is the face of your website, what users see, interact with and rely on to access your content. For people who use assistive technologies, the front end can either be helpful or not. Assistive technologies include screen readers, voice control and keyboard navigation.

1. Accessible Templates

• The TYPO3 Bootstrap package passed the BITV test of the test centre BIK für Alle in 2023 (press release of 29 August 2023, in German). Still check your own implementation, because customizations to the template change the result.
• It is based on the Bootstrap CSS framework and offers landmarks, keyboard support, ARIA roles, a contrast-friendly user interface and a semantic structure.

2. Frontend Core Features for Accessibility

• TYPO3 generates structured content and clean HTML (using Fluid templates). This allows administrators or editors to easily add accessibility features such as alt texts, captions, ARIA roles and properties, and jump links.
• Responsive behavior, scalable fonts, mobile-first rendering and fast loading can help to meet usability and perceptibility criteria.

3. Accessibility Extensions (Selection)

Extensions can support editors. They replace neither testing nor fixing templates. Check suitability and compatibility with your TYPO3 version case by case.

• a11y-by-default (web-vision): Backend module for accessibility checks using axe-core and HTML CodeSniffer. According to Packagist, for TYPO3 13.4 and 14.3.
• Alt-Text Checker (Leuchtfeuer): Flags files without alternative text in the file list. According to Packagist, for TYPO3 13.4.
• T3AA: Supports, for example, alternative texts. Editors should review and approve AI suggestions.

Disclosure: T3AA is a product of T3Planet, a brand of NITSAN GmbH. A toolbar or widget does not replace fixing templates and content.

4. Interaction-Focused Features

• ARIA roles and landmarks: Helps screen readers identify navigation, main content, banners and interactive components. Templates can embed aria-label, aria-expanded and correct roles.
• Keyboard navigation and focus management: TYPO3 templates and extensions help with tab order. They also provide visible focus indicators. Additionally, there are skip links for faster navigation.

5. Content-Level Support

• Editors can use TYPO3 forms to add alt text, correct link labels and headings in logical order. The system can implement these as mandatory fields.
• Semantic HTML elements such as <main>, <nav> and <aside> can be used directly in Fluid templates. Whether they are used correctly depends on the template.

6. Media accessibility

• The extension a11y_me_video (iundd) provides a video player based on MediaElement.js. According to Packagist, it supports subtitles, audio description, sign language video and a text alternative. Its current version 3.0 is listed on Packagist for TYPO3 12.4 and 13.2; check compatibility with TYPO3 14 beforehand.

The tool your editors work with matters too. TYPO3 has continued to develop the accessibility of the backend over recent versions, and the guideline ATAG 2.0 applies to authoring tools. Check in your own setup whether editors can do their work with keyboard and screen reader.

Real-World Testing: Accessibility in the TYPO3 Backend

A practical test published on typo3.org in February 2022 examined the usability of the backend with two blind users. The tests took place in Berlin in October and November 2021 and covered version 11.5.1. The results do not transfer directly to current versions or to your project, but they show typical questions that still come up today.

Findings from the test with an editor

• With a screen reader and Braille display, familiar workflows such as uploading and assigning files worked. In new situations obstacles occurred; all editing steps could only be completed fully with support from the test moderators.
• The TYPO3 backend was usable for trained and experienced screen reader users. Onboarding and documentation are key factors.

Findings from the test with an accessibility software tester

• Unlabeled fields, silent error messages and unclear navigation affected usability.
• Keyboard and screen reader support needs to be carefully thought through so that workflows run smoothly.

Editorial Workflow That Supports Accessibility

Beyond the user interface, TYPO3 supports an editorial system that enables structured content creation processes that follow accessibility best practices:

• Editors can easily assign alt text, headings and semantic layout blocks.
• Extensions can validate content or implement accessibility rules during editing.
• Custom roles and permissions can include accessibility checks before publishing.

Accessibility and SEO overlap. A ranking improvement cannot be derived from that, because search engines do not publish their weighting.

Where accessibility and SEO overlap

• Crawlability: A clear structure and clean HTML can make it easier for search engine bots to capture and index a page.
• User experience: Descriptive alt text, clear navigation and well-formatted content help people with and without disabilities find their way.
• Shared best practices: Many accessibility measures overlap with SEO recommendations, such as semantic HTML, meaningful link text and proper ARIA role use. This improves how well users and search engines understand your website.

Once your TYPO3 website is accessible, the real work begins: creating content that stays accessible every day.

Here are some points to keep in mind when creating accessible content in TYPO3:

1. Use Headings Correctly

It is recommended to start with an H1 heading for the page title. Use H2 for main sections and H3 for subsections. Do not skip heading levels. TYPO3 helps you to keep your headings in a good structure and order.

2. Add Alt Text to Images

Images should also have a short, meaningful alt text so that everyone knows what function they have. Only skip the alt text for decorative images. Add longer descriptions to complex graphics. TYPO3 makes this easy.

3. Make Audio and Video Accessible

Add subtitles to videos and transcripts to audio recordings. Describe important visual details verbally. Avoid sudden sounds or visual changes that can be distracting. TYPO3 has media tools that allow the use of accessibility features.

4. Use Clear and Simple Language

Use short sentences with everyday words. Define and explain all technical terms. For urgent or important content, create an easy-to-read version to improve comprehension.

5. Ensure Good Color Contrast

The text must be easy to read against the background. Always adhere to contrast rules (at least 4.5:1 for normal text) and avoid overlaying text over images unless it is clearly recognizable. Test this with WAVE or similar software.

6. Use Descriptive Link Text

Links must explain where they lead. Avoid ambiguous words such as "click here". Use descriptive terms such as "Download PDF guide" or "Learn more about TYPO3 features".

Run a free check now with the TYPO3 Accessibility Checker and get clear, actionable hints about your website.

No setup needed.

Creating an accessible website is an ongoing activity that starts with planning. TYPO3 offers a solid foundation for accessible websites, but responsibility for implementation and content stays with you.

Accessibility is never "finished", but every step forward makes a real difference for the people who use your site.

Would you like support with the technical side? Find out more on our page Implement TYPO3 accessibility and about us as a TYPO3 agency.

Status: October 2026. General information, not legal advice.