W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > October to December 2006

Re: Best practices for screen readers

From: David Poehlman <david.poehlman@handsontechnologeyes.com>
Date: Fri, 6 Oct 2006 21:43:18 -0400
Message-Id: <2ECC6CC7-E5FD-4E90-9D74-0E668DAFF6E5@handsontechnologeyes.com>
Cc: w3c-wai-ig@w3.org
To: "Christopher Hoffman" <christopher.a.hoffman@gmail.com>

I like your suggestion at the end here.  It sounds much better and  
more thoughtful when done with nnumbers..

On the question of best practices, in many waays, the AT field is  
yong and we're still figguring it out.  I think the best approach for  
now at least is to provide a semantically rich environment that is  
machine readable and let the ATs decide how to handle iit.

On Oct 6, 2006, at 9:11 PM, Christopher Hoffman wrote:

> ...daily users of adaptive
> technology have become accustomed to this type of "shorthand" and  
> they get
> it....

Then again, wheelchair users become accustomed to having to get into
buildings through the back service entrance, and having to wait for the
restaurant's assistant manager to find the keys to operate the lift.  
doesn't make it right.

The variety of ways in which screen readers interpret markup is  
similar to the disparity between the visual browsers back in the browser
wars of the Nineties. Has there been much movement toward intentional
standardization of screen readers, or are the existing standards  
mainly de

Finally, maybe the problem with breadcrumbs and screen readers isn't  
the screen readers keep reading "greater than," "greater than, "greater
than," but rather a poor choice of semantic markup. Bread crumbs are
essentially a sequence of steps, which is best marked up as an  
ordered list.
So the user would hear something like, "How you got here: one - home;  
two -
about us; three - contact us."

Received on Saturday, 7 October 2006 01:43:30 UTC

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