w3c · alastc · Jun 15, 2023 · May 15, 2023 · May 15, 2023 · May 15, 2023
diff --git a/understanding/21/animation-from-interactions.html b/understanding/21/animation-from-interactions.html
@@ -7,6 +7,17 @@
 	</head>
 	<body>
 		<h1>Understanding Animation from Interactions</h1>
+
+		<section id="brief">
+			<h2>In brief</h2>
+			<dl>
+				<dt>Objective</dt><dd>Users are not harmed or distracted by motion</dd>
+				<dt>Author task</dt><dd>Support user preferences for reduced motion, and eliminate unnecessary motion effects</dd>
+				<dt>Key beneficiaries</dt><dd>Users with vestibular dysfunction</dd>
+			</dl>
+
+		</section>		
+
 		<section id="intent">
 			<h2>Intent</h2>
 

diff --git a/understanding/21/character-key-shortcuts.html b/understanding/21/character-key-shortcuts.html
@@ -7,6 +7,17 @@
 	</head>
 	<body>
 		<h1>Understanding Character Key Shortcuts</h1>
+
+		<section id="brief">
+			<h2>In brief</h2>
+			<dl>
+				<dt>Objective</dt><dd>Reduce accidental activation of keyboard shortcuts</dd>
+				<dt>Author task</dt><dd>Ensure custom shortcuts can be turned off or modified</dd>
+				<dt>Key beneficiaries</dt><dd>Users primarily operating via speech or keyboard</dd>
+			</dl>
+
+		</section>
+
 		<section id="intent">
 			<h2>Intent</h2>
 <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.

diff --git a/understanding/21/concurrent-input-mechanisms.html b/understanding/21/concurrent-input-mechanisms.html
@@ -7,6 +7,17 @@
 	</head>
 	<body>
 		<h1>Understanding Concurrent Input Mechanisms</h1>
+
+	<section id="brief">
+		<h2>In brief</h2>
+		<dl>
+			<dt>Objective</dt><dd>Users can choose different ways of inputting content</dd>
+			<dt>Author task</dt><dd>Do not prevent users from varying their mode of input</dd>
+			<dt>Key beneficiaries</dt><dd>Users requiring specific means of operation or using assistive technology</dd>
+		</dl>
+
+	</section>
+
 		<section id="intent">
 			<h2>Intent</h2>
         <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>

diff --git a/understanding/21/content-on-hover-or-focus.html b/understanding/21/content-on-hover-or-focus.html
@@ -7,6 +7,17 @@
 	</head>
 	<body>
 		<h1>Understanding Content on Hover or Focus</h1>
+
+		<section id="brief">
+			<h2>In brief</h2>
+			<dl>
+				<dt>Objective</dt><dd>More users can perceive and dismiss non-persistent content</dd>
+				<dt>Author task</dt><dd>If content can appear or disappear without a user intentionally activating it, ensure it can persist until dismissed by the user</dd>
+				<dt>Key beneficiaries</dt><dd>Users with cognitive or visual disabilities</dd>
+			</dl>
+
+		</section>
+
 		<section id="intent">
 			<h2>Intent</h2>
 			<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>

diff --git a/understanding/21/identify-input-purpose.html b/understanding/21/identify-input-purpose.html
@@ -7,6 +7,17 @@
 </head>
 <body>
 <h1>Understanding Identify Input Purpose</h1>
+
+<section id="brief">
+  <h2>In brief</h2>
+  <dl>
+    <dt>Objective</dt><dd>It is easier to fill out forms</dd>
+    <dt>Author task</dt><dd>Indicate the purpose of common inputs, where available</dd>
+    <dt>Key beneficiaries</dt><dd>Users with some cognitive disabilities</dd>
+  </dl>
+
+</section>
+
 <section id="intent">
 			<h2>Intent of this Success Criterion</h2>
 

diff --git a/understanding/21/identify-purpose.html b/understanding/21/identify-purpose.html
@@ -7,6 +7,17 @@
 	</head>
 	<body>
 		<h1>Understanding Identify Purpose</h1>
+
+		<section id="brief">
+			<h2>In brief</h2>
+			<dl>
+				<dt>Objective</dt><dd>It is easier to operate and navigate content</dd>
+				<dt>Author task</dt><dd>Indicate the meaning of all controls and other key information, where available</dd>
+				<dt>Key beneficiaries</dt><dd>Users with some cognitive disabilities</dd>
+			</dl>
+
+		</section>
+
 		<section id="intent">
 			<h2>Intent</h2>
 			<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>

