Accessibility Initiative

Summary

Raise awareness about accessibility. Provide tools which will help everybody, involved in building websites with TYPO3, to make websites fully accessible. Have an accessible TYPO3 backend.

Background

Accessibility is an essential part of an inclusive user experience. When you commit to accessibility, you ensure that your product (whether it is a website, web application, or mobile app) is operable by people with a wide range of abilities. As a result, potential barriers to access are not only removed, but you avoid creating them in the first place. No matter if your organization is in the public, private, educational or charity sector, making sure your product is accessible will increase your audience reach.

“Information should be accessible to everyone without any barriers!”

More and more governments were demanding accessible websites since approximately 2006, but not enforcing it. This has changed in the recent years. The frontend output of TYPO3 has to comply to the laws regarding accessible websites, be it laws from the European Union, the United States or other countries.

Although 100% accessible frontend output is already possible, it highly depends on input and changes from the editors. They can easily lower the accessibility without knowing.

Initiatives have started by governments to have all tools accessible as well. This includes the TYPO3 backend. In the past there was never a focus on making the TYPO3 backend accessible.
 

Goals

Raise awareness; Provide documentation how to make sure websites are operable by people with disabilities. This can be done by documentation, linking to excellent and understandable  sources about accessibility, talks at conferences and feedback from the TYPO3 backend. Awareness should be raised for all people using TYPO3, like TYPO3 core team, text writers, developers, integrators and editors.

Provide tools to validate the frontend output of TYPO3 and make visible where improvements can be done. 

Have the TYPO3 backend fully accessible.

Image about timing (calendar)

Milestones

First we need to implement tools to validate the frontend output of TYPO3 and make visible where improvements can be done. After this we need to start raising awareness. Then we can start having the TYPO3 backend accessible.

Timing

  • Short-Term: now
  • Mid-Term: 9LTS
  • Long-Term: 10.x

Keeping TYPO3 accessible will be an ongoing process, as will be raising awareness. Help the TYPO3 contributors and core team to keep TYPO3 accessible, be it front- or backend.

Scope

For this initiative documentation and the TYPO3 core is in scope. Although we can provide information about accessibility, we will not focus on websites (e.g. TYPO3 inc), packages (e.g. Bootstrap package) or tools (e.g. Forge) within the TYPO3 universe.

Current Status

At previous TYPO3 User Experience Weeks (T3UXW) there has been already some focus on accessibility. Most of this work was focused on preparation how to implement frontend output validation, but also to have accessible websites within the TYPO3 universe (like typo3.com), which is out of focus for this project.

Patrick Broens, former active contributor,  has started implementing frontend accessibility testing and visualisation of the outcome with several existing frameworks (AChecker, QuailJS). Several times this development had to be stopped since the developer(s) of these frameworks stopped maintaining them. Since the beginning of 2018 a third attempt was made with the open source framework aXe, the currently leading accessibility testing framework, developed by the Canadian company Deque Systems, specialized in web accessibility. Since aXe is backed by a community and a company, and currently seen as the market standard for website accessibility testing, this seems to be the right way to go. The testing and parts of the visualization of these tests are as good as finished at the time of writing (April 2018).

Get involved!

Team

Patrick Broens
(Lead, Dev, Research)

Rens Admiraal
(Dev)

Luis Pato
(UX, VoiceOver testing)

Carla Froitzheim
(Documentation, Testing, Research)

Abramo Tesoro
(UX, Testing)

You?