RE: WAI-ARIA 1.0 User Agent Implementation Guide is a W3C Candidate Recommendation (Call for Implementations)

Outstanding work!

Regards
Stefan

From: Michael Cooper [mailto:cooper@w3.org]
Sent: Dienstag, 17. Dezember 2013 21:27
To: PF
Subject: Fwd: WAI-ARIA 1.0 User Agent Implementation Guide is a W3C Candidate Recommendation (Call for Implementations)

-------- Original Message --------
Subject:

WAI-ARIA 1.0 User Agent Implementation Guide is a W3C Candidate Recommendation (Call for Implementations)

Resent-Date:

Tue, 17 Dec 2013 17:31:31 +0000

Resent-From:

w3c-ac-members@w3.org<mailto:w3c-ac-members@w3.org>

Date:

Tue, 17 Dec 2013 11:31:28 -0600

From:

Ian Jacobs <ij@w3.org><mailto:ij@w3.org>

To:

w3c-ac-members@w3.org<mailto:w3c-ac-members@w3.org> <w3c-ac-members@w3.org><mailto:w3c-ac-members@w3.org>



Dear Advisory Committee Representative,



I am pleased to announce that WAI-ARIA 1.0 User Agent Implementation Guide is a W3C Candidate Recommendation:

   http://www.w3.org/TR/2013/CR-wai-aria-implementation-20131217/




The approval and publication are in response to this transition request:

   https://lists.w3.org/Archives/Member/chairs/2013OctDec/0283.html




The disposition of Last Call comments is available at:

   http://lists.w3.org/Archives/Public/public-pfwg-comments/2013OctDec/0002.html




There were no Formal Objections.



Patent disclosures relevant to this specification may be found on the Protocols and Formats Working Group's patent disclosure page in conformance with W3C policy:

   http://www.w3.org/2004/01/pp-impl/32212/status



The Protocols and Formats Working Group expects to receive more comments in the form of implementation feedback and test cases. The Working Group believes it will have satisfied its implementation criteria by 17 January 2014.



This Call for Implementations follows section 7.4.3 of the W3C Process Document:

   http://www.w3.org/2005/10/Process-20051014/tr.html#cfi




Thank you,



For Tim Berners-Lee, Director, and

Judy Brewer, WAI Technical Activity Lead;

Ian Jacobs, Head of W3C Communications



==============================================

Quoting from the WAI-ARIA 1.0 User Agent Implementation Guide W3C Candidate Recommendation - 17 December 2013

http://www.w3.org/TR/2013/CR-wai-aria-implementation-20131217/


==============================================



== Abstract ==



This document describes how user agents should support keyboard navigation and respond to roles, states, and properties provided in Web content via WAI-ARIA [ARIA]. These features are used by authors creating accessible rich internet applications. Users often access the content using assistive technologies that rely on platformaccessibility APIs to obtain and interact with information from the page. The WAI-ARIA User Agent Implementation Guide defines how implementations should expose content to accessibility APIs, helping to ensure that this information appears in a manner consistent with author intent. This document is part of the WAI-ARIA suite described in the WAI-ARIA Overview.



== Status of This 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 http://www.w3.org/TR/.




This is a Candidate Recommendation of WAI-ARIA 1.0 User Agent Implementation Guide by the Protocols & Formats Working Group of the Web Accessibility Initiative. It supports the Accessible Rich Internet Applications (WAI-ARIA) [ARIA] Candidate Recommendation, providing information about how user agents should expose ARIA features to platform accessibility APIs. The accessibility API relationships defined here are important to WAI-ARIA, and this document has been tested as part of the testing effort for WAI-ARIA.



WAI-ARIA User Agent Implementation Guide was published as a second Last Call Working Draft on 5 November 2013. Testing has been completed and minor editorial clarifications made. It is being advanced to Candidate Recommendation to signal implementers of its maturity and facilitate preparation for the next stage. Because testing is complete, it is expected to transition to Proposed Recommendation as soon as the 60-day patent review period, that began with the publication of the second Last Call Working Draft, has ended. A history of changes to WAI-ARIA 1.0 User Agent Implementation Guide is available.



=== Exit Criteria ===



