This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
There seems to be no scope attribute for the TD cell in HTML5 but your own website gives an example using it: http://www.w3.org/TR/WCAG-TECHS/H63.html. I strongly believer the scope=row (at least) should be allowed otherwise one must additionally provide a class for the TH element to override the browser styling defaults. The row scope may be data in addition to a header so I feel it is relevant to have scope for a TD cell. Also, I'm assuming from http://www.w3.org/TR/html5/tabular-data.html#attributes-common-to-td-and-th-elements that headers attribute is still supported although I have read numerous accounts where this will be dropped from HTML 5, which would be a mistake considering the coding effort for headers which would have to be "undone". I think backward compatibility here is a must. Respectfully, -Cynthia Shang
(In reply to comment #0) > There seems to be no scope attribute for the TD cell in HTML5 but your own > website gives an example using it: > http://www.w3.org/TR/WCAG-TECHS/H63.html. The WCAG example seems less than ideal. The cell in question is clearly acting as a row header, and so should be marked up as a <th> instead. Allowing @scope on ordinary table-cells (<td>) when it's only intended to be used for header cells (<th>) doesn't seem to benefit anyone. > I strongly believer the scope=row > (at least) should be allowed otherwise one must additionally provide a class > for the TH element to override the browser styling defaults. The row scope may > be data in addition to a header so I feel it is relevant to have scope for a TD > cell. I don't understand this at all. Why must one put a class on a <th> in order to override the browser default styling? Presumably the intent is to make a header cell that looks just like the other cells. This can be done in the ordinary way by using CSS to just select all the <th> elements.
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. Could you elaborate?
http://lists.w3.org/Archives/Public/public-html-a11y/2010Aug/0013.html The bug triage sub-team thinks the HTML A11Y TF does not need to formally follow this bug. Original submitters or other interested parties may choose to continue to push this issue on their own. Notes from the sub-team may follow in a separate comment.