diff --git a/understanding/21/label-in-name.html b/understanding/21/label-in-name.html
@@ -7,6 +7,17 @@
 	</head>
 	<body>
 		<h1>Understanding Label in Name</h1>
+
+	<section id="brief">
+		<h2>In brief</h2>
+		<dl>
+			<dt>Objective</dt><dd>The visual label for controls is a trigger for speech activation</dd>
+			<dt>Author task</dt><dd>Where pratical, make the control’s text label and name match</dd>
+			<dt>Key beneficiaries</dt><dd>Users operating content via speech</dd>
+		</dl>
+
+	</section>
+
 		<section id="intent">
 			<h2>Intent</h2>
 			<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>

diff --git a/understanding/21/motion-actuation.html b/understanding/21/motion-actuation.html
@@ -10,6 +10,17 @@ <h1><strong>Motion Actuation</strong>
 			<br />
 			Understanding SC 2.6.1
 		</h1>
+
+	<section id="brief">
+		<h2>In brief</h2>
+		<dl>
+			<dt>Objective</dt><dd>Content is not dependent on a user's ability to move a device</dd>
+			<dt>Author task</dt><dd>Don't rely solely on device motion to control page content</dd>
+			<dt>Key beneficiaries</dt><dd>Users with some physical disabilities</dd>
+		</dl>
+
+	</section>
+
 		<section id="intent">
 			<h2>Intent of this Success Criterion</h2>
 			<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>

diff --git a/understanding/21/non-text-contrast.html b/understanding/21/non-text-contrast.html
@@ -7,6 +7,16 @@
 	</head>
 	<body>
 		<h1>Understanding Non-text Contrast</h1>
+
+		<section id="brief">
+			<h2>In brief</h2>
+			<dl>
+				<dt>Objective</dt><dd>Important visual information meets the same minimum contrast required for larger text</dd>
+				<dt>Author task</dt><dd>Ensure meaningful visual cues achieve 3:1 against the background</dd>
+				<dt>Key beneficiaries</dt><dd>Users with low vision</dd>
+			</dl>
+
+		</section>
 		<section id="intent">
 			<h2>Intent</h2>
 

diff --git a/understanding/21/orientation.html b/understanding/21/orientation.html
@@ -13,6 +13,17 @@ <h1>
 			<abbr title="Success Criterion">SC</abbr>
 			2.6.2
 		</h1>
+
+		<section id="brief">
+			<h2>In brief</h2>
+			<dl>
+				<dt>Objective</dt><dd>Devices can be used in any orientation</dd>
+				<dt>Author task</dt><dd>Don't lock content to either portrait or landscape presentation</dd>
+				<dt>Key beneficiaries</dt><dd>Users with some physical disabilities</dd>
+			</dl>
+
+		</section>
+
 		<section id="intent">
 			<h2>Intent of this Success Criterion</h2>
 			<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

diff --git a/understanding/21/pointer-cancellation.html b/understanding/21/pointer-cancellation.html
@@ -7,6 +7,16 @@
 	</head>
 	<body>
 		<h1>Understanding Pointer Cancellation</h1>
+
+		<section id="brief">
+			<h2>In brief</h2>
+			<dl>
+				<dt>Objective</dt><dd>Reduce accidental activation of controls</dd>
+				<dt>Author task</dt><dd>Make pointer cancellation predictable and consistent</dd>
+				<dt>Key beneficiaries</dt><dd>Users with some cognitive, physical, or visual disabilities</dd>
+			</dl>
+
+		</section>
 		<section id="intent">
 			<h2>Intent</h2>
 			<p>The intent of this success criterion is to make it easier for users to prevent accidental or erroneous pointer input. People with various disabilities can inadvertently initiate touch or mouse events with unwanted results. Each of the following subsections roughly aligns with the bullets of this Success Criterion, and outlines a means of allowing users to cancel pointer operations.</p>

diff --git a/understanding/21/pointer-gestures.html b/understanding/21/pointer-gestures.html
@@ -7,6 +7,16 @@
 	</head>
 	<body>
     <h1><strong>Pointer Gestures</strong><br />Understanding SC 2.5.1</h1>
+
+	<section id="brief">
+		<h2>In brief</h2>
+		<dl>
+			<dt>Objective</dt><dd>Let users operate touchscreens with one finger</dd>
+			<dt>Author task</dt><dd>Provide single-point operation for all functions</dd>
+			<dt>Key beneficiaries</dt><dd>Users with some physical disabilities</dd>
+		</dl>
+
+	</section>
 
 		<section id="intent">
 			<h2>Intent of this Success Criterion</h2>

