Skip to content

Commit 8613481

Browse files
iadawniadawn
committed
Merge branch 'main' of https://github.com/w3c/wcag 
2 parents 423aadd + f038aa4 commit 8613481

File tree

689 files changed

+1843
-1749
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

689 files changed

+1843
-1749
lines changed

‎conformance-challenges/index.html

Lines changed: 13 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -1,13 +1,13 @@
11
<!DOCTYPE html>
22
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
33
<head>
4-
<meta charset="UTF-8" />
4+
<meta charset="UTF-8"/>
55
<title>Challenges with Accessibility Guidelines Conformance and Testing, and Approaches for Mitigating Them</title>
66
<script src="https://www.w3.org/Tools/respec/respec-w3c-common" class="remove"></script>
77
<script src="../script/wcag.js" class="remove"></script>
88
<script src="respec-config.js" class="remove"></script>
99
<script src="../biblio.js" class="remove"></script>
10-
<link rel="stylesheet" type="text/css" href="../css/sources.css" class="remove" />
10+
<link rel="stylesheet" type="text/css" href="../css/sources.css" class="remove"/>
1111
<style>
1212
.silver {
1313
font-style: italic;
@@ -296,7 +296,7 @@ <h3>Mitigations</h3>
296296
</section>
297297
<section id="Challenge-2">
298298
<h2>Challenge #2: Large, complex, and dynamic websites may have too many changing permutations to validate effectively</h2>
299-
<p>Large websites often have complex content publishing pipelines, which may render content dynamically depending upon a large number of variables (such as what is known about the logged in user and her content preferences, the geographical location that the user is visiting the site from, and the capabilities of the web rendering agent being used). It is difficult, and may not be feasible, to validate every possible publishing permutation with a page-level test, each of which can have an impact on whether that particular rendering of the content at that particular moment conforms.</p>
299+
<p>Large websites often have complex content publishing pipelines, which may render content dynamically depending upon a large number of variables (such as what is known about logged in users and their content preferences, the geographical location that the users are visiting the site from, and the capabilities of the web rendering agent being used). It is difficult, and may not be feasible, to validate every possible publishing permutation with a page-level test, each of which can have an impact on whether that particular rendering of the content at that particular moment conforms.</p>
300300

301301
<section class="mitigation">
302302
<h3>Mitigations</h3>
@@ -984,7 +984,7 @@ <h4>Audio Control
984984
<p>Where non-web software contains audio, especially audio that automatically
985985
plays in certain circumstances (e.g. making a ringing sound to indicate an
986986
incoming call) &#x2026; </p>
987-
<p><strong>EDITOR&apos;S NOTE</strong><br /> Section content yet to be written.</p>
987+
<p><strong>EDITOR&apos;S NOTE</strong><br/> Section content yet to be written.</p>
988988

989989
</section>
990990

@@ -1046,7 +1046,7 @@ <h4>Reflow
10461046
<a href="https://www.w3.org/TR/WCAG21/#reflow">Success Criterion 1.4.10</a>
10471047
</p>
10481048

1049-
<p><strong>EDITOR&apos;S NOTE</strong><br />Section content yet to be written.</p>
1049+
<p><strong>EDITOR&apos;S NOTE</strong><br/>Section content yet to be written.</p>
10501050
</section>
10511051

10521052
<section class="appendix notoc">
@@ -1056,7 +1056,7 @@ <h4>Timing Adjustable
10561056
<a href="https://www.w3.org/TR/WCAG21/#timing-adjustable">Success Criterion 2.2.1</a>
10571057
</p>
10581058

1059-
<p><strong>EDITOR&apos;S NOTE</strong><br />Section content yet to be written.</p>
1059+
<p><strong>EDITOR&apos;S NOTE</strong><br/>Section content yet to be written.</p>
10601060
</section>
10611061

10621062
<section class="appendix notoc">
@@ -1066,7 +1066,7 @@ <h4>Pointer Gestures
10661066
<a href="https://www.w3.org/TR/WCAG21/#pointer-gestures">Success Criterion 2.5.1</a>
10671067
</p>
10681068

1069-
<p><strong>EDITOR&apos;S NOTE</strong><br />Section content yet to be written.</p>
1069+
<p><strong>EDITOR&apos;S NOTE</strong><br/>Section content yet to be written.</p>
10701070
</section>
10711071

10721072
<section class="appendix notoc">
@@ -1076,7 +1076,7 @@ <h4>Pointer Cancellation
10761076
<a href="https://www.w3.org/TR/WCAG21/#pointer-cancellation">Success Criterion 2.5.2</a>
10771077
</p>
10781078

1079-
<p><strong>EDITOR&apos;S NOTE</strong><br />Section content yet to be written.</p>
1079+
<p><strong>EDITOR&apos;S NOTE</strong><br/>Section content yet to be written.</p>
10801080
</section>
10811081

10821082
<section class="appendix notoc">
@@ -1086,7 +1086,7 @@ <h4>Language of Page
10861086
<a href="https://www.w3.org/TR/WCAG21/#language-of-page">Success Criterion 3.1.1</a>
10871087
</p>
10881088

1089-
<p><strong>EDITOR&apos;S NOTE</strong><br />Section content yet to be written.</p>
1089+
<p><strong>EDITOR&apos;S NOTE</strong><br/>Section content yet to be written.</p>
10901090
</section>
10911091

10921092
<section class="appendix notoc">
@@ -1110,7 +1110,7 @@ <h4>Error Prevention
11101110
<a href="https://www.w3.org/TR/WCAG21/#error-prevention-legal-financial-data">Success Criterion 3.3.4</a>
11111111
</p>
11121112

1113-
<p><strong>EDITOR&apos;S NOTE</strong><br />Section content yet to be written.</p>
1113+
<p><strong>EDITOR&apos;S NOTE</strong><br/>Section content yet to be written.</p>
11141114
</section>
11151115

11161116
<section class="appendix notoc">
@@ -1120,7 +1120,7 @@ <h4>Parsing
11201120
<a href="https://www.w3.org/TR/WCAG21/#parsing">Success Criterion 4.1.1</a>
11211121
</p>
11221122

1123-
<p><strong>EDITOR&apos;S NOTE</strong><br /> Section content yet to be written.</p>
1123+
<p><strong>EDITOR&apos;S NOTE</strong><br/> Section content yet to be written.</p>
11241124
</section>
11251125

11261126
<section class="appendix notoc">
@@ -1130,7 +1130,7 @@ <h4>Name, Role, Value
11301130
<a href="https://www.w3.org/TR/WCAG21/#name-role-value">Success Criterion 4.1.2</a>
11311131
</p>
11321132

1133-
<p><strong>EDITOR&apos;S NOTE</strong><br />Section content yet to be written.</p>
1133+
<p><strong>EDITOR&apos;S NOTE</strong><br/>Section content yet to be written.</p>
11341134
</section>
11351135
</section>
11361136

@@ -1143,7 +1143,7 @@ <h4>Text Spacing
11431143
<a href="https://www.w3.org/TR/WCAG21/#text-spacing">Success Criterion 1.4.12</a>
11441144
</p>
11451145

1146-
<p><strong>EDITOR&apos;S NOTE</strong><br />Section content yet to be written.</p>
1146+
<p><strong>EDITOR&apos;S NOTE</strong><br/>Section content yet to be written.</p>
11471147
</section>
11481148
</section>
11491149

‎guidelines/index.html

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,15 +1,15 @@
11
<!DOCTYPE html>
22
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
33
<head>
4-
<meta charset="UTF-8" />
4+
<meta charset="UTF-8"/>
55

66
<title>Web Content Accessibility Guidelines (WCAG) 2.2</title>
77
<script src="https://www.w3.org/Tools/respec/respec-w3c" class="remove"></script>
88
<script src="../script/wcag.js" class="remove"></script>
99
<script src="respec-config.js" class="remove"></script>
1010
<script src="../biblio.js" class="remove"></script>
11-
<link rel="stylesheet" type="text/css" href="../css/sources.css" class="remove" />
12-
<link rel="stylesheet" type="text/css" href="guidelines.css" />
11+
<link rel="stylesheet" type="text/css" href="../css/sources.css" class="remove"/>
12+
<link rel="stylesheet" type="text/css" href="guidelines.css"/>
1313
</head>
1414
<body>
1515
<section id="abstract">

‎guidelines/relative-luminance.html

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -242,9 +242,9 @@ <h1>MathML version of the relative luminance definition</h1>
242242
</msub>
243243
<mo>,</mo>
244244
<mrow>
245-
<mspace width="1ex" />
245+
<mspace width="1ex"/>
246246
<mtext>and</mtext>
247-
<mspace width="1ex" />
247+
<mspace width="1ex"/>
248248
</mrow>
249249
<msub>
250250
<mi>B</mi>

‎guidelines/sc/22/focus-appearance.html

Lines changed: 6 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,9 @@
11
<section id="focus-appearance" class="sc new">
2-
32
<h4>Focus Appearance</h4>
4-
3+
54
<p class="conformance-level">AAA</p>
65
<p class="change">New</p>
7-
6+
87
<p>When the keyboard <a>focus indicator</a> is visible, an area of the focus indicator meets all the following:</p>
98
<ul>
109
<li>is at least as large as the area of a 2 <a>CSS pixel</a> thick <a>perimeter</a> of the unfocused component or sub-component, and</li>
@@ -13,14 +12,14 @@ <h4>Focus Appearance</h4>
1312

1413
<p>Exceptions:</p>
1514
<ul>
16-
<li>The focus indicator is determined by the <a>user agent</a> and cannot be adjusted by the author, or</li>
15+
<li>The focus indicator is determined by the <a>user agent</a> and cannot be adjusted by the author, or</li>
1716
<li>The focus indicator and the indicator's background color are not modified by the author.</li>
1817
</ul>
19-
20-
<p class="note">What is perceived as the user interface component or sub-component (to determine enclosure or size) depends on its visual <a>presentation</a>. The visual presentation includes the component's visible <a>content</a>, border, and component-specific background. It does not include shadow and glow effects outside the component's content, background, or border.</p>
18+
19+
<p class="note">What is perceived as the user interface component or sub-component (to determine the perimeter) depends on its visual <a>presentation</a>. The visual presentation includes the component's visible <a>content</a>, border, and component-specific background. It does not include shadow and glow effects outside the component's content, background, or border.</p>
2120

2221
<p class="note">Examples of sub-components that may receive a focus indicator are menu items in an opened drop-down menu, or focusable cells in a grid.</p>
2322

2423
<p class="note">Contrast calculations can be based on colors defined within the <a>technology</a> (such as HTML, CSS and SVG). Pixels modified by user agent resolution enhancements and anti-aliasing can be ignored.</p>
2524

26-
</section>
25+
</section>

‎guidelines/terms/21/single-pointer.html

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,6 @@
11
<dt><dfn id="dfn-single-pointer">single pointer</dfn></dt>
22
<dd>
3-
4-
<p>pointer input that operates with one point of contact with the screen, including single taps and clicks, double-taps and clicks, long presses, and path-based gestures</p>
5-
3+
<p>an input that only targets a single point on the page/screen at a time – such as a mouse, single finger on a touch screen, or stylus.</p>
4+
<p class="note">In contrast to single pointer inputs, multipoint interactions involve the use of two or more pointers at the same time – such as two finger interactions on a touchscreen, or the simultaneous use of a mouse and stylus.</p>
65
</dd>
76

‎requirements/22/index.html

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@
44

55
<head>
66
<title>Requirements for Web Content Accessibility Guidelines 2.2</title>
7-
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
7+
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
88
<script src="https://www.w3.org/Tools/respec/respec-w3c-common" class="remove"></script>
99
<!-- <script src='http://pandora.aptest.com/respec/js/require.js' data-main="http://pandora.aptest.com/respec/js/profile-w3c-common" async class='remove'></script> -->
1010
<!--<link href="../common/css/common.css" rel="stylesheet" type="text/css"/>-->

‎techniques/about.html

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -2,11 +2,11 @@
22
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
33

44
<head>
5-
<meta charset="UTF-8" />
6-
<meta name="viewport" content="width=device-width, initial-scale=1" />
5+
<meta charset="UTF-8"/>
6+
<meta name="viewport" content="width=device-width, initial-scale=1"/>
77
<title>About WCAG Techniques | WAI | W3C</title>
8-
<link rel="stylesheet" href="https://w3.org/WAI/assets/css/style.css" />
9-
<link rel="stylesheet" href="base.css" />
8+
<link rel="stylesheet" href="https://w3.org/WAI/assets/css/style.css"/>
9+
<link rel="stylesheet" href="base.css"/>
1010
</head>
1111

1212
<body dir="ltr">

‎techniques/aria/ARIA1.html

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
<!DOCTYPE html><html lang="en" xml:lang="en" xmlns="http://www.w3.org/1999/xhtml">
22
<head>
33
<title>Using the aria-describedby property to provide a descriptive label for user interface controls</title>
4-
<link rel="stylesheet" type="text/css" href="../../css/editors.css" class="remove"></link>
4+
<link rel="stylesheet" type="text/css" href="../../css/editors.css" class="remove"/>
55
</head>
66
<body>
77
<h1>Using the <code class="language-html">aria-describedby</code> property to provide a descriptive label for user interface controls</h1>

‎techniques/aria/ARIA10.html

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
<!DOCTYPE html><html lang="en" xml:lang="en" xmlns="http://www.w3.org/1999/xhtml"><head><title>Using aria-labelledby to provide a text alternative for non-text content</title><link rel="stylesheet" type="text/css" href="../../css/editors.css" class="remove"></link></head><body><h1>Using aria-labelledby to provide a text alternative for non-text content</h1><section class="meta"><p class="id">ID: ARIA10</p><p class="technology">Technology: aria</p><p class="type">Type: Technique</p></section><section id="applicability"><h2>When to Use</h2>
1+
<!DOCTYPE html><html lang="en" xml:lang="en" xmlns="http://www.w3.org/1999/xhtml"><head><title>Using aria-labelledby to provide a text alternative for non-text content</title><link rel="stylesheet" type="text/css" href="../../css/editors.css" class="remove"/></head><body><h1>Using aria-labelledby to provide a text alternative for non-text content</h1><section class="meta"><p class="id">ID: ARIA10</p><p class="technology">Technology: aria</p><p class="type">Type: Technique</p></section><section id="applicability"><h2>When to Use</h2>
22
<p>This technique applies to HTML with <a href="https://www.w3.org/TR/wai-aria/">Accessible Rich Internet Applications (WAI-ARIA)</a>.</p>
33
</section><section id="description"><h2>Description</h2>
44
<p>The purpose of this technique is to provide a short description for an element that can be read by assistive technologies by using the <code class="language-html">aria-labelledby</code> attribute. The <code class="language-html">aria-labelledby</code> attribute associates an element with text that is visible elsewhere on the page by using an <code class="language-html">id</code> reference value that matches the <code class="language-html">id</code> attribute of the labeling element. Assistive technology such as screen readers use the text of the element identified by the value of the <code class="language-html">aria-labelledby</code> attribute as the text alternative for the element with the attribute.</p>

‎techniques/aria/ARIA11.html

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
<html lang="en" xml:lang="en" xmlns="http://www.w3.org/1999/xhtml">
33
<head>
44
<title>Using ARIA landmarks to identify regions of a page</title>
5-
<link rel="stylesheet" type="text/css" href="../../css/editors.css" class="remove"></link>
5+
<link rel="stylesheet" type="text/css" href="../../css/editors.css" class="remove"/>
66
</head>
77
<body>
88
<h1>Using ARIA landmarks to identify regions of a page</h1>

‎techniques/aria/ARIA12.html

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
<!DOCTYPE html><html lang="en" xml:lang="en" xmlns="http://www.w3.org/1999/xhtml"><head><title>Using role=heading to identify headings</title><link rel="stylesheet" type="text/css" href="../../css/editors.css" class="remove"></link></head><body><h1>Using role=heading to identify headings</h1><section class="meta"><p class="id">ID: ARIA12</p><p class="technology">Technology: aria</p><p class="type">Type: Technique</p></section><section id="applicability"><h2>When to Use</h2>
1+
<!DOCTYPE html><html lang="en" xml:lang="en" xmlns="http://www.w3.org/1999/xhtml"><head><title>Using role=heading to identify headings</title><link rel="stylesheet" type="text/css" href="../../css/editors.css" class="remove"/></head><body><h1>Using role=heading to identify headings</h1><section class="meta"><p class="id">ID: ARIA12</p><p class="technology">Technology: aria</p><p class="type">Type: Technique</p></section><section id="applicability"><h2>When to Use</h2>
22
<p>Technologies that support <a href="https://www.w3.org/TR/wai-aria/">Accessible Rich Internet Applications (WAI-ARIA)</a>. </p>
33
</section><section id="description"><h2>Description</h2>
44
<p>The purpose of this technique is to provide a way for Assistive Technologies (AT) to identify

‎techniques/aria/ARIA13.html

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
<!DOCTYPE html><html lang="en" xml:lang="en" xmlns="http://www.w3.org/1999/xhtml"><head><title>Using aria-labelledby to name regions and landmarks</title><link rel="stylesheet" type="text/css" href="../../css/editors.css" class="remove"></link></head><body><h1>Using aria-labelledby to name regions and landmarks</h1><section class="meta"><p class="id">ID: ARIA13</p><p class="technology">Technology: aria</p><p class="type">Type: Technique</p></section><section id="applicability"><h2>When to Use</h2>
1+
<!DOCTYPE html><html lang="en" xml:lang="en" xmlns="http://www.w3.org/1999/xhtml"><head><title>Using aria-labelledby to name regions and landmarks</title><link rel="stylesheet" type="text/css" href="../../css/editors.css" class="remove"/></head><body><h1>Using aria-labelledby to name regions and landmarks</h1><section class="meta"><p class="id">ID: ARIA13</p><p class="technology">Technology: aria</p><p class="type">Type: Technique</p></section><section id="applicability"><h2>When to Use</h2>
22
<p>Technologies that support <a href="https://www.w3.org/TR/wai-aria/">Accessible Rich Internet Applications (WAI-ARIA)</a>. </p>
33
</section><section id="description"><h2>Description</h2>
44
<p>The purpose of this technique is to provide names for regions of a page that can be read by assistive technology. The <code class="language-html">aria-labelledby</code> attribute provides a way to associate a section of the page marked up as a region or landmarks with text that is on the page that labels it.

‎techniques/aria/ARIA14.html

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
<!DOCTYPE html><html lang="en" xml:lang="en" xmlns="http://www.w3.org/1999/xhtml"><head><title>Using aria-label to provide an invisible label where a visible label cannot be used</title><link rel="stylesheet" type="text/css" href="../../css/editors.css" class="remove"></link></head><body><h1>Using aria-label to provide an invisible label where a visible label cannot be used</h1><section class="meta"><p class="id">ID: ARIA14</p><p class="technology">Technology: aria</p><p class="type">Type: Technique</p></section><section id="applicability"><h2>When to Use</h2>
1+
<!DOCTYPE html><html lang="en" xml:lang="en" xmlns="http://www.w3.org/1999/xhtml"><head><title>Using aria-label to provide an invisible label where a visible label cannot be used</title><link rel="stylesheet" type="text/css" href="../../css/editors.css" class="remove"/></head><body><h1>Using aria-label to provide an invisible label where a visible label cannot be used</h1><section class="meta"><p class="id">ID: ARIA14</p><p class="technology">Technology: aria</p><p class="type">Type: Technique</p></section><section id="applicability"><h2>When to Use</h2>
22
<p>Technologies that support <a href="https://www.w3.org/TR/wai-aria/">Accessible Rich Internet Applications (WAI-ARIA)</a>. </p>
33
</section><section id="description"><h2>Description</h2>
44
<p>For sighted users, the context and visual appearance of an element can provide sufficient cues to determine the purpose. An example is the 'X' often used in the top right corner of pop-up <code class="language-html">div</code>s (light boxes) to indicate the control for closing the div.

‎techniques/aria/ARIA15.html

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
<!DOCTYPE html><html lang="en" xml:lang="en" xmlns="http://www.w3.org/1999/xhtml"><head><title>Using aria-describedby to provide descriptions of images</title><link rel="stylesheet" type="text/css" href="../../css/editors.css" class="remove"></link></head><body><h1>Using aria-describedby to provide descriptions of images</h1><section class="meta"><p class="id">ID: ARIA15</p><p class="technology">Technology: aria</p><p class="type">Type: Technique</p></section><section id="applicability"><h2>When to Use</h2>
1+
<!DOCTYPE html><html lang="en" xml:lang="en" xmlns="http://www.w3.org/1999/xhtml"><head><title>Using aria-describedby to provide descriptions of images</title><link rel="stylesheet" type="text/css" href="../../css/editors.css" class="remove"/></head><body><h1>Using aria-describedby to provide descriptions of images</h1><section class="meta"><p class="id">ID: ARIA15</p><p class="technology">Technology: aria</p><p class="type">Type: Technique</p></section><section id="applicability"><h2>When to Use</h2>
22
<p>Technologies that support <a href="https://www.w3.org/TR/wai-aria/">Accessible Rich Internet Applications (WAI-ARIA)</a>. </p>
33
</section><section id="description"><h2>Description</h2>
44
<p>The objective of this technique is to provide descriptions of images when a short text alternative does not adequately convey the function or information provided in the object.

0 commit comments

Comments
 (0)