W3C home > Mailing lists > Public > public-review-announce@w3.org > October 2016

CR: Accessible Rich Internet Applications (WAI-ARIA) 1.1

From: Notifier <notifier@aries.w3.org>
Date: Thu, 27 Oct 2016 06:15:04 +0000
Accessible Rich Internet Applications (WAI-ARIA) 1.1

https://www.w3.org/TR/2016/CR-wai-aria-1.1-20161027/

feedback due by: 2016-12-16

Abstract


Accessibility of web content requires semantic information about widgets, structures, and behaviors, in order to allow assistive technologies to convey appropriate information to persons with disabilities. This specification provides an ontology of roles, states, and properties that define accessible user interface elements and can be used to improve the accessibility and interoperability of web content and applications. These semantics are designed to allow an author to properly convey user interface behaviors and structural information to assistive technologies in document-level markup. This version adds features new since WAI-ARIA 1.0 [WAI-ARIA-10] to improve interoperability with assistive technologies to form a more consistent accessibility model for [HTML5] and [SVG2]. This specification complements both [HTML5] and [SVG2].

This document is part of the WAI-ARIA suite described in the WAI-ARIA Overview.

Status of the Document


This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current W3C publications and the latest revision of this technical report can be found in the W3C technical reports index at https://www.w3.org/TR/.

This is a Candidate Recommendation of WAI-ARIA 1.1 by the Accessible Rich Internet Applications Working Group of the Web Accessibility Initiative. This is a call for implementations; the Accessible Rich Internet Applications Working Group requests that initial implementations be submitted by 16 December 2016. The Working Group targets 13 January 2017 to complete the testing process and produce the implementation report. A history of changes to WAI-ARIA 1.1 is available in the appendix.

Exit Criteria: The Accessible Rich Internet Applications Working Group intends to exit the Candidate Recommendation stage and submit this document for consideration as a W3C Proposed Recommendation after documenting interoperable implementability of each feature. For each feature, passing test results in at least two different implementations will be documented.

WAI-ARIA 1.1 defines a technology that can be used in multiple host languages and exposes features to various device platforms. Specific implementation guidance for these languages and platforms is provided in a set of Accessibility API Mappings (AAMs), including at time of publication Core AAM, Accessible Name and Description AAM, HTML AAM, Graphics AAM, SVG AAM, and Digital Publishing AAM. Testing WAI-ARIA relies on the guidance in those auxiliary specifications. For each WAI-ARIA feature, successful test results in any two implementations mapping any of the accessibility APIs referenced in any of the AAMs using any host language will be considered sufficient for the purpose of determining implementability and interoperability of WAI-ARIA. It is not as expectation that the AAMs themselves be at Candidate Recommendation or later stage in order to support WAI-ARIA testing.

WAI-ARIA 1.1 builds upon WAI-ARIA 1.0, which met its implementation requirements in February 2014. Only features that are new or changed in WAI-ARIA 1.1 need be tested, as the WAI-ARIA 1.0 implementation report provides implementatibility and interoperability evidence for the remaining features. Features that will be tested for WAI-ARIA 1.1 include: Heading missing required attribute aria-level; Missing required attribute aria-valuenow on separator when focusable; Default values for aria-valuemin, aria-valuemax, and aria-valuenow when they are required for roles scrollbar, slider, and spinbutton; New properties aria-roledescription, aria-keyshortcuts, aria-placeholder, aria-current , aria-modal; Retest grid tests, and similar tests for tables with cell and table as well as new properties aria-colcount, aria-rowcount, aria-colindex, aria-rowindex, aria-colspan, and aria-rowspan; region treated as a type of landmark; region missing required accessible name; New role switch , searchbox , text , none; aria-posinset and aria-setsize on tab and radio; Repeat aria-orientation tests with no value, which now defaults to undefined; checkbox, menuitemcheckbox, menuitemradio, and radio without aria-checked now default to false; Whitespace and empty values on aria-roledescription; Allow child elements of menuitem and treeitem.

To verify the above requirements, the Accessible Rich Internet Applications Working Group will: Define test cases: Identify a set of unit tests, feature tests, dynamic tests, and any additional tests needed to cover all ARIA normative requirements; Prepare test files: Prepare test files consisting of HTML 4 content enhanced with WAI-ARIA, to cover all the test cases; Test implementations: Perform these tests on multiple separate combinations of user agent plus operating system plus accessibility API; Evaluate test results: Examine results in accessibility APIs as defined by the WAI-ARIA User Agent Implementation Guide; Verify interoperable results: Find at least two implementations of each normative requirement where the defined behavior for the respective accessibility API is observed.

The WAI-ARIA 1.1 Implementations page contains further explanation of the terms and expectations above. It also contains up-to-date information about the test suite, test harness, user agents being examined, and interim test results in the draft implementation report. Implementers who wish to include their tools in the test process will find instructions to submit their implementation for consideration.

Features at Risk: The Accessible Rich Internet Applications Working Group has identified the following feature at risk: The aria-keyshortcuts property includes an author requirement for use of modifier keys defined in the UI Events KeyboardEvent key Values specification. If this specification is not ready to advance to Recommendation in time for ARIA to maintain this normative reference, the author requirement will be changed to non-normative guidance and the reference made informative. The aria-roledescription property describes conditions under which user agents must not expose the property. If two implementations of this restriction are not found, this requirement will be removed from the property.

Comments: The Accessible Rich Internet Applications Working Group primarily seeks feedback relation to implementation of WAI-ARIA, but feedback on any aspect of the specification is accepted. When submitting feedback, please consider issues in the context of the companion documents. To comment, file an issue in the W3C ARIA GitHub repository. If this is not feasible, send email to public-aria@w3.org (comment archive). Comments are requested by 16 December 2016. In-progress updates to the document may be viewed in the publicly visible editors&#x27; draft.

This document was published by the Accessible Rich Internet Applications Working Group as a Candidate Recommendation. This document is intended to become a W3C Recommendation. W3C publishes a Candidate Recommendation to indicate that the document is believed to be stable and to encourage implementation by the developer community. This Candidate Recommendation is expected to advance to Proposed Recommendation no earlier than 13 January 2017.

Please see the Working Group&#x27;s implementation report.

Publication as a Candidate Recommendation does not imply endorsement by the W3C Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.

This document was produced by a group operating under the 5 February 2004 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 1 September 2015 W3C Process Document.
Received on Thursday, 27 October 2016 06:15:11 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 27 October 2016 06:15:12 UTC