|
20 | 20 | </section> |
21 | 21 |
|
22 | 22 | <section id="sotd"> |
23 | | - <p> |
24 | | - This is an editor's draft by the |
25 | | - <a href="https://www.w3.org/WAI/ARIA/">Accessible Rich Internet Applications Working Group</a> |
26 | | - of the |
27 | | - <a href="https://www.w3.org/WAI/">Web Accessibility Initiative</a>. |
28 | | - It supports the |
29 | | - <a href="" class="specref">WAI-ARIA 1.1</a> [<cite><a href="#bib-WAI-ARIA" class="bibref">WAI-ARIA</a></cite>] |
30 | | - specification, providing detailed advice and examples beyond what would be appropriate to a technical specification but which are important to understand the specification. |
31 | | - </p> |
32 | | - <p> 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 <a href="https://github.com/w3c/aria-practices/milestones?direction=asc&sort=due_date&state=open">Authoring Practices Milestone Plan</a>. </p> |
33 | | - <p> |
34 | | - 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. |
35 | | - The Accessible Rich Internet Applications Working Group asks in particular: |
36 | | - </p> |
37 | | - <ul> |
38 | | - <li>Is it clear how to create accessible Rich Internet Applications?</li> |
39 | | - <li>Is the usage of roles, states, and properties clear? </li> |
40 | | - <li>Are the various types of rich Web content covered? </li> |
41 | | - <li>Are considerations beyond the use of WAI-ARIA sufficiently explained? </li> |
42 | | - <li>Is the relationship of this document to the WAI-ARIA specification clear? </li> |
43 | | - <li>Are the <a href="#aria_ex">design patterns</a> clear?</li> |
44 | | - </ul> |
| 23 | + <p>This is the WAI-ARIA Authoring Practices 1.1 <a href="https://www.w3.org/2017/Process-20170301/#WGNote">Working Group Note</a> by the <a href="https://www.w3.org/WAI/ARIA/">Accessible Rich Internet Applications Working Group</a>. It supports the <a href="https://www.w3.org/TR/wai-aria-1.1/">Accessible Rich Internet Applications 1.1 W3C Recommendation</a> [[wai-aria-1.1]], providing detailed advice and examples beyond what would be appropriate to a technical specification but which are important to understand the specification.</p> |
45 | 24 | <p> |
46 | 25 | To comment, |
47 | 26 | <a href="https://github.com/w3c/aria-practices/issues/">file an issue in the <abbr title="World Wide Web Consortium">W3C</abbr> ARIA Practices GitHub repository</a>, |
48 | 27 | or if that is not possible, send email to |
49 | 28 | <a href=" mailto:[email protected]?subject=Comment%20on%20WAI-ARIA%20Practices%201.1" >[email protected]</a> |
50 | 29 | (<a href="http://lists.w3.org/Archives/Public/public-aria/">comment archive</a>). |
| 30 | + Comments received on the WAI-ARIA 1.1 Authoring Practices may be addressed in a future republication of this document as a Working Group Note, or may be addressed in future versions of WAI-ARIA Authoring Practices. In-progress updates to the document may be viewed in the <a href="https://w3c.github.io/aria-practices/">publicly visible editors' draft</a>. |
51 | 31 | </p> |
52 | 32 | </section> |
53 | 33 |
|
|
0 commit comments