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 11893 - define lexical processing rules for ARIA attributes
Summary: define lexical processing rules for ARIA attributes
Status: RESOLVED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: LC1 HTML5 spec (show other bugs)
Version: unspecified
Hardware: PC All
: P3 normal
Target Milestone: ---
Assignee: steve faulkner
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords: a11y, a11ytf, aria, TrackerIssue
Depends on:
Blocks: 11891 11892
  Show dependency tree / graph
 
Reported: 2011-01-27 15:20 UTC by Michael[tm] Smith
Modified: 2013-01-21 13:02 UTC (History)
11 users (show)

See Also:

Attachments

Description Michael[tm] Smith 2011-01-27 15:20:25 UTC 
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.
Comment 1 Michael Cooper 2011-02-01 16:43:20 UTC 
Bug triage sub-team thinks the HTML A11y TF should process this.
Comment 2 Ian 'Hixie' Hickson 2011-02-25 09:50:48 UTC 
Makes sense. What's the spec I should use as the reference for these rules?
Comment 3 Rich Schwerdtfeger 2011-03-07 22:00:06 UTC 
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.
Comment 4 Rich Schwerdtfeger 2011-05-17 21:12:40 UTC 
Mike Cooper is suppose to be submitting the change modifications for this.
Comment 5 Michael[tm] Smith 2011-08-04 05:12:02 UTC 
mass-move component to LC1
Comment 6 Ian 'Hixie' Hickson 2011-08-12 22:08:48 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: Awaiting requested information.
Comment 7 Rich Schwerdtfeger 2011-08-15 17:18:07 UTC 
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.
Comment 8 Michael Cooper 2012-01-13 18:58:32 UTC 
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.
Comment 9 Sam Ruby 2012-01-16 23:03:12 UTC 
https://www.w3.org/html/wg/tracker/issues/199