Backport October 2025 errata to 2.1

guidelines/guidelines.css

@@ -29,11 +29,17 @@ dd.new, dd.proposed, dd.changed {
 }
 .doclinks {
 	float: right;
-	border: thin solid black;
-	font-size: x-small;
+	border: thin solid #aaa;
+    background: #ecf2f7;
+	font-size: small;
 	display: block;
 	width: 25%;
 	hyphens: none;
+    padding: 1em;
+    display: flex;
+    flex-direction: column;
+    gap: 1em;
+    margin: -0.5em 0 1em 2em;
 }
 .sc dt {
 	display: list-item;

guidelines/index.html

@@ -118,7 +118,7 @@ <h4>Numbering in WCAG 2.1</h4>
 				</section>
         <section id="conformance-to-wcag-2-1">
           <h4>Conformance to WCAG 2.1</h4>
-					<p>WCAG 2.1 uses the same conformance model as WCAG 2.0 with a couple additions, which is described in the <a href="#conformance">Conformance</a> section. It is intended that sites that conform to WCAG 2.1 also conform to WCAG 2.0, which means they meet the requirements of any policies that reference WCAG 2.0, while also better meeting the needs of users on the current Web. </p>
+					<p>WCAG 2.1 uses the same conformance model as WCAG 2.0 with a couple additions, which is described in the <a href="#conformance">Conformance</a> section. It is intended that sites that conform to WCAG 2.1 also conform to WCAG 2.0, which means they meet the requirements of any policies that reference WCAG 2.0, while also better meeting the needs of users on the current web. </p>
 				</section>
 			</section>
           <section id="later-versions-of-accessibility-guidelines">

guidelines/input-purposes.html

@@ -1,6 +1,6 @@
 <section id="input-purposes">
 	<h2>Input Purposes for User Interface Components</h2>
-	<p>This section contains a listing of common <a>user interface component</a> input purposes. The terms below are not keywords that must be used, but instead represent purposes that must be captured in the taxonomy adopted by a webpage. Where applicable, authors mark up controls with the chosen taxonomy to indicate the semantic purpose. This provides the potential for user agents and assistive technologies to apply personalized presentations that can enable more people to understand and use the content.</p>
+	<p>This section contains a listing of common <a>user interface component</a> input purposes. The terms below are not keywords that must be used, but instead represent purposes that can be captured in the taxonomy adopted by a webpage. Where applicable, authors mark up controls with the chosen taxonomy to indicate the semantic purpose. This provides the potential for user agents and assistive technologies to apply personalized presentations that can enable more people to understand and use the content.</p>
 
   <p class="note">The list of input type purposes is based on the control purposes defined in the <a href="https://www.w3.org/TR/html52/sec-forms.html#sec-autofill">HTML 5.2 Autofill field section</a>, but it is important to understand that a different technology may have some or all of the same concepts defined in its specification and only the concepts that are mapped to the meanings below are required.</p>
 
@@ -58,8 +58,8 @@ <h2>Input Purposes for User Interface Components</h2>
 		<li><strong>tel-local-prefix</strong> - First part of the component of the telephone number that follows the area code, when that component is split into two components</li>
 		<li><strong>tel-local-suffix</strong> - Second part of the component of the telephone number that follows the area code, when that component is split into two components</li>
 		<li><strong>tel-extension</strong> - Telephone number internal extension code</li>
-		<li><strong>email</strong> - E-mail address</li>
+		<li><strong>email</strong> - Email address</li>
 		<li><strong>impp</strong> - URL representing an instant messaging protocol endpoint (for example, "<strong>aim:goim?screenname=example</strong>" or "<strong>xmpp:[email protected]</strong>")</li>
 	</ul>
-	
+
 </section>

guidelines/sc/21/content-on-hover-or-focus.html

@@ -4,7 +4,7 @@ <h4>Content on Hover or Focus</h4>
 
    <p class="conformance-level">AA</p>
 
-    	<p>Where receiving and then removing pointer hover or keyboard focus triggers additional content to become visible and then hidden, the following are true:</p>
+    	<p>Where receiving and then removing pointer hover or keyboard focus triggers additional content to become visible and then hidden, all of the following are true:</p>
 
   <dl>
 

guidelines/terms/20/abbreviation.html

@@ -5,38 +5,40 @@
       of the language
    </p>
 
-   <p class="note">This includes initialisms and acronyms where:</p>
-
-   <ol>
-
-      <li>
-
-         <p><strong>initialisms</strong> are shortened forms of a name or phrase made from the initial letters of words or
-            syllables contained in that name or phrase
-         </p>
-
-         <p class="note">Not defined in all languages.</p>
-
-         <aside class="example"><p>SNCF is a French initialism that contains the initial letters of the <span lang="fr">Société Nationale des Chemins de Fer</span>, the French national railroad.
-         </p></aside>
-
-         <aside class="example"><p>ESP is an initialism for extrasensory perception.</p></aside>
-
-      </li>
+   <div class="note">This includes initialisms and acronyms where:
 
-      <li>
-
-         <p><strong>acronyms</strong> are abbreviated forms made from the initial letters or parts of other words (in a
-            name or phrase) which may be pronounced as a word
-         </p>
-
-         <aside class="example"><p>NOAA is an acronym made from the initial letters of the National Oceanic and Atmospheric
-            Administration in the United States.
-         </p></aside>
-
-      </li>
+      <ol>
+
+         <li>
+
+            <p><strong>initialisms</strong> are shortened forms of a name or phrase made from the initial letters of words or
+               syllables contained in that name or phrase
+            </p>
+
+            <p><em>Note:</em> Not defined in all languages.</p>
+
+            <aside class="example"><p>SNCF is a French initialism that contains the initial letters of the <span lang="fr">Société Nationale des Chemins de Fer</span>, the French national railroad.
+            </p></aside>
+
+            <aside class="example"><p>ESP is an initialism for extrasensory perception.</p></aside>
+
+         </li>
+
+         <li>
+
+            <p><strong>acronyms</strong> are abbreviated forms made from the initial letters or parts of other words (in a
+               name or phrase) which may be pronounced as a word
+            </p>
+
+            <aside class="example"><p>NOAA is an acronym made from the initial letters of the National Oceanic and Atmospheric
+               Administration in the United States.
+            </p></aside>
+
+         </li>
+
+      </ol>
 
-   </ol>
+   </div>
 
    <p class="note">Some companies have adopted what used to be an initialism as their company name. In
       these cases, the new name of the company is the letters (for example, Ecma) and the

guidelines/terms/20/accessibility-supported.html

@@ -102,7 +102,7 @@
       would be to consult compilations of uses that are documented to be accessibility supported.
       (See <a href="https://www.w3.org/WAI/WCAG21/Understanding/conformance#documented-lists">Understanding Accessibility-Supported Web Technology Uses</a>.) Authors, companies, technology vendors, or others may document accessibility-supported
       ways of using web content technologies. However, all ways of using technologies in
-      the documentation would need to meet the definition of accessibility-supported Web
+      the documentation would need to meet the definition of accessibility-supported web
       content technologies above.
    </p>
 

guidelines/terms/20/role.html

@@ -1,7 +1,7 @@
 <dt><dfn id="dfn-role">role</dfn></dt>
 <dd>
 
-   <p>text or number by which software can identify the function of a component within Web
+   <p>text or number by which software can identify the function of a component within web
       content
    </p>
 

guidelines/terms/20/technology.html

@@ -10,7 +10,7 @@
 
    <p class="note">Web content technologies may include markup languages, data formats, or programming
       languages that authors may use alone or in combination to create end-user experiences
-      that range from static web pages to synchronized media presentations to dynamic Web
+      that range from static web pages to synchronized media presentations to dynamic web
       applications.
    </p>
 

script/wcag.js

@@ -25,7 +25,8 @@ function linkUnderstanding() {
 		var pathFrag = titleToPathFrag(heading);
 		var el = document.createElement("div");
 		el.setAttribute("class", "doclinks");
-		el.innerHTML = "<a href=\"" + understandingBaseURI + pathFrag + ".html\">Understanding " + heading + "</a> <span class=\"screenreader\">|</span> <br /><a href=\"https://www.w3.org/WAI/WCAG" + version + "/quickref/#" + pathFrag + "\">How to Meet " + heading + "</a>";
+		el.innerHTML = "<a href=\"" + understandingBaseURI + pathFrag + ".html\">Understanding " + heading +
+			"</a> <span class=\"screenreader\">|</span> <a href=\"https://www.w3.org/WAI/WCAG" + version + "/quickref/#" + pathFrag + "\">How to Meet " + heading + "</a>";
 		if (node.className = "sc") node.insertBefore(el, node.children[2]);
 		if (node.className = "guideline") node.insertBefore(el, node.children[1]);
 	})