This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
The example code uses a related set of links to define the breadcrumb navigation, but does not use a list element, so there is no way for assistive technology to convey the hierarchy or relationship between the links. The example should probably group the links in a list element, and should also provide some sort of text equivalent to explain the purpose of each list and convey the difference between the two types of breadcrumb lists.
Per the proposal at http://lists.w3.org/Archives/Public/public-html-a11y/2010Jan/0245.html, the HTML A11Y TF does not plan to formally work on this issue at this time. This does not mean the TF has no interest in it, but does not have immediate plans to work on it. The TF may review the issue in the future.
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Did Not Understand Request Change Description: no spec change Rationale: I don't understand. It's not a list, it's a breadcrumb trail. Should I include some text pointing out that ATs are expected to read out punctuation between links like ">" to indicate the trail? Incidentally, the statement "there is no way for assistive technology to convey the hierarchy or relationship between the links" is wrong the whole point of these rel values is to provide the semantics needed for ATs to do exactly that (convey the hierarchy and relationships).