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

Re: Separate adjacent links with more than whitespace

From: Charles McCathieNevile <charles@sidar.org>
Date: Wed, 5 Feb 2003 08:14:48 +1100
Cc: "Jim Ley" <jim@jibbering.com>, w3c-wai-ig@w3.org
To: Jonathan Chetwynd <j.chetwynd@btinternet.com>
Message-Id: <B0EE5FA8-3885-11D7-995D-000A95678F24@sidar.org>

I don't think that WCAG 1.0 takes this into account terribly clearly - 
proposing updates for the techniques would be one good strategy, and 
ensuring it is on the working group's agenda for WCAG 2 is another.

In principle this could be done either by the author or by the user 
agent. Currently I think user agent support for it is shaky (except 
perhaps in SVG - the news for the HTML imagemaps which are essentially 
the same functionality is not currently good...)



On Wednesday, Feb 5, 2003, at 06:55 Australia/Melbourne, Jonathan 
Chetwynd wrote:

> Easily imagined and said, but do you believe that the guidelines take 
> this into account?
> On Tuesday, February 4, 2003, at 07:39 PM, Jim Ley wrote:
>> "Jonathan Chetwynd" <j.chetwynd@btinternet.com> wrote in message
>>> We use absolute positioning so I'm wondering what the theory is on 
>>> this?
>>> Is there any explicit separation? seems unlikely :-(
>> If you're positioning with CSS, then you can easily provide 
>> characters which
>> are hidden, or positioned elsewhere when css is enabled, this 
>> requirement
>> obviously only applies to the non CSS-P situation.
>>> and finally SVG, how are links supposed to be separated in what has 
>>> the
>>> potential to be a fine mess?
>> User Agents for SVG have to cope with this in a different way, they 
>> are very
>> different mark-up languages, and techniques don't directly translate.
Charles McCathieNevile           charles@sidar.org
Fundación SIDAR                       http://www.sidar.org
Received on Tuesday, 4 February 2003 16:15:12 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 13 October 2015 16:21:22 UTC