The web stopped being a playground for the technically curious a long time ago; it is now a central place for information, communication and trade. Accessible web design is therefore not an option but a necessity, for reasons of access and because of legal requirements such as the EU Web Accessibility Directive and the European Accessibility Act. This guide shows how accessible websites can be built in WordPress and TYPO3.
Fundamentals: why accessibility counts
Accessibility goes beyond simply being reachable. It means your website is usable by everyone, regardless of individual abilities or impairments. That includes people with visual impairments, hearing loss, motor difficulties or cognitive impairments. Understanding those needs is the first step.
The benefits are varied: higher user satisfaction, better findability in search engines, a more positive picture of the company and compliance with legal requirements. And accessible does not mean old-fashioned: a well-considered accessible design usually improves usability and aesthetics as well.
WordPress: accessibility in practice
WordPress offers a solid foundation but demands attention in several places.
- Themes: choose an accessible theme with a clean semantic structure, meaning correct use of header, nav, main and footer, and sufficient colour contrast. Check the documentation and test reports before you commit.
- Plugins: tools such as Accessibility Checker run automated tests. They do not replace manual review, but they reliably find the obvious errors.
- Images: give every image an alternative text. Describe the purpose of the image and convey its content, not merely how it looks.
- Forms: every input field needs an associated label. Error messages belong next to the field concerned, not only at the top of the form.
TYPO3: accessibility in an enterprise setting
TYPO3 offers the same possibilities, but the approach is more technical.
- TypoScript: make sure the configuration produces semantically correct markup and maps the document structure cleanly.
- Extensions: testing tools and Fluid-based layouts help keep presentation and structure consistent.
- Templates: avoid unnecessary div nesting and use the appropriate HTML5 elements.
- Contrast: check text against background systematically, not by sampling. The requirement is 4.5:1 for body text.
Pitfalls and good practice
Accessible design does not mean giving up creative freedom, but using it deliberately. The typical stumbling blocks are colour contrast, navigation logic and how readable the text is.
- Colour contrast: check with tools rather than by feel. What looks fine on a calibrated screen often fails in sunlight.
- Typography: legible typefaces, adequate size, generous line spacing.
- Navigation: clear and predictable. Every important page must be reachable through the navigation, with the keyboard alone as well.
- Comprehensibility: plain language, short sentences, no unnecessary jargon. That helps everyone, not only people with cognitive impairments.
Conclusion: design it in from the start
Both WordPress and TYPO3 offer everything needed for accessible websites. The timing is what decides: designing accessibility in at the start of a project saves the rework at the end. Bolted on afterwards it gets expensive, and it is rarely complete.
Once you have understood the WCAG criteria, you apply them at no extra cost. They are not a straitjacket but a checklist for things that ought to be done well anyway.