On 12/11/05, Geoff Pack <[EMAIL PROTECTED]> wrote: > As for lists, the pipe separated menu list is perfectly clear to most people. > What is missing is a clean way to mark it up with HTML. You could use an > unordered list, styled inline, but that is overkill in many cases, and not an > useable if you want the list to be inline when styles are missing or turned > off.
This is the second time I've heard this mentioned. I'm not sure how much we should care about how a page looks when CSS is off. Maybe that's a topic for another thread, but for now, I'll say: - acessibility vs. appearance = accessibility wins - I don't care how a page looks with css off, as long as a list really looks like a list - I don't think users care how a page looks with css off, since technically it's all ugly when that happens - inline lists aren't more usable than vertical lists, or at least there isn't any reason why the direction (horizontal or vertical) implies greater usability - there's no such thing as overkill when it comes to semantics. If we are willing to waste hours on superfluous graphics and neat page dynamic effects, typing the extra markup for a list isn't too much to ask. Besides, it's for the end user... who should be the most important consideration. this is all IMO, I guess, and I'm interested in hearing what others have to say. -- -- Christian Montoya christianmontoya.com ... rdpdesign.com ... cssliquid.com ****************************************************** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list & getting help ******************************************************
