Merge pull request #426 from w3c/fixes-from-translation1

alastc · web-flow · commit 9279b4a696b5 · 2018-07-13T12:38:07.000+01:00
Editorial updates 2.0 - 2.1
diff --git a/guidelines/index.html b/guidelines/index.html
@@ -59,7 +59,7 @@ <h3>WCAG 2 Layers of Guidance</h3>
 			</section>
 			<section>
 				<h3>WCAG 2.1 Supporting Documents</h3>
-				<p>The WCAG 2.0 document is designed to meet the needs of those who need a stable, referenceable technical standard. Other documents, called supporting documents, are based on the WCAG 2.1 document and address other important purposes, including the ability to be updated to describe how WCAG would be applied with new technologies. Supporting documents include: </p>
+				<p>The WCAG 2.1 document is designed to meet the needs of those who need a stable, referenceable technical standard. Other documents, called supporting documents, are based on the WCAG 2.1 document and address other important purposes, including the ability to be updated to describe how WCAG would be applied with new technologies. Supporting documents include: </p>
 				<ol class="enumar">
 					<li>
 						<p><strong><a href="https://www.w3.org/WAI/WCAG21/quickref/">How to Meet WCAG 2.1</a></strong> - A customizable quick reference to WCAG 2.1 that includes all of the guidelines, success criteria, and techniques for authors to use as they are developing and evaluating Web content. This includes content from WCAG 2.0 and WCAG 2.1 and can be filtered in many ways to help authors focus on relevant content.</p>
@@ -113,7 +113,7 @@ <h4>New Features in WCAG 2.1</h4>
 				</section>
 				<section>
 					<h4>Numbering in WCAG 2.1</h4>
-					<p>In order to avoid confusion for implementers for whom backwards compatibility to WCAG 2.0 is important, new success criteria in WCAG 2.1 have been appended to the end of the set of success criteria within their guideline. This avoids the need to change the section number of success criteria from WCAG 2.0, which would be caused by inserting new success critera between existing success ccriteria in the guideline, but it means success criteria in each guideline are no longer grouped by conformance level. The order of success criteria within each guideline does not imply information about conformance level; only the conformance level indicator (A / AA / AAA) on the success criterion itself indicates this. The <a href="https://www.w3.org/WAI/WCAG21/quickref/">WCAG 2.1 Quick Reference</a> provides ways to view success criteria grouped by conformance level, along with many other filter and sort options.</p>
+					<p>In order to avoid confusion for implementers for whom backwards compatibility to WCAG 2.0 is important, new success criteria in WCAG 2.1 have been appended to the end of the set of success criteria within their guideline. This avoids the need to change the section number of success criteria from WCAG 2.0, which would be caused by inserting new success criteria between existing success criteria in the guideline, but it means success criteria in each guideline are no longer grouped by conformance level. The order of success criteria within each guideline does not imply information about conformance level; only the conformance level indicator (A / AA / AAA) on the success criterion itself indicates this. The <a href="https://www.w3.org/WAI/WCAG21/quickref/">WCAG 2.1 Quick Reference</a> provides ways to view success criteria grouped by conformance level, along with many other filter and sort options.</p>
 				</section>
 				<section>
 					<h4>Conformance to WCAG 2.1</h4>
@@ -379,7 +379,7 @@ <h3>Compatible</h3>
         </section>
         <section>
             <h1>Conformance</h1>
-            <p>This section lists requirements for <a>conformance</a> to WCAG 2.1. It also gives information about how to make conformance claims, which are optional. Finally, it describes what it means to be <a>accessibility supported</a>, since only accessibility-supported ways of using technologies can be <a>relied upon</a> for conformance. <a href="https://www.w3.org/TR/UNDERSTANDING-WCAG20/conformance">Understanding Conformance</a> includes further explanation of the accessibility-supported concept.</p>
+            <p>This section lists requirements for <a>conformance</a> to WCAG 2.1. It also gives information about how to make conformance claims, which are optional. Finally, it describes what it means to be <a>accessibility supported</a>, since only accessibility-supported ways of using technologies can be <a>relied upon</a> for conformance. <a href="https://www.w3.org/WAI/WCAG21/Understanding/conformance">Understanding Conformance</a> includes further explanation of the accessibility-supported concept.</p>
         	
         	<section>
         		<h2>Interpreting Normative Requirements</h2>
@@ -421,7 +421,7 @@ <h3>Complete processes</h3>
 
                 <section id="cc4">
                     <h3>Only Accessibility-Supported Ways of Using Technologies</h3>
