Merge remote-tracking branch 'refs/remotes/origin/master' into unders…

…tanding-cleanup
w3c · May 31, 2018 · d18d6da · d18d6da
2 parents 81524de + 735271c
commit d18d6da
Show file tree

Hide file tree

Showing 11 changed files with 21 additions and 14 deletions.
diff --git a/acknowledgements.html b/acknowledgements.html
@@ -1,19 +1,24 @@
 <section class="appendix" id="acknowledgments">
     <h1>Acknowledgments</h1>
-    <p>Additional information about participation in the Web Content Accessibility Guidelines Working Group (WCAG WG) can be found on the <a href="https://www.w3.org/WAI/GL/">Working Group home page</a>.</p>
+    <p>Additional information about participation in the Accessibility Guidelines Working Group (AG WG) can be found on the <a href="https://www.w3.org/WAI/GL/">Working Group home page</a>.</p>
 
     <section id="ack_participants-active">
-        <h2>Participants of the WCAG WG active in the development of this document:</h2>
+        <h2>Participants of the AG WG active in the development of this document:</h2>
         <ul>
           	<li>Jake Abma (Invited Expert)</li>
             <li>Shadi Abou-Zahra (W3C)</li>
+        	<li>Chuck Adams (Oracle Corporation)</li>
+        	<li>Amani Ali (Nomensa)</li>
             <li>Jim Allan (Invited Expert)</li>
             <li>Paul Adam (Deque Systems, Inc.)</li>
-            <li>Jon Avila (SSB Bart Group)</li>
+        	<li>Christopher Auclair (VitalSource | Ingram Content Group)</li>
+            <li>Jon Avila (Level Access)</li>
             <li>Tom Babinszki (IBM Corporation)</li>
             <li>Bruce Bailey (U.S. Access Board)</li>
             <li>Renaldo Bernard (University of Southampton)</li>
-            <li>Judy Brewer (W3c)</li>
+        	<li>Chris Blouch (Level Access)</li>
+        	<li>Denis Boudreau (Deque Systems, Inc.)</li>
+            <li>Judy Brewer (W3C)</li>
             <li>Shari Butler (Pearson plc)</li>
             <li>Thaddeus Cambron (Invited Expert)</li>
             <li>Alastair Campbell (Nomensa)</li>
@@ -35,7 +40,7 @@ <h2>Participants of the WCAG WG active in the development of this document:</h2>
             <li>Detlev Fischer (Invited Expert)</li>
             <li>John Foliot (Deque Systems, Inc.)</li>
             <li>Matt Garrish (DAISY Consortium)</li>
-            <li>Alistair Garrison (SSB Bart Group)</li>
+            <li>Alistair Garrison (Level Access)</li>
             <li>Michael Gower (IBM Corporation)</li>
             <li>Jon Gunderson</li>
             <li>Markku Hakkinen (Educational Testing Service)</li>
@@ -63,7 +68,7 @@ <h2>Participants of the WCAG WG active in the development of this document:</h2>
             <li>Adam Lund (Thomson Reuters)</li>
             <li>David MacDonald (Invited Expert)</li>
             <li>Erich Manser (IBM Corporation)</li>
-            <li>Scott McCormack (SSB Bart Group)</li>
+            <li>Scott McCormack (Level Access)</li>
             <li>Chris McMeeking (Deque Systems, Inc.)</li>
             <li>Jan McSorley (Pearson plc)</li>
             <li>Neil Milliken (Unify Software and Solutions)</li>
@@ -82,6 +87,7 @@ <h2>Participants of the WCAG WG active in the development of this document:</h2>
             <li>Jan Richards (Invited Expert)</li>
             <li>John Rochford (Invited Expert)</li>
             <li>Marla Runyan (Invited Expert)</li>
+        	<li>Stefan Schnabel (SAP SE)</li>
             <li>Ayelet Seeman (Invited Expert)</li>
             <li>Lisa Seeman-Kestenbaum (Invited Expert)</li>
             <li>Glenda Sims (Deque Systems, Inc.)</li>
@@ -99,6 +105,7 @@ <h2>Participants of the WCAG WG active in the development of this document:</h2>
             <li>Can Wang (Zhejiang University)</li>
             <li>Léonie Watson (The Paciello Group, LLC)</li>
             <li>Jason White (Educational Testing Service)</li>
+        	<li>Mark Wilcock (Unify Software and Solutions)</li>
         </ul>
     </section>
 

diff --git a/guidelines/index.html b/guidelines/index.html
@@ -14,7 +14,7 @@
     <body>
         <section id="abstract">
             <p>Web Content Accessibility Guidelines (WCAG) 2.1 covers a wide range of recommendations for making Web content more accessible. Following these guidelines will make content more accessible to a wider range of people with disabilities, including accommodations for blindness and low vision, deafness and hearing loss, limited movement, speech disabilities, photosensitivity, and combinations of these, and some accommodation for learning disabilities and cognitive limitations; but will not address every user need for people with these disabilities. These guidelines address accessibility of web content on desktops, laptops, tablets, and mobile devices. Following these guidelines will also often make Web content more usable to users in general.</p>
