To reply to a few people at once: Daisy wrote: > > You can hear the recorded output from JAWS of vertical pipes > (and other > commonly used separator characters) in Peter Krantz's article, "The > Sound of the Accessible Title Tag Separator, > [http://www.standards-schmandards.com/index.php?2004/11/06/6-t > he-sound-of-the-accessible-title-tag-separator]. >
Thanks for that link. Middot sounds like a good alternative, but vertical bar has history and common use on its side. 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. Chris Townson wrote: > > what a list looks like or how you want a list to look are > irrelevant in the > context of this debate. > > also irrelevant is whether the pipe or vertical bar has > accrued implied or > associated meaning through (ab)use. > > semantic mark-up is about utilising the most appropriate tag > available for a > particular thing within the provided specification I don't think it is irrelevant. Meaning = semantics. If my inline pipe-separated list already has the semantics I intend, then making it an html list adds nothing but cruft. I don't see the point of marking it up as a list, only to have to add CSS to change it back to what I intended in the first place. > end of story. Not really. That's what we're here for. cheers, Geoff ****************************************************** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list & getting help ******************************************************
