[TYPO3-hci] TYPO3 Backend and Accessibility
Steffen Kamper
info at sk-typo3.de
Fri Jan 28 16:47:25 CET 2011
Hi,
Am 28.01.2011 11:20, schrieb "Christian Müller (Kitsunet)":
> On 28.01.2011 10:30, Steffen Kamper wrote:
>> Hi,
>>
>> Am 28.01.2011 09:19, schrieb "Christian Müller (Kitsunet)":
>>> For now we rely only on ExtJS for the interface in v5, which probably
>>> makes it hard (impossible). Upcoming ExtJS 4 (we will switch) should
>>> offer cleaner HTML, so then we have a better chance (still JS is
>>> needed).
>>>
>>
>> ExtJS (or Javascript) and accessibility doesn't exclude eachother. It's
>> no problem to make an ExtJS application accessible. You only have to put
>> some energy into.
>>
>> vg Steffen
>
> Agree, but ExtJS sometimes creates very ugly html which hardly can
> qualify as accessible, but that should get better with ExtJS 4. Anyway
> of course you can take the time to change the rendering of everything. I
> will bring the idea to the v5 team to see at what point we can work on
> that.
>
i thought the same, but accessibility has defined rules, and complex
nested html doesn't violate those rules.
I remember well when i had to prepare TYPO3 sites for accessibility
tests, and mostly it was about menus and links and semantic structure of
headers etc.
vg Steffen
More information about the TYPO3-team-hci
mailing list