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

RE: Use of headings

From: Jamal Mazrui <Jamal.Mazrui@fcc.gov>
Date: Tue, 3 May 2005 10:45:13 -0400
Message-Id: <8C0103F2896CF143AA78F20B29FF281F0717B407@p2pxmb03.fccnet.win.fcc.gov>
To: "Janet Perkins Corbett" <Perky@uwyo.edu>, <webaim-forum@list.webaim.org>, <w3c-wai-ig@w3.org>

In my opinion, the single most helpful thing you can do for a screen
reader user is to place the first page heading at the start of the main
content of the page, after any section of navigation links.  A screen
reader user can then quickly jump over navigational links, when not
needed, and get to the unique contant of the page.  Additional page
headings are also helpful for skipping among subsections of content
within the page.

Hope this helps,

-----Original Message-----
From: w3c-wai-ig-request@w3.org [mailto:w3c-wai-ig-request@w3.org] On
Behalf Of Janet Perkins Corbett
Sent: Monday, May 02, 2005 8:37 PM
To: webaim-forum@list.webaim.org; w3c-wai-ig@w3.org
Subject: Use of headings 


Our university is implementing Sungard-SCT's Luminis portal software,
we're in the development stage.  My role is to ensure that our
implementation is as accessible as it can be. There is much to be
desired about the entire software package, but one thing that I thought
might be do-able is to encourage the use of headings in channels. Here's
my question: do screen reader users depend much on the headings list?  

The current list of headings is empty for most pages. 

The list of links yields something like the following: focus minimize
focus minimize focus minimize delete focus minimize delete j a dash sig

Janet Perkins Corbett
Wyoming INstitute for Disabilities
Received on Tuesday, 3 May 2005 15:48:27 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:36:25 UTC