Skip to content

Commit 9123102

Browse files
alastcalastc
authored
Merge pull request #3191 from w3c/WCAGQuickInfo
WCAG 2.1 brief descriptions
2 parents d9b0252 + 18f909f commit 9123102

17 files changed

Lines changed: 165 additions & 0 deletions

‎understanding/21/animation-from-interactions.html‎

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -7,6 +7,16 @@
77
</head>
88
<body>
99
<h1>Understanding Animation from Interactions</h1>
10+
11+
<section id="brief">
12+
<h2>In brief</h2>
13+
<dl>
14+
<dt>Objective</dt><dd>Users are not harmed or distracted by motion</dd>
15+
<dt>Author task</dt><dd>Support user preferences for motion, and eliminate unnecessary motion effects</dd>
16+
</dl>
17+
18+
</section>
19+
1020
<section id="intent">
1121
<h2>Intent</h2>
1222

‎understanding/21/character-key-shortcuts.html‎

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -7,6 +7,16 @@
77
</head>
88
<body>
99
<h1>Understanding Character Key Shortcuts</h1>
10+
11+
<section id="brief">
12+
<h2>In brief</h2>
13+
<dl>
14+
<dt>Objective</dt><dd>Reduce accidental activation of keyboard shortcuts</dd>
15+
<dt>Author task</dt><dd>Ensure character-only shortcut keys can be turned off or modified</dd>
16+
</dl>
17+
18+
</section>
19+
1020
<section id="intent">
1121
<h2>Intent</h2>
1222
<p>The intent of this Success Crition is to reduce accidental activation of keyboard shortcuts. Character key shortcuts work well for many keyboard users, but are inappropriate and frustrating for speech input users &#8212; whose means of input is strings of letters &#8212; and for keyboard users who are prone to accidentally hit keys.

‎understanding/21/concurrent-input-mechanisms.html‎

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -7,6 +7,16 @@
77
</head>
88
<body>
99
<h1>Understanding Concurrent Input Mechanisms</h1>
10+
11+
<section id="brief">
12+
<h2>In brief</h2>
13+
<dl>
14+
<dt>Objective</dt><dd>Users can choose different ways of inputting content</dd>
15+
<dt>Author task</dt><dd>Do not prevent users from switching their mode of input</dd>
16+
</dl>
17+
18+
</section>
19+
1020
<section id="intent">
1121
<h2>Intent</h2>
1222
<p>The intent of this Success Criterion is to ensure that people can use and switch between different modes of input when interacting with web content. Users may employ a variety of input mechanisms when interacting with web content. These may be a combination of mechanisms such as a keyboard or keyboard-like interfaces and pointer devices like a mouse, stylus or touchscreen.</p>

‎understanding/21/content-on-hover-or-focus.html‎

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -7,6 +7,16 @@
77
</head>
88
<body>
99
<h1>Understanding Content on Hover or Focus</h1>
10+
11+
<section id="brief">
12+
<h2>In brief</h2>
13+
<dl>
14+
<dt>Objective</dt><dd>More users can perceive and dismiss non-persistent content</dd>
15+
<dt>Author task</dt><dd>If hover or focus causes content changes, ensure interaction is predictable</dd>
16+
</dl>
17+
18+
</section>
19+
1020
<section id="intent">
1121
<h2>Intent</h2>
1222
<p>Additional content that appears and disappears in coordination with keyboard focus or pointer hover often leads to accessibility issues. Reasons for such issues include:</p>

‎understanding/21/identify-input-purpose.html‎

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -7,6 +7,16 @@
77
</head>
88
<body>
99
<h1>Understanding Identify Input Purpose</h1>
10+
11+
<section id="brief">
12+
<h2>In brief</h2>
13+
<dl>
14+
<dt>Objective</dt><dd>It is easier to fill out forms</dd>
15+
<dt>Author task</dt><dd>Indicate the purpose of common inputs, where technology allows</dd>
16+
</dl>
17+
18+
</section>
19+
1020
<section id="intent">
1121
<h2>Intent of this Success Criterion</h2>
1222

