- From: Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>
- Date: Thu, 17 Oct 2013 22:58:26 +0200
- To: "Jens O. Meiert" <jens@meiert.com>
- Cc: W3C Public HTML <public-html@w3.org>
Jens O. Meiert, Thu, 17 Oct 2013 15:34:55 -0500: >>> it would help if you could elaborate on the decision to use lists. My view >>> is that they’re not necessary. >> >> What about what Niels Matthijs said, in a comment to your post: [1] >> >> ]] When you don’t want lists, then at least use block elements to >> differentiate between element. With inline elements a breadcrumb >> becomes a single “sentence” which makes no sense at all. Each link is a >> separate entity, not part of an inline expression. [[ > > That depends on what problem we’re trying to solve now. Is reading > breadcrumbs as a sentence a problem? I couldn’t test but “Home [pause] > Foo [pause] Bar” does not look like an issue to me. That pause normally just means 'between two words'. And is it certain that each link is just a single word? > Even without a > pause a user likely understands what’s going on, which means there’s > no reason to add more markup. Let's say we *had* a <breadcrumb> element, isn't it likely that the links inside the element would be treated more like clickable list items, then? Why do you, on your own web site (meiert.com), use a <ul> list for the navigation links on top of each page? Is it a problem if those links are read as a sentence? In text layout - that is: in textual browsers and other user environments with few effects, I’d say that lists are practical as it clearly separates the lists, visually and semanticlaly. I am also not a screen reader user, but it seems to me that it could matter to such users if the link collection is read as a chain of word rather than as list of links. -- leif halvard silli
Received on Thursday, 17 October 2013 20:58:56 UTC