TYPO3 WCAG *cancelled application* - replaced with joint one Accessibility working group

Added by Naike Beggiato about 4 years ago

The project aims at producing a TYPO3 CMS distribution that extends the TYPO3 CMS standard distribution with the following functionality: editing tools for standard content element that drive editors in delivering WCAG 2.0 compliant contents, WCAG 2.0 verification tools, accessible theme integration.

Budget Owner: Ivano Luberti
Euro 39'025.00


Replies (6)

RE: TYPO3 WCAG - Added by Patrick Broens about 4 years ago

Related to "TYPO3 Accessibility Package"

RE: TYPO3 WCAG - Added by Patrick Broens about 4 years ago

A lot of CMS's which allow template customization can manage a website that conforms to WCAG 2.0 Level A or AA and many aspects of AAA. Just building a distribution or theme which handles WCAG is not the solution IMHO. It's only a showcase that TYPO3 can handle WCAG and will not be used by websites which actually need it, like governmental websites build from scratch.

It is better to raise awareness by writing documentation like an accessibility handbook, best practices for themes and extension frontend output. Especially extension authors are not aware of WCAG or even better WAI-ARIA, which I'm missing in this budget application.

The same goes for the "TYPO3 Accessibility Package", which I've put to related to this budget application. These two teams should sit together and form an Accessibility Workgroup.

RE: TYPO3 WCAG - Added by Peter Proell about 4 years ago

I like the feedback from Patrick very much.

For sure there will be no money to foster two WCAG groups within the TYPO3 project. Would be great if the two applicants start working together already before the polling and getting in touch with the EAB for presenting a common solution already.

RE: TYPO3 WCAG - Added by Markus Klein about 4 years ago

I fully agree with Patrick here. Besides the goal of improving education and awareness, the Core (and the exts) should provide as much WCAG compatible output as possible by default. Twitter Bootstrap made big steps in this direction already.

So effort should really go into education here and also into identifying weak spots in Core.

RE: TYPO3 WCAG - Added by Jo Hasenau about 4 years ago

Actually we already met in person during the THEMES presentation at the Internet Festival in Pisa, since Ivano and Rino invited me to come there.
So of course we found out that we are dealing with similar if not identical topics and that each team would be a very welcome improvement to the other.
So joining forces seems to be the way to go here, we just have to discuss with the EAB how to proceed now.

To be on the safe side, I will put the very same comment into the other discussion as well.

RE: TYPO3 WCAG - Added by Ivano Luberti about 4 years ago

I can of course confirm what Jo says about our intent of collaborating.

I just want to add that the description TYPO3 WCAG project provided in the
Budget Application cannot describe the whole project and, for example,
doesn't show that the plan, written using advise from Mathias
Schreiber and from one representative of the Italian Government that took
part in the team that wrote the Italian Law on Web Accessibility, is to

- provide tools for editors in order to produce WCAG
compliant contents and maintain that compliance during modifications.

- integrate a formal compliance tool to validate content

When I wrote the application I was not aware of Jo work on
accessibility but had already in mind to collaborate with someone
(still to be determined at the time), to create themes supporting WCAG
compliant content structure: Jo was one of the candidates since I had
seen its presentation at Certifuncation Day and I and my colleagues
were so impressed we invited him in Pisa for the TYPO3 Day during the
Internet Festival. That invitation was made way before starting to
work on our application.
Writing the application I was not aware that Jo was going to work in
the same field but, as he says, we mutually discovered it while he was
in Pisa.

I will also put the very same comment into the other discussion as well.

    (1-6/6)