WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Is source ordered content accessible?

for

From: Jim Allan
Date: Jan 13, 2011 12:54PM

Heading Navigation should be built into a browser.

Opera has had navigation by heading since it started.

Firefox has extension that let you navigate by heading
Heading Map https://addons.mozilla.org/en-US/firefox/addon/7203/
University of Illinois Urbana Accessibility extension
https://addons.mozilla.org/en-US/firefox/addon/5809/

Heading navigation is part of the User Agent Accessibility Guidelines
2.0 (http://www.w3.org/WAI/UA/2010/ED-UAAG20-20101117/). If you want
an accessibility feature, let your browser manufacturer know. Ask them
to meet the User Agent Accessibility Guidelines. The working group is
always interested in comments on the working draft. You can follow our
work at http://www.w3.org/WAI/UA/

Jim Allan (co-chair W3C User Agent Accessibility Working Group)

On Thu, Jan 13, 2011 at 1:36 PM, Pollard, Larry W. (DRS)
< <EMAIL REMOVED> > wrote:
> As I am reading this post, I am in the process of writing new state
> standards for E-learning accessibility and using screen readers:
>
> Tabbing from link to link is a way of skimming web content, especially
> if users are trying to find a particular section of a web site.
>
> Implication 1: Links should make sense out of context. Phrases such as
> "click here," "more," "click for details," and so on are almost
> completely meaningless when read out of context. At the same time, it
> would be overkill to ensure that every detail about a link destination
> is discernable by listening to the link context. Users would not want to
> hear "Products page on which a list of all of our products are
> presented, including software products and training products, with a
> list of prices and availability by region (this page uses the same
> navigation template as the page you are now on)." Perhaps a better
> alternative would be a link that simply says "Products."
>
> Implication 2: Place the distinguishing information of links at the
> beginning of a link. Do not put extra information first, For example, do
> not say "Link opens in a new window: Products." Instead, say "Products
> (opens in a new window)" (or something along those lines). This is
> especially important in this example if several links open in a new
> window. With the explanatory information first instead of the main
> information, screen reader users would have to listen to the phrase
> "link opens in a new window" repeatedly. They will have a harder time
> distinguishing between different links, or at least it will take them
> longer.
> Screen reader users sometimes obtain an alphabetically organized list of
> links
>
> Screen readers allow users to extract the links into an alphabetically
> organized list, using a keyboard shortcut within their screen reader
> software for that purpose. This is especially useful if they have an
> idea of what letter the link they are looking for starts with.
>
> Implication: Use link words and phrases that can be intuitively
> organized in alphabetical order. For example, the phrase "contact us" is
> a common one that users may want to access. If the link says "you can
> contact us," or "how to contact us," or some other phrase that is less
> intuitive, users may have a more difficult time finding the link.
>
> Larry. Pollard
> Accessibility Webmaster
> Department of Rehabilitative Services
>
>
>
>