WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: best screen readers for browser testing

for

From: Holly Marie
Date: Jun 19, 2002 11:55AM



----- Original Message -----
From: "John Foliot - bytown internet"

| <mantra>
| CODE TO THE STANDARDS, NOT TO THE SOFTWARE
| </mantra>
| To which I would add the WAI Guidelines as well.
|
| The W3C provides a list of over 35 different "Alternative Web
Browsers"
| (http://www.w3.org/WAI/References/Browsing), including many text to
speech
| alternatives

I agree.
Code to the standards, so when or where it works for various devices,
etc. It works.
Where it does not work, it still delivers as parsed or text only. And
there it is up to the devices or the user to learn how to use the
devices to access the pages that are marked up correctly.

What I would like to add, ... know which items do not have the best
support, and use acceptable alternatives that are marked up correctly in
the documents. [in the case of LONGDESC, it is or may still be necessary
to supply that extra "D" link, not only for non vision users, but also
for all others needing to access the information]. I feel the same way
regarding "Skip Links". This should be visible so that users with
mobility impairments, not able to use a mouse device, can access that
skip function also. There may be individuals with mobility impairments
like Cerebral palsy, that use devices for accessing pages, like sticky
keys, sticks, puff system, etc... that may not be able to read written
words. These users may understand or hear speech, and use screen readers
though they can see. So we really need to be aware of making pages
universally accessible, for a great variety of combinations and users.
These tools for one group can be used for other groups.

And lets not fall into the trap that accessibility is only about one
group. Or even the line of thought... the most serious, or largest
population is thus, and we will code for that. Ditto on the equipment.

holly



----
To subscribe, unsubscribe, or view list archives,
visit http://www.webaim.org/discussion/