W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > July to September 2002

RE: whitespace, navigation links, styled divs

From: Charles McCathieNevile <charles@w3.org>
Date: Mon, 12 Aug 2002 16:58:21 -0400 (EDT)
To: Steve Vosloo <stevenvosloo@yahoo.com>
cc: <w3c-wai-ig@w3.org>
Message-ID: <Pine.LNX.4.30.0208121649550.14375-100000@tux.w3.org>

Put in something that I can use to visually tell where one link ends and
another one begins.

That is usually very helpful. My biggest complaint about image maps is when
people have vaguely defined images for tightly-defined navigation, which
leads to problems working out what bits of the image are linked, and to what.

I realise this is mostly a question about design aesthetics, and getting
agreement on that is only ever a rough process.

It gets interesting when you want to work on links that are consecutive words
in sentences. One way to do this, depending on the context, is to rewrite the
sentence. But in other cases it is just not possible.

Maybe now it would make sense to ask the WCAG group to change the requirement
so it becomes a user's responsibility to seperate links if they still feel
the need. Does anyone use, or know personally someone who uses, a user agent
that can't cope with two consecutive links that are not seperated by anything
except whitespace? (Or not even that - two images, each a link, not seperated
at all, is a good test case. You can find it on many W3C pages...)

cheers

Chaals


On Mon, 12 Aug 2002, Steve Vosloo wrote:

>
>If we can't use the invisible chars to separate links with more than
>whitespace, what can we do?
>
>Steve
>
>
>
>
>
>-----Original Message-----
>From: w3c-wai-ig-request@w3.org [mailto:w3c-wai-ig-request@w3.org] On
>Behalf Of Julian
>Sent: 10 August 2002 12:59 PM
>To: w3c-wai-ig@w3.org
>Subject: Re: whitespace, navigation links, styled divs
>
>
>
>> For a truly CSS compliant renderer, that is the same as if the span
>> element didn't exist at all.
>
>..and for users with both a truly css compliant browser and a
>screenreader the span wouldn't appear and the links would run together.
>Good point David and I shall stop doing it.
>
>>I think you are abusing display:none to
>> take advantage of bugs in it's implemnetation,
>
>What's wrong with that? In principle I mean, not in relation to this
>particular example which I concede is bad practice.
>
>Julian
>
>----- Original Message -----
>From: "David Woolley" <david@djwhome.demon.co.uk>
>To: <w3c-wai-ig@w3.org>
>Sent: Friday, August 09, 2002 10:05 PM
>Subject: Re: whitespace, navigation links, styled divs
>
>
>>
>> > I have done something similar to that; put a "." in a span after
>> > each
>link
>> > and style it to display:none. I don't think this causes any problems
>
>> > for
>>
>> For a truly CSS compliant renderer, that is the same as if the span
>> element didn't exist at all.  I think you are abusing display:none to
>> take advantage of bugs in it's implemnetation, or a correlation
>> between browser that don't distinguish adjacent links and ones that
>> don't support CSS2.
>>
>
>

-- 
Charles McCathieNevile    http://www.w3.org/People/Charles  phone: +61 409 134 136
W3C Web Accessibility Initiative     http://www.w3.org/WAI  fax: +33 4 92 38 78 22
Location: 21 Mitchell street FOOTSCRAY Vic 3011, Australia
(or W3C INRIA, Route des Lucioles, BP 93, 06902 Sophia Antipolis Cedex, France)
Received on Monday, 12 August 2002 16:58:26 GMT

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