diff --git a/understanding/21/reflow.html b/understanding/21/reflow.html
@@ -8,6 +8,16 @@
 </head>
 <body>
     <h1>Understanding Reflow</h1>
+
+    <section id="brief">
+			<h2>In brief</h2>
+			<dl>
+				<dt>Objective</dt><dd>Content can be enlarged without requiring horizontal scrolling</dd>
+				<dt>Author task</dt><dd>Make text reflow within the width of the viewport</dd>
+				<dt>Key beneficiaries</dt><dd>Users with low vision</dd>
+			</dl>
+
+		</section>
     <section id="intent">
         <h2>Intent of this Success Criterion</h2>
         <p>The intent of this Success Criterion is to support people with low vision who need to enlarge text and read it in a single column.  When the browser zoom is used to scale content to 400%, it reflows - i.e., it is presented in one column so that scrolling in more than one direction is not necessary.</p>

diff --git a/understanding/21/status-messages.html b/understanding/21/status-messages.html
@@ -8,6 +8,17 @@
 	<body>
 		<h1>Status Messages<br />
 		Understanding SC 3.2.6</h1>
+
+	<section id="brief">
+		<h2>In brief</h2>
+		<dl>
+			<dt>Objective</dt><dd>Make users aware of important changes in content</dd>
+			<dt>Author task</dt><dd>Let assistive technology notify users about status changes that don't take focus</dd>
+			<dt>Key beneficiaries</dt><dd>Blind users and those with low vision</dd>
+		</dl>
+
+	</section>
+
 		<section id="intent">
 			<h2>Intent of this Success Criterion</h2>
 			<p>The intent of this Success Criterion is to make users aware of important changes in content that are not given focus, and to do so in a way that doesn't unnecessarily interrupt their work.</p>

diff --git a/understanding/21/target-size-enhanced.html b/understanding/21/target-size-enhanced.html
@@ -7,6 +7,17 @@
 	</head>
 	<body>
 		<h1>Understanding SC 2.5.5 Target Size (Enhanced)</h1>
+
+	<section id="brief">
+		<h2>In brief</h2>
+		<dl>
+			<dt>Objective</dt><dd>Controls can be operated more easily, especially on touch screens</dd>
+			<dt>Author task</dt><dd>Make custom targets at least 44 by 44 pixels</dd>
+			<dt>Key beneficiaries</dt><dd>Users with some physical disabilities</dd>
+		</dl>
+
+	</section>
+
 	<section id="intent">
 		<h2>Intent</h2>
 		<p>The intent of this success criterion is to help users who may have trouble activating a small target because of hand tremors, limited dexterity or other reasons. If the target is too small, it may be difficult to aim at the target. Mice and similar pointing devices can be hard to use for these users, and a larger target will help them greatly in having positive outcomes on the web page.</p>

diff --git a/understanding/21/text-spacing.html b/understanding/21/text-spacing.html
@@ -7,6 +7,16 @@
    </head>
    <body>
       <h1>Understanding Text Spacing</h1>
+
+      <section id="brief">
+			<h2>In brief</h2>
+			<dl>
+				<dt>Objective</dt><dd>Users can adjust text spacing to make it easier to read</dd>
+				<dt>Author task</dt><dd>Ensure content adapts to user text preferences</dd>
+				<dt>Key beneficiaries</dt><dd>Users with low vision or some cognitive disabilities</dd>
+			</dl>
+
+		</section>
       <section id="intent">
          <h2>Intent</h2>
          <p>The intent of this Success Criterion (SC) is to ensure that when people override author specified text spacing to improve their reading experience, content is still readable and operable. Each of the requirements stipulated in the SC's four bullets helps ensure text styling can be adapted by the user to suit their needs.</p>

diff --git a/understanding/21/timeouts.html b/understanding/21/timeouts.html
@@ -7,6 +7,17 @@
 	</head>
 	<body>
 		<h1>Understanding Timeouts</h1>
+
+		<section id="brief">
+			<h2>In brief</h2>
+			<dl>
+				<dt>Objective</dt><dd>Users do not lose data due to unknown timeouts</dd>
+				<dt>Author task</dt><dd>Tell users how long their session can be inactive before they may lose information</dd>
+				<dt>Key beneficiaries</dt><dd>Users with some cognitive disabilities</dd>
+			</dl>
+
+		</section>
+
 		<section id="intent">
 			<h2>Intent</h2>
 			<p>The intent of this Success Criterion is to ensure that when a timeout is used, users know what duration of inactivity will cause the page to time out and result in lost data. The use of timed events can present significant barriers for users with cognitive disabilities, as these users may require more time to read content or to perform functions, such as completing an online form.</p>