10493 2010-08-29 12:06:58 +0000 "ARIA restricts usage of this role to one per page" is an unclear statement 2011-05-10 15:42:00 +0000 1 1 1 Unclassified HTML WG HTML5: The Markup Language (editor: Michael(tm) Smith) unspecified PC All RESOLVED FIXED a11y, aria, TrackerIssue P2 normal --- 10066 1 faulkner.steve mike ian laura.lee.carlson public-html-a11y public-html-admin w3c public-html-bugzilla oldest_to_newest 38163 0 faulkner.steve 2010-08-29 12:06:58 +0000 Currently the aria section states for certain elements "ARIA restricts usage of this role to one per page" this is too vague. suggest changing it to something more accurate such as: 'usage of this role is restricted to one per parent element with a role="document"' 38530 1 ian 2010-09-07 17:16:46 +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: Partially Accepted Change Description: see diff given below Rationale: I just removed the parentheticals altogether, since they were a bit out of place... everything in ARIA has restrictions, it was a bit weird just to call these out specifically. 38533 2 contributor 2010-09-07 17:19:16 +0000 Checked in as WHATWG revision r5424. Check-in comment: remove some inaccurate non-normative statements http://html5.org/tools/web-apps-tracker?from=5423&to=5424 38761 3 faulkner.steve 2010-09-09 21:18:21 +0000 a clarification was requested not removal 41025 4 faulkner.steve 2010-10-12 09:07:40 +0000 added to HTML WG Issue http://www.w3.org/html/wg/tracker/issues/129 48445 5 w3c 2011-05-10 15:42:00 +0000 The bug triage sub-team doesn't think this bug is TF priority anymore because the related issue has been closed.