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 10462 - merge ARIA mapping tables and list
Summary: merge ARIA mapping tables and list
Status: CLOSED LATER
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: PC Windows NT
: P1 major
Target Milestone: ---
Assignee: steve faulkner
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords: a11y, a11ytf, aria
Depends on:
Blocks: 10066
  Show dependency treegraph
 
Reported: 2010-08-27 13:51 UTC by steve faulkner
Modified: 2013-10-09 14:14 UTC (History)
9 users (show)

See Also:


Attachments

Description steve faulkner 2010-08-27 13:51:56 UTC
Consider merging the ARIA mapping tables and list into one table and providing information in the table about what aria properties can be used on each of the html elements.
Suggest the format and level of information provided here:http://www.paciellogroup.com/blog/misc/HTML5/aria-html5-proposal.html
Comment 1 Ian 'Hixie' Hickson 2010-09-07 17:43:02 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:
   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? What list do you want to merge with what table?
Comment 2 steve faulkner 2010-09-07 19:47:01 UTC
(In reply to comment #1)
> 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? What list do you want to
> merge with what table?

the list after the text:
"A number of elements in HTML have no default role and no restrictions on what roles can be applied to those elements"

What is requested is that the role/attribute authoring conformance tables and the list be merged into a table as in http://www.paciellogroup.com/blog/misc/HTML5/aria-html5-proposal.html
Comment 3 Ian 'Hixie' Hickson 2010-09-08 08:25:34 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:
   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Rejected
Change Description: no spec change
Rationale: Ah, I see. That list is non-normative intentionally — it's actually inaccurate, and would have to be dramatically complicated to be made perfectly accurate (as would be needed to put it into a normative table). This is because the normative requirements have subtle complexities like referring to elements that define commands, as opposed to referring only to elements by element name.

Also, I think having the "no restriction" elements in the table would make the table much more difficult to read.
Comment 4 steve faulkner 2010-10-12 09:06:05 UTC
added to HTML WG Issue http://www.w3.org/html/wg/tracker/issues/129
Comment 5 Cynthia Shelly 2010-10-13 20:40:36 UTC
(In reply to comment #3)
> 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: Ah, I see. That list is non-normative intentionally — it's
> actually inaccurate, and would have to be dramatically complicated to be made
> perfectly accurate (as would be needed to put it into a normative table). This
> is because the normative requirements have subtle complexities like referring
> to elements that define commands, as opposed to referring only to elements by
> element name.
> 
> Also, I think having the "no restriction" elements in the table would make the
> table much more difficult to read.

Ian, 
Can you explain why you think this would be more difficult to read?  It seems to me that being able to look up what is allowed on any element, by finding the element in an alphabetical list, would be much easier to read and use.
Comment 6 Martin Kliehm 2010-12-14 17:34:42 UTC
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.
Comment 7 Michael Cooper 2010-12-15 14:42:11 UTC
This is part of HTML-ISSUE-129. There is some debate taking place actively. Therefore bug triage sub-team thinks this is a HTML A11Y TF priority. Adding a11ytf keyword and assigning to Steve Faulkner for ARIA mapping sub-team.
Comment 8 steve faulkner 2013-01-21 13:20:31 UTC
review for HTML 5.1