Add IDs to sections to avoid rewriting after translation

acknowledgements/funders.html

@@ -1,4 +1,4 @@
-<section>
+<section id="enabling-funders">
 	<h2>Enabling funders</h2>
 	<p>This publication has been funded in part with U.S. Federal funds from the Health and Human Services, National Institute on Disability, Independent Living, and Rehabilitation Research (NIDILRR), initially under contract number ED-OSE-10-C-0067, then under contract number HHSP23301500054C, and now under HHS75P00120P00168. The content of this publication does not necessarily reflect the views or policies of the U.S. Department of Health and Human Services or the U.S. Department of Education, nor does mention of trade names, commercial products, or organizations imply endorsement by the U.S. Government.</p>
-</section>
+</section>

guidelines/index.html

@@ -27,7 +27,7 @@
         </section>
         <section class="informative introductory" id="intro">
 			<h2>Introduction</h2>
-			<section>
+			<section id="background-on-wcag-2">
 				<h3>Background on WCAG 2</h3>
 				<p>Web Content Accessibility Guidelines (WCAG) 2.2 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.2 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.2 builds on WCAG 2.0 [[WCAG20]] and WCAG 2.1 [[WCAG21]], 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/standards-guidelines/wcag/">Web Content Accessibility Guidelines (WCAG) Overview</a>.</p>
@@ -42,7 +42,7 @@ <h3>Background on WCAG 2</h3>
                 </ul>
                 <p>Where this document refers to <q>WCAG 2</q> it is intended to mean any and all versions of WCAG that start with 2.</p>
 			</section>
-			<section>
+			<section id="wcag-2-layers-of-guidance">
 				<h3>WCAG 2 Layers of Guidance</h3>
 				<p>The individuals and organizations that use WCAG vary widely and include Web designers and developers, policy makers, purchasing agents, teachers, and students. In order to meet the varying needs of this audience, several layers of guidance are provided including overall <em>principles</em>, general <em>guidelines</em>, testable <em>success criteria</em> and a rich collection of <em>sufficient techniques</em>, <em>advisory techniques</em>, and <em>documented common failures</em> with examples, resource links and code.</p>
 				<ul>
@@ -62,7 +62,7 @@ <h3>WCAG 2 Layers of Guidance</h3>
 				<p>All of these layers of guidance (principles, guidelines, success criteria, and sufficient and advisory techniques) work together to provide guidance on how to make content more accessible. Authors are encouraged to view and apply all layers that they are able to, including the advisory techniques, in order to best address the needs of the widest possible range of users.</p>
 				<p>Note that even content that conforms at the highest level (AAA) will not be accessible to individuals with all types, degrees, or combinations of disability, particularly in the cognitive, language, and learning areas. Authors are encouraged to consider the full range of techniques, including the advisory techniques, <a href="https://www.w3.org/TR/coga-usable/">Making Content Usable for People with Cognitive and Learning Disabilities</a>, as well as to seek relevant advice about current best practice to ensure that Web content is accessible, as far as possible, to this community. <a href="https://www.w3.org/WAI/WCAG22/Understanding/understanding-metadata">Metadata</a> may assist users in finding content most suitable for their needs. </p>
 			</section>
-			<section>
+			<section id="wcag-2-2-supporting-documents">
 				<h3>WCAG 2.2 Supporting Documents</h3>
 				<p>The WCAG 2.2 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.2 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">
@@ -82,16 +82,16 @@ <h3>WCAG 2.2 Supporting Documents</h3>
 				</ol>
 				<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.2 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="https://www.w3.org/WAI/Resources/Overview">WAI Resources</a>.</p>
 			</section>
-        	<section>
+        	<section id="requirements-for-wcag-2-2">
         		<h3>Requirements for WCAG 2.2</h3>
                 <p>WCAG 2.2 meets a set of <a href="https://w3c.github.io/wcag/requirements/22/">requirements for WCAG 2.2</a> which, in turn, inherit requirements from previous WCAG 2 versions. Requirements structure the overall framework of guidelines and ensure backwards compatibility. The Working Group also used a less formal set of acceptance criteria for success criteria, to help ensure success criteria are similar in style and quality to those in WCAG 2.0. These requirements constrained what could be included in WCAG 2.2. This constraint was important to preserve its nature as a dot-release of WCAG 2.</p>
         	</section>
