[TYPO3-hci] Kickoff: TYPO3 4.1 (suggestions)

[Benjamin Mack]

Hey,

I agree with Dmitry. Accessibility is nice, but not necessary for TYPO3 
admins. It is necessary for the frontend, that's for sure. But the TYPO3 
Backend cannot work run without JavaScript (already), so Christophers 
statement "fall back on existing page-refreshing ... when javascript is 
not present" is not possible at all. So now, if we use javascript OR 
javascript w/ AJAX activity shouldn't bother much. Also it is true that 
this would be an aweful lot of work to do.

So here would be my suggestion: Make the FE-editing accessible so 
handicaped editors can work with the FE-mode. Would be way less work.

The only thing I see with AJAX (has little to do with Accessibility) is 
the "Back-Button" problem since a bunch of my clients / editors are 
comfortable with it.

greetings,
benni.
-SDG-


Dmitry Dulepov wrote:
> Hi!
> 
> Christopher wrote:
>> But in any case, even if we were to decide to ignore item 6.3 
>> altogether, the core parts of the BE could probably be made to comply, 
>> without much difficulty, with all of WCAG 1 and 2 and most of 3--meeting 
>> as many guidelines as possible is definitely the preferable course.
> 
> Who exactly needs this? Typo3 is not easy to learn and I afraid it will 
> be even harder for people with visual disabilities (if possible at all). 
> They will not use typo3 BE anyway. Thus I do not think it is worth 
> spending time on developing "accessible" BE at all. It is the same as 
> developing aircraft cabin accessible. So far no one did that and no one 
> will do I think. It is simply not worth spending so much resources on it 
> if one person of a million may be (!) will use it.
> 
>> Plus, given that there is some interest in expanding TYPO3's userbase 
>> into government and public institutions, accessibility will have to be 
>> pursued at some point or other--and it'd be best to do it during the 
>> 4.5-5.0 refactoring instead of rebuilding everything twice!
> 
> Public institutions already use typo3: many universities, non-profit 
> organizations, etc. They use due to features, not due to accessibility.
> 
> Typo3 output is accessible since meets w3c standards. As to BE, it is 
> for limited professionals only, nothing prevents any organization from 
> using it (if they can manage to learn it of course). US government uses 
> non-accessible Boeing aircrafts with pleasure even though their "BE" 
> (cabin) is totally not "accessible".
> 
>