-                    <p>Only <a>accessibility-supported</a> ways of using <a>technologies</a> are <a>relied upon</a> to satisfy the success criteria. Any information or functionality that is provided in a way that is not accessibility supported is also available in a way that is accessibility supported. (See <a href="https://www.w3.org/TR/UNDERSTANDING-WCAG20/conformance">Understanding accessibility support</a>.)</p>
+                    <p>Only <a>accessibility-supported</a> ways of using <a>technologies</a> are <a>relied upon</a> to satisfy the success criteria. Any information or functionality that is provided in a way that is not accessibility supported is also available in a way that is accessibility supported. (See <a href="https://www.w3.org/WAI/WCAG21/Understanding/conformance">Understanding accessibility support</a>.)</p>
                 </section>
 
                 <section id="cc5">
@@ -440,7 +440,7 @@ <h3>Non-Interference</h3>
                         <li><strong>2.2.2 - Pause, Stop, Hide</strong>.</li>
                     </ul>
                     <p class="note">If a page cannot conform (for example, a conformance test page or an example page), it cannot be included in the scope of conformance or in a conformance claim.</p>
-                    <p>For more information, including examples, see <a href="https://www.w3.org/TR/UNDERSTANDING-WCAG20/conformance">Understanding Conformance Requirements</a>.</p>
+                    <p>For more information, including examples, see <a href="https://www.w3.org/WAI/WCAG21/Understanding/conformance">Understanding Conformance Requirements</a>.</p>
                 </section>
             </section>
 
@@ -479,8 +479,8 @@ <h3>Optional Components of a Conformance Claim </h3>
                         <li>A machine-readable metadata version of the list of specific technologies that are <a>relied upon</a>.</li>
                         <li>A machine-readable metadata version of the conformance claim.</li>
                     </ul>
-                    <p class="note">Refer to <a href="https://www.w3.org/TR/UNDERSTANDING-WCAG20/conformance">Understanding Conformance Claims</a> for more information and example conformance claims.</p>
-                    <p class="note">Refer to <a href="https://www.w3.org/TR/UNDERSTANDING-WCAG20/appendixC">Understanding Metadata</a> for more information about the use of metadata in conformance claims.</p>
+                    <p class="note">Refer to <a href="https://www.w3.org/WAI/WCAG21/Understanding/conformance">Understanding Conformance Claims</a> for more information and example conformance claims.</p>
+                    <p class="note">Refer to <a href="https://www.w3.org/WAI/WCAG21/Understanding/understanding-metadata">Understanding Metadata</a> for more information about the use of metadata in conformance claims.</p>
                 </section>
             </section>
 

