|
169 | 169 | WD: "https://www.w3.org/TR/html-aam/", |
170 | 170 | REC: "https://www.w3.org/TR/html-aam/", |
171 | 171 | }, |
172 | | - practicesURLs: { |
173 | | - ED: "https://www.w3.org/WAI/ARIA/apg/", |
174 | | - WD: "https://www.w3.org/WAI/ARIA/apg/", |
175 | | - FPWD: "https://www.w3.org/WAI/ARIA/apg/", |
176 | | - CR: "https://www.w3.org/WAI/ARIA/apg/", |
177 | | - REC: "https://www.w3.org/WAI/ARIA/apg/", |
178 | | - }, |
179 | 172 |
|
180 | 173 | preProcess: [linkCrossReferences, getParticipants], |
181 | 174 | postProcess: [ariaAttributeReferences], |
@@ -236,16 +229,16 @@ <h1>Introduction</h1> |
236 | 229 | creating custom widgets and other web application components. Please see the <a href="https://www.w3.org/WAI/standards-guidelines/aria/">WAI-ARIA Overview</a> for links to related documents |
237 | 230 | for other audiences, such as |
238 | 231 | <cite |
239 | | - ><a href="" class="practices"><abbr title="Accessible Rich Internet Applications">ARIA</abbr> Authoring Practices Guide</a></cite |
| 232 | + ><a href="https://www.w3.org/WAI/ARIA/apg/"><abbr title="Accessible Rich Internet Applications">ARIA</abbr> Authoring Practices Guide</a></cite |
240 | 233 | > |
241 | | - [[WAI-ARIA-PRACTICES-1.2]] that introduces developers to the accessibility problems that WAI-ARIA is intended to solve, the fundamental concepts, and the technical approach of WAI-ARIA. |
| 234 | + that introduces developers to the accessibility problems that WAI-ARIA is intended to solve, the fundamental concepts, and the technical approach of WAI-ARIA. |
242 | 235 | </p> |
243 | 236 | <p> |
244 | 237 | This document currently handles two aspects of <a>roles</a>: user interface functionality and structural <a>relationships</a>. For more information and use cases, see |
245 | 238 | <cite |
246 | | - ><a href="" class="practices"><abbr title="Accessible Rich Internet Applications">ARIA</abbr> Authoring Practices Guide</a></cite |
| 239 | + ><a href="https://www.w3.org/WAI/ARIA/apg/"><abbr title="Accessible Rich Internet Applications">ARIA</abbr> Authoring Practices Guide</a></cite |
247 | 240 | > |
248 | | - [[WAI-ARIA-PRACTICES-1.2]] for the use of roles in making interactive content accessible. |
| 241 | + for the use of roles in making interactive content accessible. |
249 | 242 | </p> |
250 | 243 | <p> |
251 | 244 | Roles defined by this specification are designed to support the roles used by platform <a>accessibility <abbr title="Application Programming Interfaces">APIs</abbr></a |
@@ -329,14 +322,14 @@ <h2>Rich Internet Application Accessibility</h2> |
329 | 322 | <p> |
330 | 323 | For more information see |
331 | 324 | <cite |
332 | | - ><a href="" class="practices"><abbr title="Accessible Rich Internet Applications">ARIA</abbr> Authoring Practices Guide</a></cite |
| 325 | + ><a href="https://www.w3.org/WAI/ARIA/apg/"><abbr title="Accessible Rich Internet Applications">ARIA</abbr> Authoring Practices Guide</a></cite |
333 | 326 | > |
334 | 327 | for the use of roles in making interactive content accessible. |
335 | 328 | </p> |
336 | 329 | <p> |
337 | 330 | Users of alternate input devices need <a>keyboard accessible</a> content. The new semantics, when combined with the recommended keyboard interactions provided in |
338 | 331 | <cite |
339 | | - ><a href="" class="practices"><abbr title="Accessible Rich Internet Applications">ARIA</abbr> Authoring Practices Guide</a></cite |
| 332 | + ><a href="https://www.w3.org/WAI/ARIA/apg/"><abbr title="Accessible Rich Internet Applications">ARIA</abbr> Authoring Practices Guide</a></cite |
340 | 333 | >, will allow alternate input solutions to facilitate command and control via an alternate input solution. |
341 | 334 | </p> |
342 | 335 | <p> |
@@ -383,7 +376,9 @@ <h2>Target Audience</h2> |
383 | 376 | following documents provide important supporting information: |
384 | 377 | </p> |
385 | 378 | <ul> |
386 | | - <li>[[[WAI-ARIA-PRACTICES-1.2]]] addresses authoring recommendations for HTML, and is also of interest to developers of authoring tools and conformance checkers.</li> |
| 379 | + <li><cite><a href="https://www.w3.org/WAI/ARIA/apg/"><abbr title="Accessible Rich Internet Applications">ARIA</abbr> |
| 380 | + Authoring Practices Guide</a></cite> |
| 381 | +addresses authoring recommendations for HTML, and is also of interest to developers of authoring tools and conformance checkers.</li> |
387 | 382 | <li>[[[CORE-AAM-1.2]]] addresses developers of [=user agents=] and <a class="termref">assistive technologies</a>.</li> |
388 | 383 | <li>[[[ACCNAME-1.2]]] also addresses developers of [=user agents=] and <a class="termref">assistive technologies</a>.</li> |
389 | 384 | </ul> |
@@ -851,7 +846,7 @@ <h1>Using <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr></h |
851 | 846 | Complex web applications become inaccessible when <a>assistive technologies</a> cannot determine the <a>semantics</a> behind portions of a document or when the user is unable to effectively |
852 | 847 | navigate to all parts of it in a usable way (see |
853 | 848 | <cite |
854 | | - ><a href="" class="practices"><abbr title="Accessible Rich Internet Applications">ARIA</abbr> Authoring Practices Guide</a></cite |
| 849 | + ><a href="https://www.w3.org/WAI/ARIA/apg/"><abbr title="Accessible Rich Internet Applications">ARIA</abbr> Authoring Practices Guide</a></cite |
855 | 850 | >). <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> divides the semantics into <a>roles</a> (the type defining a user interface element) and <a>states</a> and |
856 | 851 | [=ARIA/properties=] supported by the roles. |
857 | 852 | </p> |
@@ -1001,7 +996,7 @@ <h3>Information for Authors</h3> |
1001 | 996 | it has keyboard focus. The author cannot use <code>:<span class="css-selector">focus</span></code> to style the currently active descendant since the actual focus is on the container. |
1002 | 997 | </p> |
1003 | 998 | <p> |
1004 | | - More information on managing focus can be found in the <a href="practices/keyboard-interface" class="practices">Developing a Keyboard Interface</a> section of the |
| 999 | + More information on managing focus can be found in the <a href="https://www.w3.org/WAI/ARIA/apg/keyboard-interface">Developing a Keyboard Interface</a> section of the |
1005 | 1000 | <cite><abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> Authoring Practices</cite>. |
1006 | 1001 | </p> |
1007 | 1002 | </section> |
@@ -2879,7 +2874,7 @@ <h2>Definition of Roles</h2> |
2879 | 2874 | <p> |
2880 | 2875 | The features and behaviors of combobox implementations vary widely. Consequently, there are many important authoring considerations. See the |
2881 | 2876 | <cite |
2882 | | - ><a href="" class="practices"><abbr title="Accessible Rich Internet Applications">ARIA</abbr> Authoring Practices Guide</a></cite |
| 2877 | + ><a href="https://www.w3.org/WAI/ARIA/apg/"><abbr title="Accessible Rich Internet Applications">ARIA</abbr> Authoring Practices Guide</a></cite |
2883 | 2878 | > |
2884 | 2879 | for additional details on implementing combobox design patterns. |
2885 | 2880 | </p> |
@@ -4078,7 +4073,7 @@ <h2>Definition of Roles</h2> |
4078 | 4073 | <p> |
4079 | 4074 | See the |
4080 | 4075 | <cite |
4081 | | - ><a href="" class="practices"><abbr title="Accessible Rich Internet Applications">ARIA</abbr> Authoring Practices Guide</a></cite |
| 4076 | + ><a href="https://www.w3.org/WAI/ARIA/apg/"><abbr title="Accessible Rich Internet Applications">ARIA</abbr> Authoring Practices Guide</a></cite |
4082 | 4077 | > |
4083 | 4078 | for additional details on implementing a feed design pattern. |
4084 | 4079 | </p> |
@@ -4533,7 +4528,7 @@ <h2>Definition of Roles</h2> |
4533 | 4528 | <p> |
4534 | 4529 | See the |
4535 | 4530 | <cite |
4536 | | - ><a href="" class="practices"><abbr title="Accessible Rich Internet Applications">ARIA</abbr> Authoring Practices Guide</a></cite |
| 4531 | + ><a href="https://www.w3.org/WAI/ARIA/apg/"><abbr title="Accessible Rich Internet Applications">ARIA</abbr> Authoring Practices Guide</a></cite |
4537 | 4532 | > |
4538 | 4533 | for additional details on implementing grid design patterns. |
4539 | 4534 | </p> |
@@ -10217,7 +10212,7 @@ <h5>Presentational Role Inheritance</h5> |
10217 | 10212 | <a href="#managingfocus">Managing Focus</a>. <rref>tablist</rref> elements, which contain a set of associated <rref>tab</rref> elements, are typically placed near a series of |
10218 | 10213 | <rref>tabpanel</rref> elements, usually preceding it. See the |
10219 | 10214 | <cite |
10220 | | - ><a href="" class="practices"><abbr title="Accessible Rich Internet Applications">ARIA</abbr> Authoring Practices Guide</a></cite |
| 10215 | + ><a href="https://www.w3.org/WAI/ARIA/apg/"><abbr title="Accessible Rich Internet Applications">ARIA</abbr> Authoring Practices Guide</a></cite |
10221 | 10216 | > |
10222 | 10217 | for details on implementing a tab set design pattern. |
10223 | 10218 | </p> |
@@ -10458,7 +10453,7 @@ <h5>Presentational Role Inheritance</h5> |
10458 | 10453 | <p> |
10459 | 10454 | <rref>tablist</rref> elements are typically placed near, and usually preceding, a series of <rref>tabpanel</rref> elements. See the |
10460 | 10455 | <cite |
10461 | | - ><a href="" class="practices"><abbr title="Accessible Rich Internet Applications">ARIA</abbr> Authoring Practices Guide</a></cite |
| 10456 | + ><a href="https://www.w3.org/WAI/ARIA/apg/""><abbr title="Accessible Rich Internet Applications">ARIA</abbr> Authoring Practices Guide</a></cite |
10462 | 10457 | > |
10463 | 10458 | for details on implementing a tab set design pattern. |
10464 | 10459 | </p> |
@@ -10564,7 +10559,7 @@ <h5>Presentational Role Inheritance</h5> |
10564 | 10559 | <p> |
10565 | 10560 | <rref>tablist</rref> elements are typically placed near, and usually preceding, a series of <rref>tabpanel</rref> elements. See the |
10566 | 10561 | <cite |
10567 | | - ><a href="" class="practices"><abbr title="Accessible Rich Internet Applications">ARIA</abbr> Authoring Practices Guide</a></cite |
| 10562 | + ><a href="https://www.w3.org/WAI/ARIA/apg/"><abbr title="Accessible Rich Internet Applications">ARIA</abbr> Authoring Practices Guide</a></cite |
10568 | 10563 | > |
10569 | 10564 | for details on implementing a tab set design pattern. |
10570 | 10565 | </p> |
@@ -12722,7 +12717,7 @@ <h2>Definitions of States and Properties (all aria-* attributes)</h2> |
12722 | 12717 | <p> |
12723 | 12718 | Examples using the <code>mixed</code> value of tri-state inputs are covered in the |
12724 | 12719 | <cite |
12725 | | - ><a href="" class="practices"><abbr title="Accessible Rich Internet Applications">ARIA</abbr> Authoring Practices Guide</a></cite |
| 12720 | + ><a href="https://www.w3.org/WAI/ARIA/apg/"><abbr title="Accessible Rich Internet Applications">ARIA</abbr> Authoring Practices Guide</a></cite |
12726 | 12721 | >. |
12727 | 12722 | </p> |
12728 | 12723 | </div> |
@@ -14267,7 +14262,7 @@ <h2>Definitions of States and Properties (all aria-* attributes)</h2> |
14267 | 14262 | Authors SHOULD avoid implementing shortcut keys that inhibit operating system, user agent, or assistive technology functionality. This requires the author to carefully consider both |
14268 | 14263 | which keys to assign and the contexts and conditions in which the keys are available to the user. For guidance, see the keyboard shortcuts section of the |
14269 | 14264 | <cite |
14270 | | - ><a href="" class="practices"><abbr title="Accessible Rich Internet Applications">ARIA</abbr> Authoring Practices Guide</a></cite |
| 14265 | + ><a href="https://www.w3.org/WAI/ARIA/apg/"><abbr title="Accessible Rich Internet Applications">ARIA</abbr> Authoring Practices Guide</a></cite |
14271 | 14266 | >. |
14272 | 14267 | </p> |
14273 | 14268 | <p> |
|
0 commit comments