‎understanding/21/identify-purpose.html‎

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -7,6 +7,16 @@
77
</head>
88
<body>
99
<h1>Understanding Identify Purpose</h1>
10+
11+
<section id="brief">
12+
<h2>In brief</h2>
13+
<dl>
14+
<dt>Objective</dt><dd>It is easier to operate and navigate content</dd>
15+
<dt>Author task</dt><dd>Indicate the meaning of all controls and other key information, where available</dd>
16+
</dl>
17+
18+
</section>
19+
1020
<section id="intent">
1121
<h2>Intent</h2>
1222
<p>The intent of this Success Criterion is to ensure that the purpose of many elements on a page can be programmatically determined, so that user agents can extract and present that purpose to users using different modalities.</p>

‎understanding/21/label-in-name.html‎

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -7,6 +7,16 @@
77
</head>
88
<body>
99
<h1>Understanding Label in Name</h1>
10+
11+
<section id="brief">
12+
<h2>In brief</h2>
13+
<dl>
14+
<dt>Objective</dt><dd>The visual label for controls is a trigger for speech activation</dd>
15+
<dt>Author task</dt><dd>Where pratical, make the control’s text label and name match</dd>
16+
</dl>
17+
18+
</section>
19+
1020
<section id="intent">
1121
<h2>Intent</h2>
1222
<p>The intent of this Success Criterion is to ensure that the words which visually label a component are also the words associated with the component programmatically. This helps ensure that people with disabilities can rely on visible labels as a means to interact with the components.</p>

‎understanding/21/motion-actuation.html‎

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -10,6 +10,16 @@ <h1><strong>Motion Actuation</strong>
1010
<br />
1111
Understanding SC 2.6.1
1212
</h1>
13+
14+
<section id="brief">
15+
<h2>In brief</h2>
16+
<dl>
17+
<dt>Objective</dt><dd>Content is not dependent on a user's ability to move a device</dd>
18+
<dt>Author task</dt><dd>Don't rely solely on device motion to control page content</dd>
19+
</dl>
20+
21+
</section>
22+
1323
<section id="intent">
1424
<h2>Intent of this Success Criterion</h2>
1525
<p>The intent of this success criterion is to ensure that functions triggered by moving a device (for example, shaking or tilting) or by gesturing towards the device (so that sensors like a camera can pick up and interpret the gesturing), can also be operated by more conventional user interface components.</p>

‎understanding/21/non-text-contrast.html‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -7,6 +7,15 @@
77
</head>
88
<body>
99
<h1>Understanding Non-text Contrast</h1>
10+
11+
<section id="brief">
12+
<h2>In brief</h2>
13+
<dl>
14+
<dt>Objective</dt><dd>Important visual information meets the same minimum contrast required for larger text</dd>
15+
<dt>Author task</dt><dd>Ensure meaningful visual cues achieve 3:1 against the background</dd>
16+
</dl>
17+
18+
</section>
1019
<section id="intent">
1120
<h2>Intent</h2>
1221

‎understanding/21/orientation.html‎

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -13,6 +13,16 @@ <h1>
1313
<abbr title="Success Criterion">SC</abbr>
1414
2.6.2
1515
</h1>
16+
17+
<section id="brief">
18+
<h2>In brief</h2>
19+
<dl>
20+
<dt>Objective</dt><dd>Devices can be used in any orientation</dd>
21+
<dt>Author task</dt><dd>Don't lock content to either portrait or landscape presentation</dd>
22+
</dl>
23+
24+
</section>
25+
1626
<section id="intent">
1727
<h2>Intent of this Success Criterion</h2>
1828
<p>The intent of this Success Criterion is to ensure that content displays in the orientation (portrait or landscape) preferred by the user. Some websites and applications automatically set and restrict the screen to a particular display orientation and expect

0 commit comments

Comments
 (0)