TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

Semantically styling breadcrumbs—What’s wrong with » › / •?

33 pointsby jimsteinhartover 14 years ago

7 comments

goodsideover 14 years ago
The blind are blind, not retarded. Sighted people infer the meaning of breadcrumbs from context and blind people can do the same. The "&#62;" symbol didn't start out as being an international breadcrumb sign--it had a different meaning and was adapted to the metaphorically similar purpose of showing the relative size of subsections. There's nothing stopping blind people from making the same inference when they read "Home greater-than Articles greater-than Movie reviews".<p>If he thinks the blind can't figure out breadcrumbs, he'd probably spit his coffee if he saw one programming.
评论 #1894104 未加载
评论 #1894069 未加载
评论 #1893807 未加载
derefrover 14 years ago
On a tangent: when parsing &#60;title&#62;s, does Google comprehend "page &#60; section &#60; site" the same as "site &#62; section &#62; page"? Up until now, I used the former, because it reads better in squished tabs and bookmarks better—but am I losing Google juice because of that?
Yaggoover 14 years ago
I wonder how screen readers interpret the following:<p><pre><code> #breadcrumbs li:after { content: "&#62;"; }</code></pre>
评论 #1893846 未加载
xentroniumover 14 years ago
So slash is the best solution out there, I guess?
评论 #1893722 未加载
JoachimSchipperover 14 years ago
This seems somewhat silly - isn't the most useful part of the whole "semantic web" that machines can process it easily? I do agree that Google's implementation is rather... ad-hoc.
Tichyover 14 years ago
Hm, a &#62; b &#62; c is supposed to be worse than a (image) b (image) c? I disagree. The style="breadcrumb" approach also sucks (overly verbose and complicated).
Shorelover 14 years ago
This seems to be something to fix and standardize in HTML5.