Geoff Pack wrote:
Gunlaug Sørtun wrote:
...I'm just not sure it makes really good sense to add any kind of
separators between links since they don't add any value from a
usability point of view. They are just visuals that may come out as
noise.
I would agree, but for the fact that it violates WAI guideline 10.5:
http://www.w3.org/TR/WAI-WEBCONTENT/#tech-divide-links That 'until
user agents' is a bit vague though. Anyone know? I've heard arguments
that 10.4 (place-holding characters in edit boxes) is redundant now.
AFAIK: 'user agents (including assistive technologies)' are past the
"until" point for most of those checkpoints by now. Not all users may
have upgraded their user agents though, so whether one should focus on
'user agents' or 'users' may be the question here. WAI say 'user
agents', and I'm not going to argue with them as long as my 'users' say
a particular solution is OK :-)
---
Basically, I think navigation links should be contained, marked up or
simply texted in such a way, that it is clear on all levels (css/no
css/assistive technology/whatever) that they _are_ navigation links and
not just links. I don't see the need for lists or any particular
solution, as long as the uniqueness of nav-links is clear.
I don't think we have a working nav-element that will solve all problems
once and for all, so we just have to find the most usable, and hopefully
semantic, solution for each case as we go along.
I do *not* think "creating noise" is a good option - regardless of WAI,
and I clearly do not believe in styling for 'css off'.
regards
Georg
--
http://www.gunlaug.no
******************************************************
The discussion list for http://webstandardsgroup.org/
See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list & getting help
******************************************************