-            <p>WCAG 2.1 success criteria are written as testable statements that are not technology-specific. Guidance about satisfying the success criteria in specific technologies, as well as general information about interpreting the success criteria, is provided in separate documents. See <a href="https://www.w3.org/WAI/intro/wcag.php">Web Content Accessibility Guidelines (WCAG) Overview</a> for an introduction and links to WCAG technical and educational material.</p>
+        	<p>WCAG 2.1 success criteria are written as testable statements that are not technology-specific. Guidance about satisfying the success criteria in specific technologies, as well as general information about interpreting the success criteria, is provided in separate documents. See <a href="http://www.w3.org/WAI/standards-guidelines/wcag/">Web Content Accessibility Guidelines (WCAG) Overview</a> for an introduction and links to WCAG technical and educational material.</p>
             <p>WCAG 2.1 extends <a href="https://www.w3.org/TR/WCAG20/">Web Content Accessibility Guidelines 2.0</a> [[!WCAG20]], which was published as a W3C Recommendation December 2008. Content that conforms to WCAG 2.1 also conforms to WCAG 2.0. The WG intends that for policies requiring conformance to WCAG 2.0, WCAG 2.1 can provide an alternate means of conformance. The publication of WCAG 2.1 does not deprecate or supersede WCAG 2.0. While WCAG 2.0 remains a W3C Recommendation, the W3C advises the use of WCAG 2.1 to maximize future applicability of accessibility efforts. The W3C also encourages use of the most current version of WCAG when developing or updating Web accessibility policies.</p>
         </section>
         <section id="sotd">
@@ -25,15 +25,15 @@ <h2>Introduction</h2>
 			<section>
 				<h3>Background on WCAG 2</h3>
 				<p>Web Content Accessibility Guidelines (WCAG) 2.1 defines how to make Web content more accessible to people with disabilities. Accessibility involves a wide range of disabilities, including visual, auditory, physical, speech, cognitive, language, learning, and neurological disabilities. Although these guidelines cover a wide range of issues, they are not able to address the needs of people with all types, degrees, and combinations of disability. These guidelines also make Web content more usable by older individuals with changing abilities due to aging and often improve usability for users in general.</p>
-                <p>WCAG 2.1 is developed through the <a href="https://www.w3.org/WAI/intro/w3c-process">W3C process</a> in cooperation with individuals and organizations around the world, with a goal of providing a shared standard for Web content accessibility that meets the needs of individuals, organizations, and governments internationally. WCAG 2.1 builds on WCAG 2.0 [[!WCAG20]], which in turn built on WCAG 1.0 [[WAI-WEBCONTENT]] and is designed to apply broadly to different Web technologies now and in the future, and to be testable with a combination of automated testing and human evaluation. For an introduction to WCAG, see the <a href="https://www.w3.org/WAI/intro/wcag">Web Content Accessibility Guidelines (WCAG) Overview</a>.</p>
+				<p>WCAG 2.1 is developed through the <a href="https://www.w3.org/WAI/standards-guidelines/w3c-process/">W3C process</a> in cooperation with individuals and organizations around the world, with a goal of providing a shared standard for Web content accessibility that meets the needs of individuals, organizations, and governments internationally. WCAG 2.1 builds on WCAG 2.0 [[!WCAG20]], which in turn built on WCAG 1.0 [[WAI-WEBCONTENT]] and is designed to apply broadly to different Web technologies now and in the future, and to be testable with a combination of automated testing and human evaluation. For an introduction to WCAG, see the <a href="http://www.w3.org/WAI/standards-guidelines/wcag/">Web Content Accessibility Guidelines (WCAG) Overview</a>.</p>
 
-                <p>Significant challenges were encountered in defining additional criteria to address cognitive, language, and learning disabilities, including a short timeline for development as well as challenges in reaching consensus on testability, implementability, and international considerations of proposals. Work will carry on in this area in future versions of WCAG. We encourage authors to refer to our supplemental guidance on <a href="https://www.w3.org/WAI/intro/wcag#supplement">improving inclusion for people with disabilities, including learning and cognitive disabilities, people with low-vision, and more</a>.</p>
+				<p>Significant challenges were encountered in defining additional criteria to address cognitive, language, and learning disabilities, including a short timeline for development as well as challenges in reaching consensus on testability, implementability, and international considerations of proposals. Work will carry on in this area in future versions of WCAG. We encourage authors to refer to our supplemental guidance on <a href="http://www.w3.org/WAI/standards-guidelines/wcag/#supplement">improving inclusion for people with disabilities, including learning and cognitive disabilities, people with low-vision, and more</a>.</p>
 
 				<p>Web accessibility depends not only on accessible content but also on accessible Web browsers and other user agents. Authoring tools also have an important role in Web accessibility. For an overview of how these components of Web development and interaction work together, see:</p>
 				<ul>
 					<li><strong><a href="https://www.w3.org/WAI/intro/components">Essential Components of Web Accessibility</a></strong></li>
