Skip to content

Commit 9bc3388

Browse files
fstrrmbgower
fstrr
and
mbgower
authored
Broken link fixes to 2.2 documents (#3481)
- fixed links to Accessible Auth (Minimum) in Accessible Auth (Enhanced) - Updated understanding Understanding: - fix all in-page links - replace references to WCAG 2.1 with WCAG 2.2 - fix links to Accessible Auth criteria in Redundant Entry - fix broken links in techniques → about. (side note: that list hasn't been updated in over three years) - fix links to 2.2 criteria --------- Co-authored-by: Mike Gower 
1 parent 6624385 commit 9bc3388

File tree

18 files changed

+85
-118
lines changed

18 files changed

+85
-118
lines changed

‎techniques/aria/ARIA20.html

Lines changed: 6 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
><html lang="en" xml:lang="en" xmlns="http://www.w3.org/1999/xhtml"><head><title>Using the region role to identify a region of the pagetitle><link rel="stylesheet" type="text/css" href="../../css/editors.css" class="remove"/>head><body><h1>Using the region role to identify a region of the pageh1><section class="meta"><p class="id">ID: ARIA20p><p class="technology">Technology: ariap><p class="type">Type: Techniquep>section><section id="applicability"><h2>When to Useh2>
22
<p>Technologies that support <a href="https://www.w3.org/TR/wai-aria/">Accessible Rich Internet Applicationsa>.p>
33
section><section id="description"><h2>Descriptionh2>
4-
<p>This technique demonstrates how to assign a generic <code class="language-html">regioncode> role to a section of a page so that user agents and assistive technologies may be able to programmatically identify it. The <code class="language-html">regioncode> role demarcates a segment of the page that contains content of significance so that it is more readily discoverable and navigable. The generic region should be used when the section cannot be marked up using a standard document landmark role (see <a href="../aria/ARIA11">ARIA11a>).p>
4+
<p>This technique demonstrates how to assign a generic <code class="language-html">regioncode> role to a section of a page so that user agents and assistive technologies may be able to programmatically identify it. The <code class="language-html">regioncode> role demarcates a segment of the page that contains content of significance so that it is more readily discoverable and navigable. The generic region should be used when the section cannot be marked up using a standard document landmark role (see <a href="ARIA11">ARIA11a>).p>
55
<p>It is important to name regions, because they are generic grouping elements and users will need some way to tell which region they are in. Regions can be named using <code class="language-html">aria-labelledbycode>, <code class="language-html">aria-labelcode>, or another technique. Doing so helps to better expose content and information relationships on the page. The role of <code class="language-html">regioncode> should be used prudently, because if overused they can make the page overly verbose for screen reader users.p>
66
section><section id="examples"><h2>Examplesh2>
77
<section class="example">
@@ -92,15 +92,11 @@

Identifying a portlet with a generic region

9292
<li>Checks #1-3 are true.li>
9393
ul>
9494
section>
95-
section>
96-
<section id="related">
97-
<h2>Related Techniquesh2>
98-
<ul>
99-
<li><a href="../aria/ARIA11">ARIA11a>li>
100-
<li><a href="../aria/ARIA12">ARIA12a>li>
101-
<li><a href="../aria/ARIA13">ARIA13a>li>
102-
ul>
103-
section>
95+
section><section id="related"><h2>Related Techniquesh2><ul>
96+
<li><a href="ARIA11">ARIA11a>li>
97+
<li><a href="ARIA12">ARIA12a>li>
98+
<li><a href="ARIA13">ARIA13a>li>
99+
ul>section>
104100
<section id="resources">
105101
<h2>Resourcesh2>
106102
<ul>

‎techniques/aria/ARIA24.html

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,8 +2,7 @@
22
<html xmlns="http://www.w3.org/1999/xhtml" lang="en">
33
<head>
44
<title>Semantically identifying a font icon with role="img"title>
5-
<link rel="stylesheet" type="text/css" href="https://rawgit.com/w3c/wcag21/master/css/sources.css"/>
6-
<link rel="stylesheet" type="text/css" href="../../css/editors.css"/>
5+
<link rel="stylesheet" type="text/css" href="../../css/editors.css" class="remove" />
76
head>
87
<body>
98

‎techniques/client-side-script/SCR38.html

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -144,9 +144,9 @@

Related Techniques

144144
<h2>Resourcesh2>
145145
<ul>
146146
<li>
147-
<a href="../css/C29#C29-sa1">Using Cookiesa>
147+
<a href="../css/C29#using-cookies">Using Cookiesa>
148148
li>
149-
<li><a href="../css/C29#C29-sa2">Progressive Enhancement and Unobtrusive JavaScripta>
149+
<li><a href="../css/C29#progressive-enhancement-and-unobtrusive-javascript">Progressive Enhancement and Unobtrusive JavaScripta>
150150
li>
151151
ul>
152152
section>

‎techniques/css/C30.html

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@

Description

2121
<p>This technique can be used to meet Success Criterion 1.4.5 or 1.4.9 if a presentation that does not include images of text is available and as long as the user interface control that is provided to allow users to switch to an alternate presentation meets the relevant criteria. Where possible, authors should deliver the presentation that does not include images of text as the default presentation. In addition, the control used to switch should be located near the beginning of the page.p>
2222
<p>A variety of "image replacement" techniques have been developed to address a variety of user agent, configuration and compatibility with assistive technology issues (See resources for more information). While there are a variety of approaches authors may use to replace text, it is important to consider compatibility with assistive technology, whether the technique will work correctly if scripting, CSS, images (or combinations of these) are turned off. Since it can be difficult to find a single solution that works in all cases, this technique recommends the use of a control that allows users to switch to a presentation that does not include an image replacement technique.p>
2323
<div class="note">
24-
<p>This technique can be used in combination with a style switching technique to present a page that is a <a>conforming alternate versiona> for non-conforming content. Refer to <a href="../css/C29">C29a> and <a href="../Understanding/conformance#conforming-alt-versions">Understanding Conforming Alternate Versionsa> for more information.p>
24+
<p>This technique can be used in combination with a style switching technique to present a page that is a <a>conforming alternate versiona> for non-conforming content. Refer to <a href="C29">C29a> and <a href="../../Understanding/conformance#conforming-alt-versions">Understanding Conforming Alternate Versionsa> for more information.p>
2525
div>
2626
section>
2727
<section id="examples">
@@ -106,7 +106,7 @@

Expected Results

106106
<section id="related">
107107
<h2>Related Techniquesh2>
108108
<ul>
109-
<li><a href="../css/C29">C29a>li>
109+
<li><a href="C29">C29a>li>
110110
<li><a href="../failures/F3">F3a>li>
111111
ul>
112112
section>
@@ -123,10 +123,10 @@

Resources

123123
<a href="https://www.digital-web.com/articles/in_defense_of_fahrner_image_replacement/">In Defense of Fahrner Image Replacementa>
124124
li>
125125
<li>
126-
<a href="https://en.wikipedia.org/wiki/Fahrner_Image_Replacement">Fahrner Image Replacementa>
126+
<a href="https://en.wikipedia.org/wiki/CSS_image_replacement">CSS image replacementa>
127127
li>
128128
<li>
129-
<a href="https://www.w3.org/TR/CSS2/colors.html#background-properties">CSS2: 14.2.1 Background properties: 'background-color', 'background-image', 'background-repeat', 'background-attachment', 'background-position', and 'background'a>
129+
<a href="https://www.w3.org/TR/css-backgrounds/">CSS Backgrounds And Borders Modulea>
130130
li>
131131
ul>
132132
section>

‎techniques/failures/F105.html

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@

Applicability

2121
<h2>Descriptionh2>
2222
<p>The objective of this Failure is to describe situations where authors have implemented a function that is operated via a path-based gesture, and no alternative ways of operating this function via simple pointer gestures exist.p>
2323
<p>If you did not create the content and functionality you can find path-based gestures by exploring the content on a touch screen, or checking the page code for the existence of specific event handlers such as touchstart or touchend. See the <a href="../../Understanding/pointer-gestures.html">Understanding document for Pointer Gesturesa> for more on the path-based gestures.p>
24-
<p><em>Note:em> For functionality implemented with a path-based gesture, the possibility of also operating it via the keyboard is beneficial (and may serve to meet Success Criterion 2.1.1 Keyboard). The point of Success Crtierion 2.5.1, however, is to ensure that pointer users who on many devices will have no keyboard available, have alternative ways of operating the function via simple pointer input.p>
24+
<p><em>Note:em> For functionality implemented with a path-based gesture, the possibility of also operating it via the keyboard is beneficial (and may serve to meet <a href="../../Understanding/keyboard">Success Criterion 2.1.1 Keyboarda>). The point of Success Criterion 2.5.1, however, is to ensure that pointer users who on many devices will have no keyboard available, have alternative ways of operating the function via simple pointer input.p>
2525
section>
2626
<section id="examples">
2727
<h2>Examplesh2>
@@ -51,16 +51,18 @@

Expected Results

5151
<section id="related">
5252
<h2>Related Techniquesh2>
5353
<ul>
54-
<li><a href="../general/G216">Providing single point activation for a control slidera>li>
55-
<li><a href="../failures/F101">Failure of Success Criterion 2.5.2 due to activating a control on the down-eventa>.li>
54+
<li><a href="F101">Failure of Success Criterion 2.5.2 due to activating a control on the down-eventa>.li>
55+
<li><a href="../general/G216">Providing single point activation for a control slidera>li>
5656
ul>
5757
section>
58+
6567
body>
6668
html>

‎techniques/failures/F41.html

Lines changed: 14 additions & 25 deletions
Original file line numberDiff line numberDiff line change
@@ -1,30 +1,19 @@
11
><html lang="en" xml:lang="en" xmlns="http://www.w3.org/1999/xhtml"><head><title>Failure of Success Criterion 2.2.1, 2.2.4, and 3.2.5 due to using meta refresh to reload the pagetitle><link rel="stylesheet" type="text/css" href="../../css/editors.css" class="remove"/>head><body><h1>Failure of Success Criterion 2.2.1, 2.2.4, and 3.2.5 due to using meta refresh to reload the pageh1><section class="meta"><p class="id">ID: F41p><p class="technology">Technology: failuresp><p class="type">Type: Failurep>section><section id="applicability"><h2>When to Useh2>
22
<p>HTMLp>
3-
section><section id="description"><h2>Descriptionh2>
4-
<p>
5-
meta
6-
http-equiv of refresh is often used to periodically refresh
7-
pages or to redirect users to another page. If the time interval is too
8-
short, and there is no way to turn auto-refresh off, people who are blind will not have enough time to make their screen
9-
readers read the page before the page refreshes unexpectedly and causes the
10-
screen reader to begin reading at the top. Sighted users may also be
11-
disoriented by the unexpected refresh.p>
12-
section><section id="examples"><h2>Examplesh2>
3+
section>
4+
<section id="description">
5+
<h2>Descriptionh2>
6+
<p><code class="language-html">meta http-equivcode> of <code class="language-html">refreshcode> is often used to periodically refresh pages or to redirect users to another page. If the time interval is too short, and there is no way to turn auto-refresh off, people who are blind will not have enough time to make their screen readers read the page before the page refreshes unexpectedly and causes the screen reader to begin reading at the top. Sighted users may also be disoriented by the unexpected refresh.p>
7+
section>
8+
<section id="examples">
9+
<h2>Examplesh2>
1310
<section class="example">
14-
15-
<p> This is a deprecated example that changes the user's page at regular
16-
intervals. Content developers should not use this technique to
17-
simulate "push" technology. Developers cannot predict how much time
18-
a user will require to read a page; premature refresh can disorient
19-
users. Content developers should avoid periodic refresh and allow
20-
users to choose when they want the latest information. (The number
21-
in the content attribute is the refresh interval in
22-
seconds.)p>
11+
<p>This is a deprecated example that changes the user's page at regular intervals. Content developers should not use this technique to simulate "push" technology. Developers cannot predict how much time a user will require to read a page; premature refresh can disorient users. Content developers should avoid periodic refresh and allow users to choose when they want the latest information. (The number in the content attribute is the refresh interval in seconds.)p>
2312

2413
<pre xml:space="preserve"><code class="language-html"><!doctype>
2514
<html lang="en">
2615
<head>
27-
<title>HTML Techniques for WCAG 2.0</title>
16+
<title>HTML Techniques for WCAG 2</title>
2817
<meta http-equiv="refresh" content="60" />
2918
</head>
3019
<body>
@@ -34,13 +23,13 @@
3423
section>
3524
section><section id="tests"><h2>Testsh2>
3625
<section class="procedure"><h3>Procedureh3>
37-
<p>For a page that uses <code>meta http-equiv="refresh"code>:p>
26+
<p>For a page that uses <code class="language-html">meta http-equiv="refresh"code>:p>
3827
<ol>
39-
<li>Check that the numerical value for seconds until refresh in the <att>contentatt> attribute is present.li>
40-
<li>Check that the numerical value for seconds until refresh in the <att>contentatt> attribute is less than one or greater than 72,000.li>
41-
<li>Check if the page qualifies for Real-time or Essential Exceptions in <a href="/TR/WCAG/#timing-adjustable">Success Criterion 2.2.1 Timing Adjustablea>.li>
28+
<li>Check that the numerical value for seconds until refresh in the <code class="language-html">contentcode> attribute is present.li>
29+
<li>Check that the numerical value for seconds until refresh in the <code class="language-html">contentcode> attribute is less than one or greater than 72,000.li>
30+
<li>Check if the page qualifies for Real-time or Essential Exceptions in <a href="../../Understanding/timing-adjustable">Success Criterion 2.2.1 Timing Adjustablea>.li>
4231
<li>Check if the user is provided an opportunity to turn off, extend, or adjust the timing of the page refresh.li>
43-
<li>Check if the page does not refresh after the duration specified in the <att>contentatt> attribute.li>
32+
<li>Check if the page does not refresh after the duration specified in the <code class="language-html">contentcode> attribute.li>
4433
ol>
4534
section>
4635
<section class="results"><h3>Expected Resultsh3>

‎techniques/failures/F42.html

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@
77
agents including assistive technology may not be able to identify the links
88
in the content as links. They may be recognized as interactive controls but still not recognized as links. Such elements do not appear in the links
99
list generated by user agents or assistive technology.p>
10-
<p><div class="note">It is possible to use the ARIA <code class="language-html">rolecode> attribute to identify an anonymous element as link control for assistive technologies. However, best practice for ARIA calls for <a href="https://www.w3.org/TR/aria-in-html/#first-rule-of-aria-use">making use of native elements whenever possiblea>, so the use of the <code class="language-html">rolecode> attribute to identify anonymous elements as links is not recommended.div>p>
10+
<p><div class="note">It is possible to use the ARIA <code class="language-html">rolecode> attribute to identify an anonymous element as link control for assistive technologies. However, best practice for ARIA calls for <a href="https://www.w3.org/TR/aria-in-html/#rule1">making use of native elements whenever possiblea>, so the use of the <code class="language-html">rolecode> attribute to identify anonymous elements as links is not recommended.div>p>
1111
<p>The <code class="language-html">acode> and <code class="language-html">areacode>
1212
elements are intended to mark up links.p>
1313
section><section id="examples"><h2>Examplesh2>
@@ -116,13 +116,13 @@

Scripting a div element

116116
ul>
117117
section>
118118
section><section id="related"><h2>Related Techniquesh2><ul>
119-
<li><a href="../general/G115">G115a>li>
120119
<li><a href="../failures/F59">F59a>li>
120+
<li><a href="../general/G115">G115a>li>
121121
ul>section><section id="resources"><h2>Resourcesh2>
122122

123123
<ul>
124124
<li>
125-
<a href="https://www.w3.org/TR/wai-aria/">Accessible Rich Internet Applications (WAI-ARIA) Version 1.0a>
125+
<a href="https://www.w3.org/TR/wai-aria/">Accessible Rich Internet Applications (WAI-ARIA)a>
126126
li>
127127
ul>
128128

‎techniques/failures/F47.html

Lines changed: 2 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -1,19 +1,11 @@
11
><html lang="en" xml:lang="en" xmlns="http://www.w3.org/1999/xhtml"><head><title>Failure of Success Criterion 2.2.2 due to using the blink elementtitle><link rel="stylesheet" type="text/css" href="../../css/editors.css" class="remove"/>head><body><h1>Failure of Success Criterion 2.2.2 due to using the blink elementh1><section class="meta"><p class="id">ID: F47p><p class="technology">Technology: failuresp><p class="type">Type: Failurep>section><section id="applicability"><h2>When to Useh2>
22
<p>HTMLp>
33
section><section id="description"><h2>Descriptionh2>
4-
<p>The blink element, while not part of the official HTML or XHTML
5-
specification, is supported by many user agents. It causes any text inside
6-
the element to blink at a predetermined rate. This cannot be interrupted by
7-
the user, nor can it be disabled as a preference. The blinking continues as
8-
long as the page is displayed. Therefore, content that uses
9-
blink fails the Success Criterion because blinking can continue
10-
for more than three seconds.p>
4+
<p>The blink element, while not part of the official HTML specification, is supported by many user agents. It causes any text inside the element to blink at a predetermined rate. This cannot be interrupted by the user, nor can it be disabled as a preference. The blinking continues as long as the page is displayed. Therefore, content that uses blink fails the Success Criterion because blinking can continue for more than three seconds.p>
115
section><section id="examples"><h2>Examplesh2>
126
<section class="example">
137

14-
<p>A product list page uses the blink element to draw
15-
attention to sale prices. This fails the Success Criterion because
16-
users cannot control the blink.p>
8+
<p>A product list page uses the blink element to draw attention to sale prices. This fails the Success Criterion because users cannot control the blink.p>
179

1810
<pre xml:space="preserve"><code class="language-html"><p>My Great Product <blink>Sale! $44,995!</blink></p>code>pre>
1911
section>

0 commit comments

Comments
 (0)