W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > April to June 2002

Re: Testing web page accessibility by phone

From: phoenixl <phoenixl@sonic.net>
Date: Wed, 29 May 2002 17:52:26 -0700
Message-Id: <200205300052.g4U0qQdA025540@newbolt.sonic.net>
To: w3c-wai-ig@w3.org


User agent is a factor to consider.  Another way to look at the
accessibility testing of a web page is to see the combination of person,
the user agent and the access technology as a single entity which is
being tested.


> I wonder how much of this depends on the user agent, by which I mean the
> combination of the web browser and screen reader.  As a specific example,
> ever since JAWS for Windows discovered how to grab headings (*real* headings
> with numbers, not just over-sized type that web designers like to pretend
> are headings) and present them in a list with the ability to move
> immediately to a heading, I have suddenly become very enthusiastic about
> proper use of headings to mark off important section divisions in a web
> page.  Prior to the heading support, I have to confess that headings didn't
> do much for me because they were essentially indistinguishable from other
> stuff on the page.  It makes a big difference, to me anyway, if you can gain
> some sort of hierarchical view of a web page rather than just the classic
> never-ending linear version.
> In summary, how a web page "stacks up" may be surprisingly dependent on the
> browser/screen reader used to view it.  Just my two cents, and hopefully not
> too far off the mark.
> Regards,
> Jerry
Received on Wednesday, 29 May 2002 20:53:04 UTC

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