- This document provides readers with an understanding of how to use WAI-ARIA 1.1 [[WAI-ARIA]] to create accessible rich internet applications. + This document provides readers with an understanding of how to use WAI-ARIA 1.2 [[WAI-ARIA]] to create accessible rich internet applications. It describes considerations that might not be evident to most authors from the WAI-ARIA specification alone and recommends approaches to make widgets, navigation, and behaviors accessible using WAI-ARIA roles, states, and properties. This document is directed primarily to Web application developers, but the guidance is also useful for user agent and assistive technology developers.
@@ -26,10 +26,10 @@ of the Web Accessibility Initiative. It supports the - WAI-ARIA 1.1 [WAI-ARIA] + WAI-ARIA 1.2 [WAI-ARIA] specification, providing detailed advice and examples beyond what would be appropriate to a technical specification but which are important to understand the specification. -This draft includes only a portion of content planned for WAI-ARIA Authoring Practices 1.1. To see plans for the complete guide, review the Authoring Practices Milestone Plan.
+This draft includes only a portion of content planned for WAI-ARIA Authoring Practices 1.2. To see plans for the complete guide, review the Authoring Practices Milestone Plan.
Feedback on the information provided here is essential to the ultimate success of Rich Internet Applications that afford full access to their information and operations. The Accessible Rich Internet Applications Working Group asks in particular: @@ -46,7 +46,7 @@ To comment, file an issue in the W3C ARIA Practices GitHub repository, or if that is not possible, send email to - public-aria@w3.org + public-aria@w3.org (comment archive).
This section is informative.
WAI-ARIA Authoring Practices is a guide for understanding how to use - WAI-ARIA 1.1 to create an accessible Rich Internet Application. + WAI-ARIA 1.2 to create an accessible Rich Internet Application. It provides guidance on the appropriate application of WAI-ARIA, describes recommended WAI-ARIA usage patterns, and explains concepts behind them.
@@ -136,7 +136,7 @@
Testing assistive technology interoperability is essential before using code from this guide in production. - Because the purpose of this guide is to illustrate appropriate use of ARIA 1.1 as defined in the ARIA specification, the design patterns, reference examples, and sample code intentionally do not describe and implement coding techniques for working around problems caused by gaps in support for ARIA 1.1 in browsers and assistive technologies. + Because the purpose of this guide is to illustrate appropriate use of ARIA 1.2 as defined in the ARIA specification, the design patterns, reference examples, and sample code intentionally do not describe and implement coding techniques for working around problems caused by gaps in support for ARIA 1.2 in browsers and assistive technologies. It is thus advisable to test implementations thoroughly with each browser and assistive technology combination that is relevant within a target audience.
@@ -146,7 +146,7 @@
Except in cases where the ARIA Working Group and other contributors have overlooked an error, examples in this guide that do not function well in a particular browser or with a specific assistive technology are demonstrating browser or assistive technology bugs. - Browser and assistive technology developers can thus utilize code in this guide to help assess the quality of their support for ARIA 1.1. + Browser and assistive technology developers can thus utilize code in this guide to help assess the quality of their support for ARIA 1.2.
- A banner landmark identifies site-oriented content at the beginning of each page within a website. Site-oriented content typically includes things such as the logo or identity
+ A banner landmark identifies site-oriented content at the beginning of each page within a website. Site-oriented content typically includes things such as the logo or identity
of the site sponsor, and site-specific search tool. A banner usually appears at the top of the page and typically spans the full width.
A complementary landmark is a supporting section of the document, designed to be complementary to the main content at a similar level in the DOM hierarchy, but remains meaningful
+
A complementary landmark is a supporting section of the document, designed to be complementary to the main content at a similar level in the DOM hierarchy, but remains meaningful
when separated from the main content.
A contentinfo landmark is a way to identify common information at the bottom of each page within a website, typically called the "footer" of the page, including information
+
A contentinfo landmark is a way to identify common information at the bottom of each page within a website, typically called the "footer" of the page, including information
such as copyrights and links to privacy and accessibility statements.
A form landmark identifies a region that contains a collection of items and objects that, as a whole, combine to create a form when no other named landmark is appropriate (e.g. main
+
A form landmark identifies a region that contains a collection of items and objects that, as a whole, combine to create a form when no other named landmark is appropriate (e.g. main
or search).