This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
this "<tr role="cell">" is not currently considered a conformance error as you removed any role constraints on table related elements. So suggest replacing it with an example that is actually a conformance error. from the spec: "Errors that involve a conflict in expressed semantics Similarly, to draw the author's attention to mistakes in the use of elements, clear contradictions in the semantics expressed are also considered conformance errors. In the fragments below, for example, the semantics are nonsensical: a row cannot simultaneously be a cell, nor can a radio button be a progress bar. <tr role="cell"> <input type=radio role=progressbar>"
Bug triage sub-team thinks this is not a A11Y TF priority, can be worked out by original filer.
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: Accepted Change Description: see diff given below Rationale: Concurred with reporter's comments. ...though the fact that the spec now allows people to mark rows as cells is pretty crazy.
Checked in as WHATWG revision r6098. Check-in comment: correctness http://html5.org/tools/web-apps-tracker?from=6097&to=6098
> ...though the fact that the spec now allows people to mark rows as cells is > pretty crazy. agreed, but it was your doing.
mass-move component to LC1
removed keywords as is fixed