-					<li><strong><a href="https://www.w3.org/WAI/intro/uaag">User Agent Accessibility Guidelines (UAAG) Overview</a></strong></li>
-					<li><strong><a href="https://www.w3.org/WAI/intro/atag">Authoring Tool Accessibility Guidelines (ATAG) Overview</a></strong></li>
+					<li><strong><a href="https://www.w3.org/WAI/standards-guidelines/uaag/">User Agent Accessibility Guidelines (UAAG) Overview</a></strong></li>
+					<li><strong><a href="https://www.w3.org/WAI/standards-guidelines/atag/">Authoring Tool Accessibility Guidelines (ATAG) Overview</a></strong></li>
 				</ul>
 			</section>
 			<section>
@@ -70,10 +70,10 @@ <h3>WCAG 2.1 Supporting Documents</h3>
 						<p><strong><a href="https://www.w3.org/WAI/WCAG21/Techniques/">Techniques for WCAG 2.1</a></strong> - A collection of techniques and common failures, each in a separate document that includes a description, examples, code and tests.</p>
 					</li>
 					<li>
-						<p><strong><a href="https://www.w3.org/WAI/intro/wcag20">The WCAG Documents</a></strong> - A diagram and description of how the technical documents are related and linked.</p>
+						<p><strong><a href="https://www.w3.org/WAI/standards-guidelines/wcag/docs/">The WCAG Documents</a></strong> - A diagram and description of how the technical documents are related and linked.</p>
 					</li>
 				</ol>
-				<p>See <a href="http://www.w3.org/WAI/intro/wcag.php">Web Content Accessibility Guidelines (WCAG) Overview</a> for a description of the WCAG 2.0 supporting material, including education resources related to WCAG 2. Additional resources covering topics such as the business case for Web accessibility, planning implementation to improve the accessibility of Web sites, and accessibility policies are listed in <a href="http://www.w3.org/WAI/Resources/Overview">WAI Resources</a>.</p>
+				<p>See <a href="https://www.w3.org/WAI/standards-guidelines/wcag/">Web Content Accessibility Guidelines (WCAG) Overview</a> for a description of the WCAG 2.0 supporting material, including education resources related to WCAG 2. Additional resources covering topics such as the business case for Web accessibility, planning implementation to improve the accessibility of Web sites, and accessibility policies are listed in <a href="http://www.w3.org/WAI/Resources/Overview">WAI Resources</a>.</p>
 			</section>
         	<section>
         		<h3>Requirements for WCAG 2.1</h3>

diff --git a/understanding/21/concurrent-input-mechanisms.html b/understanding/21/concurrent-input-mechanisms.html
@@ -29,7 +29,7 @@ <h2>Examples</h2>
         <li>On a touch-enabled laptop with coarse precision, people who have difficulty activating a small target because of hand tremors, limited dexterity or other reasons are still able to interact with content using their keyboard and trackpad.</li>
         <li>A user starts interacting with a page using a desktop keyboard, and then attaches a secondary touch-enabled monitor. Content can be operated using this newly added input mechanism and does not assume that the keyboard, the first input mechanism it detected, is the only one in use.</li>
         <li>A speech input user navigates content using voice commands which translate to simulate mouse (and keyboard) commands. When talking with a colleague, however, the user turns speech recognition off and uses the mouse instead.</li>
-
+        <li>A user opens a menu with a mouse, and then navigates between the menu items with arrow keys.</li>
       </ul>
 		</section>
 		<section id="resources">

diff --git a/understanding/21/img/contrast-currency-down.png b/understanding/21/img/contrast-currency-down.png
diff --git a/understanding/21/img/contrast-gradient.png b/understanding/21/img/contrast-gradient.png
diff --git a/understanding/21/img/contrast-magnet.png b/understanding/21/img/contrast-magnet.png
diff --git a/understanding/21/img/contrast-phone.png b/understanding/21/img/contrast-phone.png
diff --git a/understanding/21/img/graphics-contrast_pie-chart_fail.png b/understanding/21/img/graphics-contrast_pie-chart_fail.png
diff --git a/understanding/21/img/infographic-fail.png b/understanding/21/img/infographic-fail.png
diff --git a/understanding/21/img/infographic-pass.png b/understanding/21/img/infographic-pass.png
diff --git a/understanding/21/img/stroke-comparisons.png b/understanding/21/img/stroke-comparisons.png