Published: Last updated:

Contao

Contao is an open-source PHP CMS under the LGPL that puts accessibility and clean, semantic markup at its centre. It ships the tools for websites to WCAG and the European Accessibility Act, yet accessibility stays an editorial discipline, not an automatic property of the tool choice.

Anyone choosing a CMS aimed at accessible output from the start arrives quickly at Contao. It positions itself explicitly as a low-barrier system and tunes its templates, its back end and its HTML output to that end. This page describes what Contao is technically, what the accessibility focus actually rests on, and why the tool choice eases the obligation to be accessible but does not fulfil it.

Core concept

Contao is a classic database-backed CMS built on the Symfony framework and thus firmly rooted in the PHP world. It separates content, configuration and presentation and emits HTML5 by default that follows W3C and WAI guidance. Editors maintain content in a back end that, by the vendor's account, is itself largely accessible and compatible with assistive technologies. The licence is LGPL-3.0, so use is free even in commercial projects; the open-source availability places Contao in the same family as Drupal, Grav CMS or the likewise German-speaking-region TYPO3.

The accessibility focus

The difference from many other systems lies in the starting stance. Contao states that it brings everything needed to build websites that meet WCAG 2.1 Level AA and work with assistive technologies. Three layers carry that claim:

  • Clean HTML5 output. The supplied templates produce semantically structured code to W3C and WAI guidance rather than nested layout markup. That is the foundation on which screen readers and keyboard navigation can work at all.
  • Customisable templates. The output is not walled into a rigid theme machinery but openly customisable. Whoever builds their own templates can preserve the accessible structure instead of undermining it.
  • Accessible back end. The administration area too is, by the vendor's account, largely low-barrier. That lowers the bar for editorial teams who themselves rely on assistive technologies.

Contao names the German BITV 2.0 and the European Accessibility Act explicitly as target marks. It therefore delivers not just code but an alignment with concrete regulations.

Accessibility is a discipline, not an automatism

This is the decisive point where many projects fail. The vendor's statement is that accessible websites can be built with Contao, not that every website built with Contao is automatically accessible. The difference is operationally large.

An embedded image without alternative text stays inaccessible, no matter how clean the CMS beneath it. A self-built template with a broken heading hierarchy breaks the structure the standard templates would have provided. A colour scheme with too little contrast misses the WCAG criteria regardless of the system. Accessibility emerges from the sum of tool, template building, editorial practice and ongoing testing. Contao shifts the starting position towards accessibility but replaces neither the training of the editorial team nor testing with real assistive technologies.

The regulatory proximity

The topic matters more because accessibility is moving from the optional to the obligatory. The European Accessibility Act requires a defined group of products and services, among them e-commerce offerings, banking services and e-books, to be designed accessibly. The substantive yardstick for web content is the Web Content Accessibility Guidelines (WCAG), currently in version 2.2. A CMS that eases WCAG-conformant output thereby lowers the effort of meeting these obligations.

For Swiss actors the European Accessibility Act applies where they offer affected products or services in the EU internal market. Independently of that, accessibility is a question of quality and reach even without immediate legal compulsion: an accessible site reaches more people and is usually technically cleaner too. Where digital solutions are to be built for longevity and standards conformance anyway, the accessibility focus fits into the consideration of digital sovereignty.

Where Contao fits and where it does not

flowchart TD
    A["Requirement:<br/>accessible website"] --> B{"Accessibility<br/>as a core goal?"}
    B -->|"yes"| C["Contao:<br/>clean output + EAA alignment"]
    B -->|"no, more data model"| D["Drupal:<br/>complex entities"]
    B -->|"no, more lean + fast"| E["Grav CMS:<br/>flat-file, small sites"]
    C --> F["test templates, content, output<br/>for accessibility"]
    F --> G["accessible website<br/>as a result, not a guarantee"]

The diagram shows the placement. Contao plays its strength where accessibility is a stated core goal and the output should be clean from the start. Where the focus is mainly complex data relationships, Drupal is stronger; where a lean, fast site without a database suffices, Grav CMS is the simpler choice. The last step stays the same in every case: templates, content and the result have to be tested for accessibility. Contao shortens the path there, the goal itself remains work.

Assessment

  • Use case. Websites with a stated accessibility ambition, public-sector and authority-adjacent presences, and offerings that fall under the European Accessibility Act.
  • Advantage. Accessibility is part of the product orientation rather than a retrofitted add-on; clean HTML5 output, customisable templates and a largely accessible back end.
  • Limitation. Smaller adoption and a smaller extension ecosystem than the large competitors; and the central caveat that the system enables accessibility while editorial discipline is what actually produces it.

References

  • Contao Accessible websites with Contao. Vendor statements on BITV 2.0, EAA, WCAG 2.1 AA and accessible HTML5 output. (2026). contao.org/en/features
  • W3C WAI Web Content Accessibility Guidelines (WCAG) 2.2. Current version of the international guidelines for accessible web content. (05.10.2023). www.w3.org/WAI/standards-guidelines/wcag/
  • European Union Directive (EU) 2019/882, European Accessibility Act. Accessibility requirements for a defined group of products and services in the EU internal market. (17.04.2019). EUR-Lex CELEX 32019L0882

Related topics

  • Drupal, the modular enterprise CMS for complex data models.
  • Grav CMS, the lean flat-file CMS for small, fast sites.
  • Symfony, the framework Contao builds on.
  • PHP, the language Contao is written in.
  • Digital sovereignty, the strategic frame for standards-conformant, long-lived solutions.

Ask AI

These links open external AI services, the conversation and its content are sent to their providers.