-Original file line number
+Diff line change
 			section>
 			<section>
 				<h3>WCAG 2.1 Supporting Documentsh3>
 -				<p>The WCAG 2.0 document is designed to meet the needs of those who need a stable, referenceable technical standard. Other documents, called supporting documents, are based on the WCAG 2.1 document and address other important purposes, including the ability to be updated to describe how WCAG would be applied with new technologies. Supporting documents include: p>
 +				<p>The WCAG 2.1 document is designed to meet the needs of those who need a stable, referenceable technical standard. Other documents, called supporting documents, are based on the WCAG 2.1 document and address other important purposes, including the ability to be updated to describe how WCAG would be applied with new technologies. Supporting documents include: p>
 				<ol class="enumar">
 					<li>
 						<p><strong><a href="https://www.w3.org/WAI/WCAG21/quickref/">How to Meet WCAG 2.1a>strong> - A customizable quick reference to WCAG 2.1 that includes all of the guidelines, success criteria, and techniques for authors to use as they are developing and evaluating Web content. This includes content from WCAG 2.0 and WCAG 2.1 and can be filtered in many ways to help authors focus on relevant content.p>
 				section>
 				<section>
 					<h4>Numbering in WCAG 2.1h4>
 -					<p>In order to avoid confusion for implementers for whom backwards compatibility to WCAG 2.0 is important, new success criteria in WCAG 2.1 have been appended to the end of the set of success criteria within their guideline. This avoids the need to change the section number of success criteria from WCAG 2.0, which would be caused by inserting new success critera between existing success ccriteria in the guideline, but it means success criteria in each guideline are no longer grouped by conformance level. The order of success criteria within each guideline does not imply information about conformance level; only the conformance level indicator (A / AA / AAA) on the success criterion itself indicates this. The <a href="https://www.w3.org/WAI/WCAG21/quickref/">WCAG 2.1 Quick Referencea> provides ways to view success criteria grouped by conformance level, along with many other filter and sort options.p>
 +					<p>In order to avoid confusion for implementers for whom backwards compatibility to WCAG 2.0 is important, new success criteria in WCAG 2.1 have been appended to the end of the set of success criteria within their guideline. This avoids the need to change the section number of success criteria from WCAG 2.0, which would be caused by inserting new success criteria between existing success criteria in the guideline, but it means success criteria in each guideline are no longer grouped by conformance level. The order of success criteria within each guideline does not imply information about conformance level; only the conformance level indicator (A / AA / AAA) on the success criterion itself indicates this. The <a href="https://www.w3.org/WAI/WCAG21/quickref/">WCAG 2.1 Quick Referencea> provides ways to view success criteria grouped by conformance level, along with many other filter and sort options.p>
 				section>
 				<section>
 					<h4>Conformance to WCAG 2.1h4>
         section>
         <section>
             <h1>Conformanceh1>
 -            <p>This section lists requirements for <a>conformancea> to WCAG 2.1. It also gives information about how to make conformance claims, which are optional. Finally, it describes what it means to be <a>accessibility supporteda>, since only accessibility-supported ways of using technologies can be <a>relied upona> for conformance. <a href="https://www.w3.org/TR/UNDERSTANDING-WCAG20/conformance">Understanding Conformancea> includes further explanation of the accessibility-supported concept.p>
 +            <p>This section lists requirements for <a>conformancea> to WCAG 2.1. It also gives information about how to make conformance claims, which are optional. Finally, it describes what it means to be <a>accessibility supporteda>, since only accessibility-supported ways of using technologies can be <a>relied upona> for conformance. <a href="https://www.w3.org/WAI/WCAG21/Understanding/conformance">Understanding Conformancea> includes further explanation of the accessibility-supported concept.p>
         	<section>
         		<h2>Interpreting Normative Requirementsh2>
                 <section id="cc4">
                     <h3>Only Accessibility-Supported Ways of Using Technologiesh3>
 -                    <p>Only <a>accessibility-supporteda> ways of using <a>technologiesa> are <a>relied upona> to satisfy the success criteria. Any information or functionality that is provided in a way that is not accessibility supported is also available in a way that is accessibility supported. (See <a href="https://www.w3.org/TR/UNDERSTANDING-WCAG20/conformance">Understanding accessibility supporta>.)p>
 +                    <p>Only <a>accessibility-supporteda> ways of using <a>technologiesa> are <a>relied upona> to satisfy the success criteria. Any information or functionality that is provided in a way that is not accessibility supported is also available in a way that is accessibility supported. (See <a href="https://www.w3.org/WAI/WCAG21/Understanding/conformance">Understanding accessibility supporta>.)p>
                 section>
                 <section id="cc5">
                         <li><strong>2.2.2 - Pause, Stop, Hidestrong>.li>
                     ul>
                     <p class="note">If a page cannot conform (for example, a conformance test page or an example page), it cannot be included in the scope of conformance or in a conformance claim.p>
 -                    <p>For more information, including examples, see <a href="https://www.w3.org/TR/UNDERSTANDING-WCAG20/conformance">Understanding Conformance Requirementsa>.p>
 +                    <p>For more information, including examples, see <a href="https://www.w3.org/WAI/WCAG21/Understanding/conformance">Understanding Conformance Requirementsa>.p>
                 section>
             section>
                         <li>A machine-readable metadata version of the list of specific technologies that are <a>relied upona>.li>
                         <li>A machine-readable metadata version of the conformance claim.li>
                     ul>
 -                    <p class="note">Refer to <a href="https://www.w3.org/TR/UNDERSTANDING-WCAG20/conformance">Understanding Conformance Claimsa> for more information and example conformance claims.p>
 -                    <p class="note">Refer to <a href="https://www.w3.org/TR/UNDERSTANDING-WCAG20/appendixC">Understanding Metadataa> for more information about the use of metadata in conformance claims.p>
 +                    <p class="note">Refer to <a href="https://www.w3.org/WAI/WCAG21/Understanding/conformance">Understanding Conformance Claimsa> for more information and example conformance claims.p>
 +                    <p class="note">Refer to <a href="https://www.w3.org/WAI/WCAG21/Understanding/understanding-metadata">Understanding Metadataa> for more information about the use of metadata in conformance claims.p>
                 section>
             section>