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 11892 - explicitly state that ARIA states and properties are formal/normative HTML attributes
Summary: explicitly state that ARIA states and properties are formal/normative HTML at...
Status: RESOLVED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: LC1 HTML5 spec (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: steve faulkner
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords: a11y, a11ytf, aria
Depends on: 11893
Blocks:
  Show dependency tree / graph
 
Reported: 2011-01-27 15:11 UTC by Michael[tm] Smith
Modified: 2013-01-21 13:10 UTC (History)
9 users (show)

See Also:

Attachments

Description Michael[tm] Smith 2011-01-27 15:11:48 UTC 
per http://www.w3.org/2011/01/aria-lexical-processing the position of the PFWG is that the HTML5 spec should explicitly state that the ARIA states and properties referenced in the spec are a formal/normative part of the HTML language, on par with all other attributes that are a normative/formal part of the language

So some kind of statement to that effect needs to be added to  http://dev.w3.org/html5/spec/content-models.html#annotations-for-assistive-technology-products-aria
Comment 1 Michael Cooper 2011-02-01 16:43:02 UTC 
Bug triage sub-team thinks the HTML A11y TF should process this.
Comment 2 Ian 'Hixie' Hickson 2011-02-16 08:23:50 UTC 
Could you elaborate on the way in which they are not a formal/normative part of the HTML language? What prose would satisfy this request?
Comment 3 Ian 'Hixie' Hickson 2011-05-03 22:09:24 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: see comment 2
Comment 4 Michael[tm] Smith 2011-08-04 05:35:24 UTC 
mass-move component to LC1
Comment 5 steve faulkner 2013-01-21 13:10:55 UTC 
resolved by http://www.w3.org/html/wg/tracker/issues/199