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

What's new (was Re: modem use limits)

From: Harvey Bingham <hbingham@acm.org>
Date: Sun, 07 Oct 2001 15:34:14 -0400
Message-Id: <5.1.0.14.2.20011007153023.02a2ba30@pop.rcn.com>
To: mailto:
Cc: "Jon Gunderson" <jongund@staff.uiuc.edu>
At 2001-09-25 14:15, Jon Gunderson wrote to EASI:

 > People using screen readers take longer to read the information on web
 > pages since there is little support for higher level navigation to the
 > information contained on the web page.  There is more than just links on
 > many web pages for people to find and read.  Most web pages are also not
 > designed for accessibility, so there is time involved in trying figure out
 > what the information that is "missing".  Even familiar pages are often
 > updated requiring reading of the whole page just to check to see if there
 > are changes.

 > Jon

Jon: you raise an interesting issue:
How does the user learn what if anything is "new".
That seems to be an authoring/WCAG issue.

WCAG 2.0 "Checkpoint 2.1 Provide multiple site navigation mechanisms"

A thread to "what's new" might be appropriate.

A thread to "what's changed since a supplied date"
(possibly based on the last time the site were visited)
could use the user's history of visiting that URL.

The checkpoint refers to site navigation, yet the case Jon suggests for
a single page corresponds to the example given of WCAG1.0 as a single
page needing several navigation mechanisms.

So the checkpoint may well be broadened to include intra-page navigation.

For pages that the user visits often, with primarily static content, 
yet  containing new information, an early link to a region where that new
info resides would be useful. Alternatively, from the first such, the
other new items could be clustered by being in tab order from the first.

Regards/Harvey Bingham
Received on Sunday, 7 October 2001 16:35:30 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:47:16 GMT