8700 2010-01-10 13:56:57 +0000 modify contentinfo mapping and conformance 2010-10-04 14:47:41 +0000 1 1 1 Unclassified HTML WG pre-LC1 HTML5 spec (editor: Ian Hickson) unspecified PC All RESOLVED FIXED a11y, aria, NE P2 normal --- 1 faulkner.steve ian ian mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 30847 0 faulkner.steve 2010-01-10 13:56:57 +0000 currently the HTML5 address element is mapped onto the ARIA contentinfo role. [http://dev.w3.org/html5/spec/embedded-content-0.html#annotations-for-assistive-technology-products-aria] This is incorrect. Although it may be appropriate for a containing element that is role=contentinfo to include an address element along with other content, there is not a one to one mapping. a closer approximation for the contentinfo role would be to the footer element , as specified in the spec. current public wai-aria working draft states: Within any document or application, the author SHOULD mark no more than one element with the contentinfo role. [http://www.w3.org/TR/wai-aria/roles#contentinfo] requested modifications to HTML5: remove address to contentinfo mapping. add contentinfo conformance statement in the appropriate section of the spec [http://dev.w3.org/html5/spec/embedded-content-0.html#annotations-for-assistive-technology-products-aria]. 31563 1 ian 2010-02-06 00:28:08 +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: Accepted Change Description: see diff given below Rationale: Concurred with reporter's comments. I handled this like the <header>/banner case. I also applied this to <footer>, and added the contentinfo note to <section>. 31564 2 contributor 2010-02-06 00:29:05 +0000 Checked in as WHATWG revision r4674. Check-in comment: Mention that ARIA restricts 'contentinfo' to one per page, and adjust requirements accordingly. http://html5.org/tools/web-apps-tracker?from=4673&to=4674 31831 3 cooper 2010-02-11 17:26:44 +0000 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.