[TYPO3] Accessibility: Typo3 vs other CMS

[Benjamin Todd]

Well said :)

Work told me they needed to get back to a customer that had asked how
accessible we could make Typo3 websites. I asked whether they meant FE
or BE. I then had to tell work that 99% of the time we can do totally
accessible XHTML Strict FE websites in Typo3. But as for the
accessibility of the BE, it's totally :(

 
------------------------
Benjamin Todd
Linux Web Developer
 
b.todd at emnet.co.uk
EMNET, PO Box 559, Nottingham, NG1 3LB
Tel:  +44 (0)115 956 8260
Fax: +44 (0)115 956 8264
 
www.emnet.co.uk
Company Registration No. 3144383 - VAT No. 694 620 609 - Registered
Office: Church House, 13-15 Regent Street, Nottingham NG1 5BS
 
www.emnetsolutions.co.uk
Company Registration No. 05384178 - VAT No. 856 671 781 - Registered
office: Church House, 13-15 Regent Street, Nottingham, NG1 5BS
 
 

-----Original Message-----
From: typo3-english-bounces at lists.netfielders.de
[mailto:typo3-english-bounces at lists.netfielders.de] On Behalf Of Tyler
Kraft
Sent: 30 March 2007 01:54 PM
To: typo3-english at lists.netfielders.de
Subject: Re: [TYPO3] Accessibility: Typo3 vs other CMS

Yes, kind of, except that said bus in the UK needs to accommodate 
roughly 65million people at any possible time, and a lot of those 
65million people might have a disability. So if we say only 1/1000 of 
those people have a disability, they still constitute a large amount of 
the population. And they are often likely to be employed which means 
their work environment must be accessible. And last time I checked the 
point of a CMS was so that people could publish information online - 
they don't need to have sight, or hearing, or even arms in order to 
write copy well....

Obviously a possible work force of 65000 people can't be excluded. But 
its worse than that even, in the fact that there are 45 million people 
in the EU with disabilities[1]. Imagine that we're going to continue to 
ignore the fact that they might have a very very hard time making use of

this CMS. Add onto this fact that the population is ageing and they 
might start to find the BE harder to use or to make more usable for 
there specific age related issue. We will have a hard time justifying 
why this product isn't accessible, especially as other competing 
products will become accessible.

We either accept the idea that we need to take accessibility into 
account or there will come a day when we're left behind by other CMS' 
that do take it into account. Several of our most recent large jobs have

asked how accessible the back end of typo3 is already. And this isn't 
limited to the UK, it is the law in the US and I think in the EU also, 
that the website must be accessible... Not sure they would take kindly 
to a web authoring tool that's not accessible

[1] 
http://ec.europa.eu/information_society/policy/accessibility/z-techserv-
web/index_en.htm

Just my 2c.




Bernd Wilke wrote:

> just my 2cent:
> 
> it sounds like building a bus in mass-production which is accesible by
> every(!) impaired. And don't think the impaired are passengers. the
bus
> should be driven by the impaired.
> 
> Bernd
_______________________________________________
TYPO3-english mailing list
TYPO3-english at lists.netfielders.de
http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-english

Scanned for viruses by MailDefender