Accessibility Project

h1. Accessibility project

h2. Introduction

For this project first a local testing environment will be setup by Patrick Broens. This testing environment will cover all Content Objects from the TYPO3 Core with all their possible settings. Once this environment is setup, a .t3d file will be posted here on the Wiki. Other participants or people who are interested in this project, can use this .t3d file to follow the progress of the project.

The testing environment will use a very clean output, HTML and CSS, not to disturb any of the output the core renders. Multiple things need to be checked and changed according to this check:

* W3C validation of HTML, XHTML and CSS

* Inline styles are not allowed

* Accessibility according to BITV

These checks and the outcome will be documented on this Wiki in week 30, including what has to be done and what has been done already. So the progress of the whole project is visible here.

The first issues which will be resolved are the inline styles. Some investigation has already been done, especially for the style="width: xxpx;" for images and captions. This can be resolved quite easily using a different markup and CSS2.1. Some other inline style issues are still there which need some investigation. These issues need CSS, which can be put in the stylesheets already generated in typo3temp/.

Stay tuned!

h2. Tests

There is a testing environment available which you can use locally or put it on a server. It consists of two files (t3d.tar.gz.part-xx) which have been splitted using the OSX split command and contains the T3D file for this setup. Next there is a file with the copy of the fileadmin folder (fileadmin.tar.gz)

* [[W3C tests on HTML 4.0 Transitional / XHTML 1.0 Transitional / XHTML 1.0 Strict / XHTML 1.1 / HTML 5]]

* [[Inline styles]]

* [[Markup]]

h2. Pending documentation for TSREF

filelink: target has now data type "target/stdWrap"

filelink: title has been added and has data type "string/stdWrap". This is the title attribute for the link, titleText and altText are used for the icon.

GMENU: target has now data type "target/stdWrap"

TMENU: target has now data type "target/stdWrap"

IMGMENU: target has now data type "target/stdWrap"

JSMENU: target has now data type "target/stdWrap"

filelink: longdescURL has now data type "string/typolink"

FILE: longdescURL has now data type "string/typolink"

IMAGE: longdescURL has now data type "string/typolink"

IMGTEXT: longdescURL has now data type "string/typolink"

h2. Pending documentation for doc_core_api

In the part "Wizard scripts in the core" there is browse_links.php. This gets an extra configuration option:

blindLinkFields -> string -> Comma separated list of fields that should not be displayed. Possible values are target, title, class and params. By default, all fields are displayed.

h2. Current status

Current state of HTML5 support in TYPO3 BLE Accessibility

FIGURE and FIGCAPTION

instead of table and caption element

headers 

using HEADER tag instead of wrapping div

when used with subheader HGROUP is used

TIME is used when the date has to be displayed

menus

like menu sitemap uses a NAV element around it

links

Links produced by typolink where not represented as NFC

tables

Removed summary attribute only for HTML5 which is not supported anymore. There is no real alternative for it. Nothing is done with this information in HTML5

Different solution for cellpadding/cellspacing (obsolete)

Change in border attribute which has a totally different meaning in HTML5

Current state of wai-aria support in TYPO3 BLE Accessibility

longdesc attribute is not supported in HTML5, instead aria-describedby construction is used

Current state of WCAG 2.0 support in TYPO3 BLE Accessibility

Possibility to add a "bypass navigation block" link to each option in cObj Menu/Sitemap

Possibility to add wrapping MAP tag around navigation blocks

Other fixed things in TYPO3 BLE Accessibility

W3C validation on all doctypes TYPO3 supports (css_styled_content & cms)

target attribute is only added when explicitly set in doctypes which do not support frames

Inline CSS has been removed. Markup has changed for cObj "Text with Images" and "Images" to get rid of all these inline width styles. When not possible to remove specific margins or widths, this has been moved to a css file instead of inline.

Cleaner markup where ever possible

cObj File links possibility to add alt text to file icons/thumbnails

css_styled_content Content Objects Search, Form are not covered by the project because other solutions will be used. The work on the MEDIA element is still in progress.

There is one problem with markup of cObj "Text with images" and "Images" together with WCAG 2.0. Table construction is used for this when there is a caption to get rid of all these width styles. CAPTION is not allowed by WCAG 2.0 for layout tables.

WCAG 2.0 does not describe how to handle HTML5, which is awkward.