-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CR Request for ARIA in HTML #350
Comments
Additional information (correct if any are wrong):
|
Note that both the HTML and SVG Accessibility API Mappings are currently in Working Draft state. In the case of the SVG AAM mapping, the reference is to a definition and the usage in ARIA in HTML looks stable independent of the specifics of that definition. For the HTML AAM mapping, there is a stronger dependency but the WG seems to be actively working on this so it can manage the CR exit timeline. |
Transition approved. |
Published -> https://www.w3.org/TR/2021/CR-html-aria-20210706/ |
Document title, URLs, estimated publication date
ARIA in HTML
https://www.w3.org/TR/html-aria/
W3C Candidate Recommendation Snapshot 06 July 2021
Abstract
This specification defines the authoring rules (author conformance requirements) for the use of Accessible Rich Internet Applications (WAI-ARIA) 1.1 and Digital Publishing WAI-ARIA Module 1.0 attributes on [HTML] elements. This specification's primary objective is to define requirements for use with conformance checking tools used by authors (i.e., web developers). These requirements will aid authors in their development of web content, including custom interfaces/widgets, that makes use of ARIA to complement or extend the features of the host language [HTML].
Status
ARIA in HTML is an [HTML] specification module. Any HTML features, conformance requirements, or terms that this specification module makes reference to, but does not explicitly define, are defined in the HTML specification.
This document was published by the Web Applications Working Group as a Candidate Recommendation Snapshot. This document is intended to become a W3C Recommendation.
GitHub Issues are preferred for discussion of this specification. Alternatively, you can send comments to our mailing list. Please send them to [email protected] (subscribe, archives).
Publication as a Candidate Recommendation does not imply endorsement by the W3C Membership. A Candidate Recommendation Snapshot has received wide review and is intended to gather implementation experience.
This Candidate Recommendation is not expected to advance to Proposed Recommendation any earlier than 28 June 2021.
This document was produced by a group operating under the W3C Patent Policy. W3C maintains a public list of any patent disclosures made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains Essential Claim(s) must disclose the information in accordance with section 6 of the W3C Patent Policy.
This document is governed by the 15 September 2020 W3C Process Document.
Link to group's decision to request transition
w3c/html-aria#326
8 people supported.
Changes
None.
Requirements satisfied
None.
Dependencies met (or not)
HTML Accessibility API Mappings 1.0 and SVG Accessibility API Mappings are in WD status, the group believe these features will become stable and widely implemented when ARIA in HTML moves to REC.
Wide Review
The horizontal review result were tracked in #273, and there are no outstanding issues
Issues addressed
No open issues for 1.0. See issues with the label To Do for 1.0
Formal Objections
None.
Implementation
The editors confirmed that the number of features at risk is now zero. An implementation report is also available
Patent disclosures
https://www.w3.org/groups/wg/webapps/ipr
The text was updated successfully, but these errors were encountered: