The Accessibility Team helps to improve and maintain the accessibility in TYPO3. Therefore we share our accessibility expertise with all TYPO3 developers, but that is not enaugh. That is why we additionally look for supporters of an accessible TYPO3. Feel free to get in contact if you are interested in helping us or have questions regarding accessibility.
We also promote this topic in the community to boost accessibility long term.
Open Accessibility Sprint in October
For October 2020 we are planing to have an online sprint for improvements of the TYPO3 Accessibility
Making TYPO3 accessible is a mission to make the web a little bit better! You can help us with your development and UI/UX skills, accessibility know-how or your documentation or testing experience. The Accessibility Sprint will be an open remote sprint and everyone is welcome to join!
Where: Online! The event will be remote due to the current COVID-19 situation. Additionally we will have some hotspot locations (if the COVID-19 situation allows it) where small groups get together to team up in one location. The first hotspots are Budapest (Hungary), Melk (Austria) and Munich (Germany). Eveyone interested in providing a space for developers to meet is welcome to get in contact for sharing it here. When: It will take place from October 21–23, 2020. Time: The times for the sprint event are scheduled according to Central European Time. If you would like to join from another timezone, please get in contact with michael.telgkamp(at)mindscreen.de, and we can figure out a way to handle it.
The event is organized by the TYPO3 Accessibility Initiative. The initiative was reinitiated in September, 2019 by members of the TYPO3 community. We provide information on accessibility and give the opportunity to discuss accessibility topics on a regular basis in our TYPO3 Slack channel #cig-accessibility and the monthly TYPO3 Accessibility Hour.
Our goal is to make TYPO3 accessible and improve the knowledge on accessibility for other TYPO3 developers.
Current Status of TYPO3 Accessibility
While it is possible to use TYPO3 to create accessible websites, the TYPO3 editing interface is missing support for accessibility in some important places. As a starting point for the initiative, the TYPO3 pagetree was improved during the TYPO3 Initiative Week 2019. It now fully supports keyboard navigation following the best practices described in WAI-ARIA Authoring Practices 1.1.
Since then, a user survey helped to get feedback from users and discover which parts of the TYPO3 backend were lacking in accessibility. As a result, multiple issues have been documented and some of them have already been resolved. There is a public custom query to show accessibility issues on Forge, the TYPO3 core issue tracker.
Ideas & Goals for the Accessibility Sprint
We want to raise awareness for accessibility in TYPO3. Making TYPO3 more accessible will help every user of TYPO3, and is also a requirement for customers in the public sector, such as universities and governments.
During the sprint we will try to feature live tests by people with disabilities to get an insight into the major issues.
For TYPO3 itself, we will focus on several parts, and we plan to:
Create developer guidelines for future improvements and education.
Enhance consistency with TYPO3 backend components, such as Buttons and Tabs.
Improve accessibility for the most important parts of the TYPO3 backend.
Create accessibility tests integrated in the TYPO3 Core Bamboo testing suites to ensure the accessibility for future development.
Create issues in Forge for all accessibility problems discovered during the sprint to have a collection of improvements to make after the sprint.
You’re Welcome to Join Us!
Join our sprint to make TYPO3 better for everyone, October 21–23, 2020.
Accessibility is an essential part of an inclusive user experience. Improving accessibility by removing barriers will simplify the usage of TYPO3 for everyone.
To support editors, information on accessibility issues should be given on editing elements. We could highlight missing alternative texts for images. Additionally helping information on how to write a good alternative text can be given. Editors need to be aware of accessibility. Then should be guided in creating accessible webcontent.
The Backend accessibility
The user interface of the authoring tool is not accessible yet. Firstly we set a focus on keyboard interaction. In addition the layout and the design as well as a consistent usage of interactive elements needs to be in focus.
The frontend is the most important part for the audience of a website. Delivering an accessible frontend is already possible with TYPO3. However we still want to improve and update the default rendering.