-    		<section>
+    		<section id="comparison-with-wcag-2-1">
                 <h3>Comparison with WCAG 2.1</h3>
                 <p>WCAG 2.2 was initiated with the goal to continue the work of WCAG 2.1: Improving accessibility guidance for three major groups: users with cognitive or learning disabilities, users with low vision, and users with disabilities on mobile devices. Many ways to meet these needs were proposed and evaluated, and a set of these were refined by the Working Group. Structural requirements inherited from WCAG 2.0, clarity and impact of proposals, and timeline led to the final set of success criteria included in this version. The Working Group considers that WCAG 2.2 incrementally advances web content accessibility guidance for all these areas, but underscores that not all user needs are met by these guidelines.</p>
 
 				<p>WCAG 2.2 builds on and is backwards compatible with WCAG 2.1, meaning web pages that conform to WCAG 2.2 are at least as accessible as pages that conform to WCAG 2.1. Requirements have been added that build on 2.1 and 2.0. WCAG 2.2 has removed one success criterion, <a href="#parsing">4.1.1 Parsing</a>. Authors that are required by policy to conform with WCAG 2.0 or 2.1 will be able to update content to WCAG 2.2, but may need to continue to test and report 4.1.1. Authors following more than one version of the guidelines should be aware of the following additions.</p>
-				<section>
+				<section id="new-features-in-wcag-2-2">
 					<h4>New Features in WCAG 2.2</h4>
 					<p>WCAG 2.2 extends WCAG 2.1 by adding new success criteria, definitions to support them, and guidelines to organize the additions. This additive approach helps to make it clear that sites which conform to WCAG 2.2 also conform to WCAG 2.1. The Accessibility Guidelines Working Group recommends that sites adopt WCAG 2.2 as their new conformance target, even if formal obligations mention previous versions, to provide improved accessibility and to anticipate future policy changes.</p>
           <p>The following success criteria are new in WCAG 2.2:</p>
@@ -110,16 +110,16 @@ <h4>New Features in WCAG 2.2</h4>
           <p>WCAG 2.2 also introduces new sections detailing aspects of the specification which may impact <a href="#privacy-summary">privacy</a> and <a href="#security-summary">security</a>.</p>
 
 				</section>
-				<section>
+				<section id="numbering-in-wcag-2-2">
 					<h4>Numbering in WCAG 2.2</h4>
 					<p>In order to avoid confusion for implementers for whom backwards compatibility to WCAG 2 versions is important, new success criteria in WCAG 2.2 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, 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/WCAG22/quickref/">WCAG 2.2 Quick Reference</a> will provide a way to view success criteria grouped by conformance level, along with many other filter and sort options.</p>
 				</section>
-				<section>
+				<section id="conformance-to-wcag-2-2">
 					<h4>Conformance to WCAG 2.2</h4>
 					<p>WCAG 2.2 uses the same conformance model as WCAG 2.0. It is intended that sites that conform to WCAG 2.2 also conform to WCAG 2.0 and WCAG 2.1, which means they meet the requirements of any policies that reference WCAG 2.0 or WCAG 2.1, while also better meeting the needs of users on the current Web. </p>
 				</section>
 			</section>
-        	<section>
+        	<section id="later-versions-of-accessibility-guidelines">
         		<h3>Later Versions of Accessibility Guidelines</h3>
         		<p>In parallel with WCAG 2.2, the Accessibility Guidelines Working Group is developing another major version of accessibility guidelines. The result of this work is expected to be a more substantial restructuring of web accessibility guidance than would be realistic for dot-releases of WCAG 2. The work follows a research-focused, user-centered design methodology to produce the most effective and flexible outcome, including the roles of content authoring, user agent support, and authoring tool support. This is a multi-year effort, so WCAG 2.2 is needed as an interim measure to provide updated web accessibility guidance to reflect changes on the web since the publication of WCAG 2.0. The Working Group might also develop additional interim versions, continuing with WCAG 2.2, on a similar short timeline to provide additional support while the major version is completed. </p>
         	</section>
@@ -128,14 +128,14 @@ <h3>Later Versions of Accessibility Guidelines</h3>
             <h2> Perceivable </h2>
             <p>Information and user interface components must be presentable to users in ways they can perceive.</p>
 
-            <section class="guideline">
+            <section class="guideline" id="text-alternatives">
                 <h3>Text Alternatives</h3>
                 <p>Provide text alternatives for any non-text content so that it can be changed into other forms people need, such as large print, braille, speech, symbols or simpler language.</p>
 
                 <section data-include="sc/20/non-text-content.html" data-include-replace="true"></section>
             </section>
 
-            <section class="guideline">
+            <section class="guideline" id="time-based-media">
                 <h3>Time-based Media</h3>
                 <p>Provide alternatives for time-based media.</p>
 
