W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > January to March 2013

Re: Creating an accessible Table of Contents

From: <accessys@smart.net>
Date: Fri, 1 Mar 2013 09:28:32 -0500 (EST)
To: Ramón Corominas <listas@ramoncorominas.com>
cc: Olaf Drümmer <olaf@druemmer.com>, "w3c-wai-ig@w3.org list" <w3c-wai-ig@w3.org>, Vivienne CONWAY <v.conway@ecu.edu.au>
Message-ID: <Pine.LNX.4.60.1303010926110.6155@cygnus.smart.net>
On Thu, 28 Feb 2013, [windows-1252] Ramón Corominas wrote:

> Olaf said:
>> I don't think it is viable in the long run to require that
>> something that is guaranteed to be accessible on all operating
>> systems.

it is ABSOLUTELY critical to require access to all operating system, do 
you wish to totally stifle inovation, prevent anyone from developing a new 
OS, keep those who need access from new OS that may be developed, make it 
easy for developers or to line the pockets of windows??


> Probably not, but WCAG talks about "accessibility support", and therefore 
> "Windows-only" can only be acceptable in a closed environment.
> Moreover, sighted MacOS users don't need to spend more to buy a copy of 
> Windows (and of course would not have to install a complete OS to read a 
> PDF). However, blind MacOS users would have to:
> 1. Buy a copy of Windows
> 2. Install it (at least as a Virtual Machine)
> 3. Install a screen reader that is compatible with Adobe Reader
> So "Windows-only" does not meet the requirement about "same cost, same 
> easiness", and therefore cannot be used to claim accessibility support.
> And, of course, I don't think that excluding all MacOS users, all Linux 
> users, all iOS users, all Android users, among others, can be considered 
> acceptable in terms of "accessibility support".
> Regards,
> Ramón.
Received on Friday, 1 March 2013 14:29:18 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 13 October 2015 16:21:47 UTC