The Protocols and Formats Working Group intends to submit this document for consideration as a W3C Proposed Recommendation as soon as the following conditions are met:



        • Define test cases: Identify a set of unit tests, feature tests, dynamic tests, and any additional tests needed to cover all normative absolute (RFC2119 "MUST") requirements;

        • Prepare test files: Prepare test files consisting of HTML 4 content enhanced with WAI-ARIA, or HTML 5 content when features are not supported in HTML 4, to cover all the test cases;

        • Test implementations: Perform these tests on multiple user agents supporting multiple accessibility APIs to demonstrate implementation in at least two user agents and in at least two accessibility APIs;

        • Evaluate test results: Examine results in accessibility APIs and user agents;

        • Verify interoperable results: Find at least two independent interoperable implementations of each requirement where the defined behavior is observed.

The main purpose of the WAI-ARIA 1.0 User Agent Implementation Guide is to define concrete accessibility API mappings for the features of WAI-ARIA 1.0. Consistent with the plan for WAI-ARIA, the requirement to demonstrate implementability is to find any two accessibility API mappings for each WAI-ARIA feature, regardless of platform, as defined by this specification. The guide defines mappings for multiple accessibility APIs, but demonstration of complete mapping of a given API is not feasible because each API is supported by only one or two implementations. To demonstrate that each API referenced in the guide can be supported, at least two ARIA features must be mapped to that API by a user agent.



Most of the testing for the above has been carried out during the testing effort in progress for the WAI-ARIA 1.0 Candidate Recommendation, using this document as a normative supporting resource, and those test results are applicable to the test requirements of this document. During this phase, 683 test cases were defined and have passed in at least two implementations. The completion of the testing for the User Agent Implementation Guide will complete the final step for the ARIA Candidate Recommendation phase. These tests address requirements specific to the User Agent Implementation Guide such as error handling requirements as well as some host language dependencies. 103 test cases have been prepared and 96 of them have at least two passing implementations at the time this documented entered Candidate Recommendation. The seven tests that have not yet met this bar relate to features that have been marked as at risk.



The WAI-ARIA 1.0 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. Several implementations have already been tested; the Protocols and Formats Working Group requests that additional implementations be submitted by 17 January 2014. The Working Group targets 28 January 2014 to complete the testing process and produce the implementation report.



=== Features at risk ===



The Protocols and Formats Working Group has identified four features at risk:



        • Steps 10 and 11 of Controlling focus with tabindex (Section 4.2), which broaden keyboard accessibility by event simulation, may be removed as a normative requirement if interoperable implementations are not found. The remaining steps in this section are not at risk and would not be removed.

        • The Microsoft UIA column in the mapping tables for sections 4.1, 5.4.1, 5.5.1, 5.8.1, 5.8.2, 5.8.3, 5.8.4 may be removed if an implementation is not found. The remaining AAPI columns would not be removed.

        • The Text Alternative Computation (Section 5.6.1.1), step 2B, may be changed from a normative requirement to an informative recommendation if interoperable implementations are not found. This does not affect the rest of the Text Alternative Computation.

        • Section 5.8.4 Special Events for Menus is only implemented on one platform. If an additional implementation is not found, this section will be removed. It would be reconsidered for a future version of this specification.

=== Feedback ===



The Working Group plans to advance this document to Proposed Recommendation as soon as possible, as a key step in advancing the WAI-ARIA 1.0 suite to Recommendation. Therefore, it it plans to process and close comments close to the closing date. The PFWG asks in particular:



        • Are the accessibility APIs in common use today covered?

        • Are all the features needed by accessibility APIs to make rich content accessible addressed?

        • Is the relationship of this document to the WAI-ARIA specification clear?

        • Is it acceptable to remove features marked as at risk if interoperable implementations are not found? If not, are implementations likely?

To comment, send email to public-pfwg-comments@w3.org<mailto:public-pfwg-comments@w3.org> (comment archive). Comments should be made by 24 January 2014. In-progress updates to the document may be viewed in the publicly visible editors' draft.



=== Publication Information ===



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 anything 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.



The disclosure obligations of the Participants of this group are described in the charter.





--

Ian Jacobs <ij@w3.org><mailto:ij@w3.org>      http://www.w3.org/People/Jacobs


Tel:                       +1 718 260 9447