- From: Markku T. Hakkinen <hakkinen@dev.prodworks.com>
- Date: Wed, 15 Jul 1998 17:05:15 -0400
- To: "Jamie Fox" <jfox@fenix2.dol-esa.gov>, "'Paul Adelson'" <paul.adelson@citicorp.com>
- Cc: "'Web Accessibility Initiative'" <w3c-wai-ig@w3.org>
The way we have implemented support for client side image maps in webspeak offers one approach to dealing with links at the top and bottom of the page: we collapse the links of the image map into a single selection, announced as "Image Map Menu - Navigation Bar" (or whatever the audio style sheet and Alt text says). The user can then either select the menu to listen to it, or proceed on with reading the page. This works especially well if the page author supplies a title and alt text for the image map. Mark --- Jamie:: > PW WebSpeak 1.4.3 will read through to the bottom of the page > regardless of > the length on a graphical browser. I am interested to hear the > opinions of > others about the placement of navigation bars at the top or the bottom. > > -Jamie Fox > > ---------- > From: Paul Adelson[SMTP:paul.adelson@citicorp.com] > Sent: Wednesday, July 15, 1998 4:02 PM > To: 'Web Accessibility Initiative' > Subject: Placing generic navigation links > > Is there any consensus on the following, or has anyone had experience or > done usability studies to determine which is better for accessible web > design: > > For a site that has a standard set of links on every page (e.g. Home | > Products | Employment | Contacts), is it better for accessibility to > have those linkes at the top of every page or at the bottom? > > Does the answer change if seeing/hearing the bottom of the page will > occasionally require scrolling the page? In other words, the user may > get used to browsing the site without needing to scroll and then > unknowingly come to a page where either the standard links or the > non-standard links are not visible/screen-readable without scrolling. > > Thanks, > -- Paul > > > >
Received on Wednesday, 15 July 1998 17:04:24 UTC