10467 2010-08-27 14:19:10 +0000 provide headings in the WAI-ARIA section of the spec to make it easier to understand 2010-12-14 17:46:55 +0000 1 1 1 Unclassified HTML WG pre-LC1 HTML5 spec (editor: Ian Hickson) unspecified PC Windows NT RESOLVED WONTFIX a11y, aria P1 major --- 10066 1 faulkner.steve ian ian laura.lee.carlson mike mjs public-html-a11y public-html-admin public-html-wg-issue-tracking w3c public-html-bugzilla oldest_to_newest 38005 0 faulkner.steve 2010-08-27 14:19:10 +0000 consider providing subsections with headings in the WAI-ARIA section of the HTML5 spec, that make it much clear which inofrmation is directed at aithors/implementors/conformance checkers for example see: http://www.paciellogroup.com/blog/misc/HTML5/aria-html5-proposal.html 38006 1 faulkner.steve 2010-08-27 14:21:30 +0000 again without typos consider providing subsections with headings in the WAI-ARIA section of the HTML5 spec that make it much clearer which inofrmation is directed at authors/implementors/ and conformance checkers for example see: http://www.paciellogroup.com/blog/misc/HTML5/aria-html5-proposal.html 38538 2 ian 2010-09-07 17:32:01 +0000 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: Rejected Change Description: no spec change Rationale: It seems pretty clear already. There's only a few paragraphs that apply to only one or the other, and they are already marked up with class=impl, so they get hidden when in author mode. 43354 3 w3c 2010-12-14 17:46:55 +0000 The bug-triage sub-team thinks this is important, but does not require the attention of the whole task force as the ARIA mapping sub-team is able to deal with it and take the appropriate steps. @Ian, we believe it's a matter of invisible meta information: in this regard classes are like @summary. Headings provide a clear structure that is accessible for screenreaders and visible for all users, therefore they are preferable. Classes are machine readable, and filters provide viewing modes, but they are no alternatives to structure.