An accessible CMS for an inclusive website

Since the entry into force of the law on strengthening accessibility, it is essential to create accessible websites with a CMS. A content management system with the right features makes it possible to comply with legal requirements, improve the user experience and optimize content for SEO.

Why should a CMS guarantee content accessible to everyone?

Digital accessibility does not only concern the technical infrastructure of a website, but also the content published. So that the digital information is accessible to all visitorsthey must be designed so that they can be viewed with screen readers, braille devices or by keyboard.

The content management system (CMS) used plays a central role here. If the accessibility of the user interface of a CMS is often highlighted, it is just as essential to consider to what extent it supports the editorial creation of accessible content. The CMS must provide editors with support toolsof the structural guidelines and validation mechanisms making it easier to create barrier-free websites. Here are some concrete examples:

• Input fields for alternative texts for images
• Warnings for missing title structure
• Tools for creating tables and forms
• Automatic checks for contrasts and semantic errors

An accessible CMS reduces the risk of editorial errors and helps organizations meet legal requirements, while providing equivalent information to all users.

What are the standards that define web accessibility?

Web accessibility is governed by the General framework for improving accessibility (RGAA)which transposes European Directive (EU) 2016/2102 on the accessibility of public sites and applications. Since 2023, the transposition of Directive (EU) 2019/882 (European Accessibility Act) extends these obligations to certain digital products and services, applicable from June 28, 2025. These rules are based on the WCAG 2.2 international guidelines of the W3C as well as on the European standard EN 301 549which set out the fundamental principles to guarantee the accessibility of online content.

WCAG 2.2 defines four essential principles to respect to ensure the accessibility of a site or CMS:

• Perceptibility : all information must be presented in a way that each user can understand, for example with text alternatives to images and sufficient contrast.
• Usability : the interface must be navigable with different devices, including the keyboard.
• Understandability : the contents must be clearly structured, written in simple language and easy to read.
• Robustness : Content must be compatible with different devices and support tools.

For editors, this involves using a logical heading hierarchy (H1 to H6) and integrating alternative texts and relevant links. It is equally essential to adopt clear language and consistent navigation. An inclusive CMS that meets these requirements simplifies editorial work and contributes to compliance with legal obligations in France.

Accessibility in the CMS: practical examples with Contao, Plone and Papaya CMS

Not all CMS offer the same conditions for creating accessible content. Some systems stand out for the quality of their frontend rendering, while others emphasize editorial control or semantic rigor. The three CMS open source Contao, Plone and Papaya CMS are particularly known for promoting accessibility. That’s why we present their main features in this area below.

Contao

Contao is a CMS developed in Germany, designed from the outset for accessible and semantically clean code. In order to facilitate the creation of content that complies with accessibility legislation, the software offers the following features in particular:

• Accessible templates : Many themes follow WCAG standards and are designed to be responsive.
• Structured content elements : Editors use modules that ensure clear and semantically correct output.
• Support for alt texts : images, videos and other media can be enriched with alternative descriptions.
• Form modules : Out-of-the-box components support mandatory field designation, keyboard navigation, and error handling.

In addition, extensions like SiteCockpit add built-in accessibility features, such as color contrast adjustment, font size control and automated audit reports. Thanks to these advantages, Contao constitutes a solution particularly suited to public institutions, educational establishments and NGOs.

Plone

Plone is a powerful Python-based CMS that has had strict accessibility standards for many years. It is used worldwide by universities, government departments and organizations with high requirements for digital accessibility. Plone complies with WCAG 2.1, level AA, and therefore integrates by default many features facilitating accessibility.

To attest to this conformity, a VPAT document (Voluntary Product Accessibility Template) is available. This is a standardized report that describes how well the software meets accessibility standards. This document allows businesses and institutions to quickly check whether Plone meets their legal obligations and accessibility needs.

Among the main editorial accessibility advantages offered by Plone are:

• Clear semantic structures : the formatting of the content is strictly based on HTML5 standards.
• Editorial workflow management : content can be checked and validated for compliance before publication.
• Access control : allows collaborative work thanks to clearly defined roles.

Additionally, extensions like Plone All in One Accessibility Widget add practical features, such as adjusting font size, changing contrasts or optimized keyboard navigation. These advantages make Plone an ideal solution for accessible portals integrating complex processes.

Papaya CMS

Papaya CMS is a modular, XML-based content management system that stands out for its clear separation between content, layout and logic. This architecture makes it possible to generate semantically correct and accessible HTML output. Papaya is particularly suited to complex projects with strong editorial requirements and well-defined distribution channels.

• Strict structuring : Thanks to the separation of content, layout and logic, the creation of websites conforming to HTML semantic standards is facilitated.
• Accessible templates and modules : many models and components comply with WCAG standards.
• Multilingual content : data management allows inclusive dissemination in multiple languages.

The creation of accessible content does not stop with its entry into the CMS. Regular verification is essential to quickly detect and correct barriers to use. To test the accessibility of a website, it is recommended to combine automated tools with manual methods.

Automated tools

• DevTools axis : a proven browser extension from Deque Systems, which reliably detects accessibility errors according to WCAG criteria and provides precise guidance for correcting them.
• WAVE (Web Accessibility Evaluation Tool) : allows you to directly view the barriers in the browser window; ideal for checking the editorial quality of content such as alternative texts and title structure.
• Google Lighthouse : provides accessibility scores and concrete recommendations on structure, colors, usability and more; executable via Google PageSpeed ​​Insights, in Chrome DevTools, on the command line or as a Node.js module.
• Evicted : uses artificial intelligence and machine learning to detect complex barriers; offers detailed developer reporting as well as integrations for DevOps environments.

Manual testing

Automated tools cannot identify all accessibility issues. This is why it is essential to complement their use with manual methods, such as:

• Keyboard navigation : check that the site is usable only with Tab and Shift, and that the focus indicators are visible and consistent.
• Testing with screen readers : Use NVDA (Windows), VoiceOver (macOS/iOS), or JAWS to control semantically correct reading, focus announcements, and reading sequence logic.
• Checking contrasts and color simulations : tools like WebAIM Contrast Checker or Color Oracle allow you to evaluate contrasts and simulate different visual deficiencies.
• Forms control : ensure that labels are correctly associated, that error messages are clear, that focus moves logically and that input fields are accessible.
• Visual inspection and zoom tests : check if the design remains functional with a high zoom rate and if the content adapts correctly, without the appearance of horizontal scroll bars.

Finally, it is recommended to set up a editorial guide on accessibility and to provide regular trainingin order to sustainably strengthen skills within the team.