@@ -158,7 +158,7 @@ <h3>Time-based Media</h3>
                 <section data-include="sc/20/audio-only-live.html" data-include-replace="true"></section>
             </section>
 
-            <section class="guideline">
+            <section class="guideline" id="adaptable">
                 <h3>Adaptable</h3>
                 <p>Create content that can be presented in different ways (for example simpler layout) without losing information or structure.</p>
 
@@ -176,7 +176,7 @@ <h3>Adaptable</h3>
 
           </section>
 
-            <section class="guideline">
+            <section class="guideline" id="distinguishable">
                 <h3>Distinguishable</h3>
                 <p>Make it easier for users to see and hear content including separating foreground from background.</p>
 
@@ -213,7 +213,7 @@ <h3>Distinguishable</h3>
             <h2>Operable </h2>
             <p>User interface components and navigation must be operable.</p>
 
-            <section class="guideline">
+            <section class="guideline" id="keyboard-accessible">
                 <h3>Keyboard Accessible</h3>
                 <p>Make all functionality available from a keyboard.</p>
 
@@ -227,7 +227,7 @@ <h3>Keyboard Accessible</h3>
 
             </section>
 
-            <section class="guideline">
+            <section class="guideline" id="enough-time">
                 <h3>Enough Time</h3>
                 <p>Provide users enough time to read and use content.</p>
 
@@ -245,7 +245,7 @@ <h3>Enough Time</h3>
 
             </section>
 
-            <section class="guideline">
+            <section class="guideline" id="seizures-and-physical-reactions">
                 <h3>Seizures and Physical Reactions</h3>
                 <p>Do not design content in a way that is known to cause seizures or physical reactions.</p>
 
@@ -257,7 +257,7 @@ <h3>Seizures and Physical Reactions</h3>
 
             </section>
 
-            <section class="guideline">
+            <section class="guideline" id="navigable">
                 <h3>Navigable</h3>
                 <p>Provide ways to help users navigate, find content, and determine where they are.</p>
 
@@ -289,7 +289,7 @@ <h3>Navigable</h3>
 
             </section>
 
-            <section class="guideline">
+            <section class="guideline" id="input-modalities">
                 <h3>Input Modalities</h3>
                 <p>Make it easier for users to operate functionality through various inputs beyond keyboard.</p>
 
@@ -316,7 +316,7 @@ <h3>Input Modalities</h3>
             <h2> Understandable </h2>
             <p>Information and the operation of the user interface must be understandable.</p>
 
-            <section class="guideline">
+            <section class="guideline" id="readable">
                 <h3>Readable</h3>
                 <p>Make text content readable and understandable.</p>
 
@@ -334,7 +334,7 @@ <h3>Readable</h3>
 
             </section>
 
-            <section class="guideline">
+            <section class="guideline" id="predictable">
                 <h3>Predictable</h3>
                 <p>Make Web pages appear and operate in predictable ways.</p>
 
@@ -352,7 +352,7 @@ <h3>Predictable</h3>
 
             </section>
 
-            <section class="guideline">
+            <section class="guideline" id="input-assistance">
                 <h3>Input Assistance</h3>
                 <p>Help users avoid and correct mistakes.</p>
 
@@ -381,7 +381,7 @@ <h3>Input Assistance</h3>
             <h2> Robust </h2>
             <p>Content must be robust enough that it can be interpreted by a wide variety of user agents, including assistive technologies.</p>
 
-            <section class="guideline">
+            <section class="guideline" id="compatible">
                 <h3>Compatible</h3>
                 <p>Maximize compatibility with current and future user agents, including assistive technologies.</p>
 
@@ -394,12 +394,12 @@ <h3>Compatible</h3>
            </section>
 
         </section>
-        <section>
+        <section id="conformance">
             <h1>Conformance</h1>
 
             <p>This section lists requirements for <a>conformance</a> to WCAG 2.2. 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/WCAG22/Understanding/conformance">Understanding Conformance</a> includes further explanation of the accessibility-supported concept.</p>
 
-        	<section>
+        	<section id="interpreting-normative-requirements">
         		<h2>Interpreting Normative Requirements</h2>
 
         		<p>The main content of WCAG 2.2 is <a>normative</a> and defines requirements that impact conformance claims. Introductory material, appendices, sections marked as "non-normative", diagrams, examples, and notes are <a>informative</a> (non-normative). Non-normative material provides advisory information to help interpret the guidelines but does not create requirements that impact a conformance claim.</p>