This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 10493 - "ARIA restricts usage of this role to one per page" is an unclear statement
Summary: "ARIA restricts usage of this role to one per page" is an unclear statement
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML5: The Markup Language (editor: Michael(tm) Smith) (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Michael[tm] Smith
QA Contact: HTML WG Bugzilla archive list
Keywords: a11y, aria, TrackerIssue
Depends on:
Blocks: 10066
  Show dependency treegraph
Reported: 2010-08-29 12:06 UTC by steve faulkner
Modified: 2011-05-10 15:42 UTC (History)
5 users (show)

See Also:


Description steve faulkner 2010-08-29 12:06:58 UTC
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"'
Comment 1 Ian 'Hixie' Hickson 2010-09-07 17:16:46 UTC
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:

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.
Comment 2 contributor 2010-09-07 17:19:16 UTC
Checked in as WHATWG revision r5424.
Check-in comment: remove some inaccurate non-normative statements
Comment 3 steve faulkner 2010-09-09 21:18:21 UTC
a clarification was requested not removal
Comment 4 steve faulkner 2010-10-12 09:07:40 UTC
added to HTML WG Issue
Comment 5 Martin Kliehm 2011-05-10 15:42:00 UTC
The bug triage sub-team doesn't think this bug is TF priority anymore because the related issue has been closed.