11893 2011-01-27 15:20:25 +0000 define lexical processing rules for ARIA attributes 2013-01-21 13:02:10 +0000 1 1 1 Unclassified HTML WG LC1 HTML5 spec unspecified PC All RESOLVED FIXED a11y, a11ytf, aria, TrackerIssue P3 normal --- 11891 11892 1 mike faulkner.steve chuck cooper hans.hillen ian laura.lee.carlson mike public-html-a11y public-html-admin public-html-wg-issue-tracking rubys schwer public-html-bugzilla oldest_to_newest 44803 0 mike 2011-01-27 15:20:25 +0000 per http://www.w3.org/2011/01/aria-lexical-processing it is my understanding that the PFWG believes the rules for lexical processing of ARIA attributes in HTML should be defined in the HTML5 spec, along with the rules for processing of ARIA attributes in embedded content in other languages within HTML documents (e.g., SVG and MathML). This is therefore a request to change the spec to add such processing rules in the appropriate places within the spec. 44974 1 cooper 2011-02-01 16:43:20 +0000 Bug triage sub-team thinks the HTML A11y TF should process this. 46044 2 ian 2011-02-25 09:50:48 +0000 Makes sense. What's the spec I should use as the reference for these rules? 46474 3 schwer 2011-03-07 22:00:06 +0000 We are drafting spec. text at the HTML Accessibility Face to Face in San Diego (March 19th and 20th) to go into section 3.2.6 (The ARIA section). We would welcome your participation Ian. 48573 4 schwer 2011-05-17 21:12:40 +0000 Mike Cooper is suppose to be submitting the change modifications for this. 53258 5 mike 2011-08-04 05:12:02 +0000 mass-move component to LC1 54824 6 ian 2011-08-12 22:08:48 +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: Did Not Understand Request Change Description: no spec change Rationale: Awaiting requested information. 55117 7 schwer 2011-08-15 17:18:07 +0000 This was a specification to the ARIA section to describe how ARIA attributes are process. One case in point: ARIA booleans are handled different from HTML booleans as you must pass a "true" value for an ARIA boolean attribute to be true vs. having say: <dive role="checkbox" aria-checked> as you are able to do in HTML. I will poke Michael on this as he has had this to do item since January of 2011. 62675 8 cooper 2012-01-13 18:58:32 +0000 Adding TrackerRequest keyword. The proposed tracker issue is: aria-processing: Define complete processing requirements for ARIA attributes ARIA processing was previously raised in a number of issues, particularly ISSUE-129 (chair decision on ISSUE-129 http://lists.w3.org/Archives/Public/public-html/2011Mar/0005.html). The ARIA sub-team has continued work on details for this and expects to be able to provide a complete change proposal that will address this and related bugs. 62792 9 rubys 2012-01-16 23:03:12 +0000 https://www.w3.org/html/wg/tracker/issues/199