- From: Kynn Bartlett <kynn-edapta@idyllmtn.com>
- Date: Tue, 03 Jul 2001 21:36:12 -0700
- To: David Woolley <david@djwhome.demon.co.uk>
- Cc: w3c-wai-ig@w3.org
At 03:34 PM 7/3/2001 , David Woolley wrote:
> > If a series of links are created in separate table
> > cells do they still need to be separated by non-link
> > printable characters?
>Yes. Because the the table cell boundaries may not be
>presented to the end user.
That sounds like a user agent problem to me. The links are
clearly separated by markup; it's not my fault that your user
agent isn't presenting the boundaries to you.
<table>
<tr>
<td><a href="http://kynn.com/">Kynn's Homepage</a></td>
<td><a href="http://kynn.com/cam/">KynnCam</a></td>
</tr>
</table>
The delineation of the links above is completely and utterly
unambiguous in the markup. If there is a problem with the
presentation of the links then it is the fault of the user agent,
is it not?
<ul>
<li><a href="http://kynn.com/">Kynn's Homepage</a></li>
<li><a href="http://kynn.com/cam/">KynnCam</a></li>
</ul>
Likewise, the two are clearly separated by markup in the example
above; and yet a (silly) user agent could likewise refuse to
present the "boundaries" of the LI elements. Surely there is not
a need to introduce printable non-link characters there?
<div>
<a href="http://kynn.com/">Kynn's Homepage</a>
<span> | </span>
<a href="http://kynn.com/cam/">KynnCam</a>
</div>
There's certainly a need here, however.
--Kynn
PS: I'm about 50% playing the devil's advocate here. I believe
there are some cases in which you do have to make allowances
for the fact that certain user agents _don't_ do what they
should, but I think it's also necessary to identify the root
cause as defective browsers!
--
Kynn Bartlett <kynn@reef.com>
Technical Developer Liaison
Reef North America
Accessibility - W3C - Integrator Network
Tel +1 949-567-7006
________________________________________
BUSINESS IS DYNAMIC. TAKE CONTROL.
________________________________________
http://www.reef.com
Received on Wednesday, 4 July 2001 00:37:04 UTC