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

Re: Guideline 10.5 and Table Cells

From: David Woolley <david@djwhome.demon.co.uk>
Date: Wed, 4 Jul 2001 08:14:51 +0100 (BST)
Message-Id: <200107040714.f647Epk13146@djwhome.demon.co.uk>
To: w3c-wai-ig@w3.org
> That sounds like a user agent problem to me.  The links are
> clearly separated by markup; it's not my fault that your user

The whole point of the rule is user agent behaviour.  </a><a> i
completely obvious in the markup.  I seem to remember that there are
two issues, one is to do with non-visual presentation (e.g. speech)
and the other is that some browsers (and these days most style sheets)
don't highlight spaces within links (style="text-decoration: none").

Unless you display table borders (and the first thing that people learn
these days, after the fact that *all* web pages are just nested tables,
is how to turn off table cell borders), the gap between the links is
just like it would be with spaces (except, sometimes, wider).  If you
do have table cell borders displayed, Lynx is possibly the only browser
that has real problems, when used visually, because the level of table
formatting required is incompatible with fast, single pass, rendering
and limited effective page width (speed is one of the main reasons for
sighted users to use Lynx - there are other text only browser that 
attempt to render tables, but at the expense of speed).

(I believe Lynx can be configured to change background colours, so you
can see the spaces, but that is ugly, as it goes against the idea that
hyper text documents are normal documents with some text annotated as 
links, by making the links too intrusive.  This is why people like 
turning off the underlines, except that they still make the links 
intrusive by using "click here".)
Received on Wednesday, 4 July 2001 09:13:32 UTC

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