W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > July to September 2010

Re: Microsoft PowerPoint accessibility

From: Wayne Dick <wed@csulb.edu>
Date: Sun, 15 Aug 2010 12:27:44 -0700
Message-ID: <AANLkTi=D3y3YeTUsMkbOsntoc_+=SDD7CQXU-x+RZGu7@mail.gmail.com>
To: Mario Grullon <mario.grullon@optic.gob.do>, "w3c-wai-ig@w3.org" <w3c-wai-ig@w3.org>
I think this discussion is overly complicated.

For each level 1 and 2 criterion just click to "How to meet", find the
relevant case and make sure your power point meets the sufficient
conditions.

Don't worry if a particular screen reader can or cannot read it.  If
you meet the sufficient conditions and a screen reader can't read it
then the screen reader has a bug and you should report it.

In a corporate environment, it is easier to train programmers how to
use the criteria and sufficient techniques than it is to write your
own guidelines or practice weird kludges.

Screen readers should be able to read text boxes if Microsoft
identifies them as such.  Developers should be able to control the
page reading order of text boxes. Microsoft's responsibility is to
make sure and identify text boxes through their API.  Microsoft must
also allow developers to control the reading order, and less competent
authors to receive a correct default reading order.  Screen readers
should read the API and do their job.

Finally, the term accessible PDF is more of an advertising slogan than
a reality.  Well marked up PDF still lacks accessibility support for
1.3.1, separation of presentation from information, structure and
presentation.  There is still no browser or media player that
satisfies the the sufficient techniques for 1.3.1 or 1.3.2.

Wayne Dick
Received on Sunday, 15 August 2010 19:28:20 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 19 July 2011 18:14:34 GMT