W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > January to March 2003

Re: Separate adjacent links with more than whitespace

From: David Poehlman <poehlman1@comcast.net>
Date: Tue, 04 Feb 2003 11:07:00 -0500
To: Michael Cooper <michaelc@watchfire.com>, W3c-Wai-Ig <w3c-wai-ig@w3.org>
Message-id: <001d01c2cc67$a332abe0$6501a8c0@handsontech>

<br> is most likely not sufficient.  styling or list mark up would be much
better.

----- Original Message -----
From: "Michael Cooper" <michaelc@watchfire.com>
To: "W3c-Wai-Ig" <w3c-wai-ig@w3.org>
Sent: Tuesday, February 04, 2003 10:54 AM
Subject: RE: Separate adjacent links with more than whitespace



Before I read this reply I was going to post a message saying we're
considering changing Bobby's evaluation to consider links on different lines
(e.g., separated by <br>) as being sufficiently separated. I'm with everyone
on the importance of separated links, and just have the question - are
non-whitespace separators just important for links on the same "line" or is
it also important for links on different lines? I realize the definition of
"line" might depend on the user agent and there might be my answer, that you
can't count on a <br> element as creating the needed separation. But I
wanted to float the idea and see what people think.

Michael

> -----Original Message-----
> From: John Foliot - bytown internet [mailto:foliot@bytowninternet.com]
> Sent: Tuesday, February 04, 2003 9:18 AM
> To: Steve Vosloo
> Cc: W3c-Wai-Ig
> Subject: 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 11:09:47 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 19 July 2011 18:14:08 GMT