Accessibility best practices guide for TYPO3

Application by
Lina Wolf

What is your idea about?
There is already much information available on how to create accessible web pages in general. However, little of it deals with what you have to do in TYPO3. Even less is known about best practices.

In the existing documentation, some random information on accessibility is scattered throughout the official information: Search results for: accessibility

We want to write a guide on how to create accessible websites specifically with TYPO3, including frontend and backend configurations. To accomplish that, we’ll gather the experiences of the Accessibility Team and collect best practices from universities and public institutions that have highly accessible websites in TYPO3 already.

Accessibility is much more than just frontend rendering. The backend must be usable by editors with disabilities, and editors must enter content in a way that will be more accessible. To help with this, we will document relevant backend settings and features.

This resource will also serve to raise awareness of accessibility topics within the TYPO3 community.

What is the potential impact of your idea?
Accessibility is an important requirement for many government-owned website in many countries. TYPO3 is a strong tool for creating accessible websites. However, details on how to best create a state-of-the-art accessible website in TYPO3 is scarce and scattered.

A guide collecting best practices on accessibility can make the creation of accessible websites easier and therefore cheaper for government websites, universities, and many others. More institutions will use TYPO3 and join the TYPO3 Association. Having a section specific to accessibility in our documentation will help show TYPO3’s commitment to accessibility in general.

Who can / should implement your idea?
Lina Wolf and Paul Hansen

Approximate Funds needed
€5,000 - €10,000

5 Likes

I see three target groups.

FE-integrators:
What needs to be configured in TYPO3 and how must default templates be changed to make the rendered HTML accessible.
Integrators should be provided with links to existing resources that cover the general topic of a11y.

BE-integrators:
What needs to be configured in TYPO3 to aid editors to create accessible content.

Editors:
What tools does TYPO3 provide to make your content accessible.
Editors should be provided with links to existing resources that cover the topic of writing with a11y in mind.

Another group are UI/UX and graphic designers. There is nothing special for TYPO3, but we could provide also links. As a bad design can ruin all later efforts, I think it makes sense to include that.

1 Like

This is important. Delivering accessible projects is required for some contracts by law (e.g., for some public services).

1 Like