RE: Separate adjacent links with more than whitespace

JAWS says the word link, IBM HPR just changes the "voice" to indicate that
the text is "different" (i.e.- Hyperlink).

While I detest Bobby worship if you are going for strict compliance you need
to separate the links with more than white space.  I usually use the "bar"
(|), and often even style it "away" using CSS. (or mark up your LIST of
links using list markup (<UL><LI>) and again style away the bullets,
indentation, etc. using CSS)

The point is that there is in fact a distinct separation between the
hyperlinks.  This is useful for users with mobility impairments as well,
including but not limited to Parkinson's, Arthritis, quadriplegics, etc.  In
fact, even younger children lack fine motor skills, although with them
getting younger and younger at the computer screen/mouse/keyboard the
thresh-hold age keeps getting smaller and smaller...

HTH

JF

> -----Original Message-----
> From: w3c-wai-ig-request@w3.org [mailto:w3c-wai-ig-request@w3.org]On
> Behalf Of Steve Vosloo
> Sent: Tuesday, February 04, 2003 9:06 AM
> To: WAI IG
> Subject: Separate adjacent links with more than whitespace
>
>
>
> I have a list of links which I'm placing on top of each other and
> separating with an HTML break statement, like the list of links at the
> bottom of the Tesco Access site. Bobby squeals with WAI checkpoint 10.5:
> Separate adjacent links with more than whitespace. Is this an outdated
> checkpoint? My experience is that screen readers say the word "link"
> before reading a link.
>
> All input greatly appreciated.
>
> Steve
>
>
>
>

Received on Tuesday, 4 February 2003 09:18:13 UTC