Accessibility Initiative

Summary

The focus of the Accessibility Initiative is improving the accessibility in TYPO3. We share our accessibility expertise and are looking for supporters of an accessible TYPO3. Feel free to get in contact.

We will also promote this in the community to boost accessibility long term. We want to establish coding standards to ensure improvement of accessibility.

Background

Accessibility is an essential part of an inclusive user experience. Improving accessibility by removing barriers will also simplify the usage of TYPO3.

There are three parts we need to have in mind:

  1. Deliver an accessible website (frontend rendering)
  2. Support the editors in creating accessible content
  3. Provide an accessible user interface for authoring the content

Delivering an accessible website is already possible with TYPO3. We want to improve and update the default rendering. Our main focus is to improve the parts “editor support” and “accessible authoring tools”. To support editors, information on accessibility issues should be given on editing elements (e.g. missing alternative texts for images and information on how an alternative text should look like). Editors need to be aware of accessibility and are currently not guided in creating accessible websites. The user interface of the authoring tool (TYPO3 backend) is not accessible. A first focus can be set on keyboard interaction, but the design (e.g. contrasts) and consistent usage of interactive elements (e.g. checkbox vs. toggle vs. radiobutton) needs to be in focus, too.

Goals

  • Provide information on accessibility and give opportunities to discuss on accessibility topics on a regular basis (Slack channel & TYPO3 Accessibility Hour)
  • Raise awareness for accessibility in the TYPO3 core team and the community
  • Implement accessibility guidance tools (notices for editors on creating accessibility issues)
  • Improve the accessibility of the TYPO3 backend and implement processes to support continuous improvement of the backend accessibility
  • Establish coding standards to ensure improvement of the accessibility
Image about timing (calendar)

Milestones

Reached Milestones

  • Establish a TYPO3 Accessibility Hour

Short-Term

  • Participating in the T3INIT19 and other events like barcamps and meetups to promote the initiative in the community
  • Talk to core members on this topic and get their support of the goals of the initiative

Mid-Term

  • Add tools to check the accessibility of editor content
  • Improve the TYPO3 backend, make it accessible for keyboard usage.

Timing

Keeping TYPO3 accessible will be an ongoing process, as will be raising awareness. We will help the TYPO3 contributors and core team to keep TYPO3 accessible.

Scope

For this initiative the TYPO3 core and core extensions are in scope. We will raise awareness and provide information on 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

We already have had some accessibility hours and are looking for more to come.

Get involved!

Team

Michael Telgkamp
(Lead)

Patrick Broens
(Dev, Research)

Torben Hansen
(Dev)

You?