Don't just refer to SCs by their number, don't use colon (#4939)

For consistency:

* don't use a colon between the SC number and its title - my main reason
is that it looks somehow "stilted", and when used in a sentence it can
end up "fighting" with the punctuation of the actual sentence
(particularly when not part of a link), and just makes it harder to
parse
* don't just refer to SCs by number alone - (at least for first mentions
in a document) this helps documents be more readable without assuming
that the reader walks around remembering what each SC number is/what
criterion it actually represents.

It would be good to get something decided/officially mentioned in the
style guide (particularly for the use of `:` or not)

EDIT: normative changes split into #4947

---------

Co-authored-by: Kenneth G. Franqueiro <kfranqueiro@users.noreply.github.com>

Author: patrickhlauke

11ty/README.md

@@ -71,14 +71,14 @@ The following list outlines properties available on each technique object:
   - May be empty string (`""`), in which case the subsequent "of" is dropped
 - `usingPrefix` - Adds text to appear before `usingConjunction`
 - `skipUsingPhrase` - Omits the entire "... using ... of the following techniques" phrase
-  - This is mainly an escape hatch for rare instances where a child list is used but no "using" phrase appears at all (e.g. in 1.4.4: Resize Text)
+  - This is mainly an escape hatch for rare instances where a child list is used but no "using" phrase appears at all (e.g. in 1.4.4 Resize Text)
 
 Typically, either `id` or `title` is required.
 If `id` is specified, then `prefix` and/or `suffix` may also be specified (with HTML flow content allowed in each),
 resulting in "{prefix} {linked technique title} {suffix}".
 
 In extremely rare cases, `using` may be specified alone without either `id` or `title`,
-e.g. for top-level "Using two or more of the following" in 2.4.5: Multiple Ways.
+e.g. for top-level "Using two or more of the following" in 2.4.5 Multiple Ways.
 
 #### Conjunctions
 
@@ -87,7 +87,7 @@ To represent multiple parallel techniques, an `and` key may be specified instead
 - `and` - an array of technique objects or shorthand strings (as described above)
 - `using` and its related fields (seen above) may optionally be specified alongside `and`
 - `andConjunction` may optionally be specified alongside `and`,
-  to override the default `"<strong>AND</strong>"` phrasing (e.g. in 4.1.3: Status Messages)
+  to override the default `"<strong>AND</strong>"` phrasing (e.g. in 4.1.3 Status Messages)
 - Techniques listed _within_ `and` should be flat, never containing `and` or `using`
 
 ### Situations or Other Subsections (Sufficient only)
@@ -96,19 +96,19 @@ The top level of the `sufficient` array may consist entirely of either technique
 or subsection entries. It should not contain a mix of both.
 
 Subsections are typically used to define multiple "situations", where each title begins with "Situation A:", "Situation B:", etc.;
-in rare cases it is used for other purposes, e.g. in 1.4.8: Visual Presentation.
+in rare cases it is used for other purposes, e.g. in 1.4.8 Visual Presentation.
 
 Subsection entries contain the following:
 
 - `title` (required, HTML allowed)
 - `techniques` (required) - array of technique entries (see above)
-- `note` (optional, HTML allowed) - content to appear in a Note at the end of the subsection (e.g. in 4.1.3: Status Messages)
+- `note` (optional, HTML allowed) - content to appear in a Note at the end of the subsection (e.g. in 4.1.3 Status Messages)
 - `groups` (optional) - array of objects with `id`, `title`, `techniques`; see more below
   - `techniques` within `groups` are not expected to involve `and` or `using`
 
 #### Groups within Situations
 
-Most of the situations in 1.1.1: Non-text Content include groupings which start with a boldface paragraph (not a heading),
+Most of the situations in 1.1.1 Non-text Content include groupings which start with a boldface paragraph (not a heading),
 and are referenced one or more times within preceding "using" clauses.
 Groups can be defined at the top level of each situation/section entry as mentioned above.
 Defining `groups` automatically implies a "using" relationship, without explicitly defining `using` for each technique.

README.md

@@ -178,7 +178,7 @@ Obsolete techniques should not be removed from the repository. Instead, they can
 ---
 obsoleteSince: 22
 obsoleteMessage: |
-  This failure relates to 4.1.1: Parsing, which was removed as of WCAG 2.2.
+  This failure relates to 4.1.1 Parsing, which was removed as of WCAG 2.2.
 ---
 ```
 

_includes/understanding/h1.html

@@ -4,7 +4,7 @@ <h1>
     Understanding
     <a href="https://w3.org/TR/WCAG{{ version }}#{{ page.fileSlug }}">
       {{- guideline.type }} {{ guideline.num -}}
-    </a>:
+    </a>
   </span>{{ guideline.name }}
   {%- if guideline.level %} (Level {{ guideline.level }}){% endif %}
 </h1>

eleventy.config.ts

@@ -378,7 +378,7 @@ export default async function (eleventyConfig: any) {
           const urlBase = this.page.filePathStem.startsWith("/understanding/")
             ? ""
             : baseUrls.understanding;
-          const label = `${guideline.num}: ${guideline.name}`;
+          const label = `${guideline.num} ${guideline.name}`;
           return `<a href="${urlBase}${id}">${label}</a>`;
         })
         .join("\nand\n");

techniques/client-side-script/SCR29.html

@@ -21,7 +21,7 @@ <h2>Description</h2>
       <p>When the <code>tabindex</code> attribute has the value <code>0</code>, the element can be focused via the keyboard and is included in the tab order of the document. When the <code>tabindex</code> attribute has the value <code>-1</code>, the element cannot be tabbed to, but focus can be set programmatically, using <code>element.focus()</code>.</p>
       <p>Because static HTML elements do not have actions associated with them, it is not possible to provide a backup implementation or explanation in environments in which scripting is not available. This technique should only be used in environments in which client-side scripting can be relied upon.</p>
       <div class="note">
-				<p>Such user interface controls must still satisfy Success Criterion 4.1.2. Applying this technique without also providing role, name, and state information about the user interface control will results in <a href="../failures/F59">Failure F59</a>, Failure of Success Criterion 4.1.2 due to using script to make <code>div</code> or <code>span</code> a user interface control in HTML.</p>
+				<p>Such user interface controls must still satisfy Success Criterion 4.1.2 Name, Role, Value. Applying this technique without also providing role, name, and state information about the user interface control will results in <a href="../failures/F59">Failure F59</a>, Failure of Success Criterion 4.1.2 due to using script to make <code>div</code> or <code>span</code> a user interface control in HTML.</p>
       </div>
 		</section>
 		<section id="examples">

techniques/css/C30.html

@@ -18,7 +18,7 @@ <h2>When to Use</h2>
 		<section id="description">
 			<h2>Description</h2>
       <p>The objective of this technique is to demonstrate how CSS can be used to replace structured <abbr title="HyperText Markup Language">HTML</abbr> text with images of text in a way that makes it possible for users to view content according to their preferences. To use this technique, an author starts by creating an HTML page that uses semantic elements to mark up the structure of the page. The author then designs two or more stylesheets for that page. One stylesheet presents the HTML text as text and the second uses CSS features to replace some of the HTML text with images of text. Finally, through the use of server-side or client-side scripting, the author provides a control that allows the user to switch between the available views.</p>
-      <p>This technique can be used to meet Success Criterion 1.4.5 or 1.4.9 if a presentation that does not include images of text is available and as long as the user interface control that is provided to allow users to switch to an alternate presentation meets the relevant criteria. Where possible, authors should deliver the presentation that does not include images of text as the default presentation. In addition, the control used to switch should be located near the beginning of the page.</p>
+      <p>This technique can be used to meet Success Criterion 1.4.5 Images of Text or 1.4.9 Images of Text (No Exception) if a presentation that does not include images of text is available and as long as the user interface control that is provided to allow users to switch to an alternate presentation meets the relevant criteria. Where possible, authors should deliver the presentation that does not include images of text as the default presentation. In addition, the control used to switch should be located near the beginning of the page.</p>
       <p>A variety of "image replacement" techniques have been developed to address a variety of user agent, configuration and compatibility with assistive technology issues (See resources for more information). While there are a variety of approaches authors may use to replace text, it is important to consider compatibility with assistive technology, whether the technique will work correctly if scripting, CSS, images (or combinations of these) are turned off. Since it can be difficult to find a single solution that works in all cases, this technique recommends the use of a control that allows users to switch to a presentation that does not include an image replacement technique.</p>
       <div class="note">
 				<p>This technique can be used in combination with a style switching technique to present a page that is a <a>conforming alternate version</a> for non-conforming content. Refer to <a href="C29">C29</a> and <a href="../../Understanding/conformance#conforming-alt-versions">Understanding Conforming Alternate Versions</a> for more information.</p>

techniques/failures/F103.html

@@ -29,7 +29,7 @@ <h2>Description</h2>
 					<li>the new content does not take focus (does not change context);</li>
 					<li>the new content provides information to the user on the outcome of an action, the state of an application, the progress of a process, or the existence of errors.</li>
 				</ol>
-			 Where updated content does not conform to the definition of <a>status messages</a>, a failure of 4.1.3 has not taken place.</p>
+			 Where updated content does not conform to the definition of <a>status messages</a>, a failure of 4.1.3 Status Messages has not taken place.</p>
 				<p>The second step in this failure technique involves examining code.  Where dynamic content meets the definition of a status message, its container can be examined for an appropriate WAI-ARIA role or property which allows it to be programmatically determinable as a status message. Currently there are only a small number of techniques available to indicate status messages to assistive technologies. They are:
 					<ul>
 						<li>the HTML <code>output</code> element</li>

techniques/failures/F105.html

@@ -49,7 +49,7 @@ <h3>Expected Results</h3>
 		<section id="related">
 			<h2>Related Techniques</h2>
       <ul>
-				<li><a href="F101">Failure of Success Criterion 2.5.2 due to activating a control on the down-event</a>.</li>
+				<li><a href="F101">Failure of Success Criterion 2.5.2 Pointer Cancellation due to activating a control on the down-event</a>.</li>
       	<li><a href="../general/G216">Providing single point activation for a control slider</a></li>
 			</ul>
 		</section>

techniques/failures/F107.html

@@ -19,7 +19,7 @@ <h2>Applicability</h2>
       <h2>Description</h2>
       <p>The purpose of this technique is to identify a failure condition where form inputs do not have the correct <code>autocomplete</code> attribute values for inputs that request information about the user of the form.</p>
 
-      <p>Success Criterion 1.3.5 uses a fixed list of tokens in <a href="/TR/WCAG/#input-purposes">Input Purposes for user interface components</a> (based on the HTML 5.2 <code>autocomplete</code> attribute's fixed list of token values) because the programmatic association of specified token values (metadata) allows for other machine processing, such as expressing the input label in different modalities.</p>
+      <p>Success Criterion 1.3.5 Identify Input Purpose uses a fixed list of tokens in <a href="/TR/WCAG/#input-purposes">Input Purposes for user interface components</a> (based on the HTML 5.2 <code>autocomplete</code> attribute's fixed list of token values) because the programmatic association of specified token values (metadata) allows for other machine processing, such as expressing the input label in different modalities.</p>
 
       <p>Another important part of this success criterion is that the token values are associated with inputs that are <strong>scoped directly to the primary end user</strong>.</p>
     </section>

techniques/failures/F109.html

@@ -21,7 +21,7 @@ <h1>Failure of Success Criterion 3.3.8 and 3.3.9 due to preventing password or c
    <section id="description">
     <h2>Description</h2>
 
-    <p>Requiring users to authenticate by entering a password or code in a different format from which it was originally created is a failure to meet Success Criteria 3.3.8 and 3.3.9 (unless alternative authentication methods are available). The string to be entered could include a password, verification code, or any string of characters the user has to remember or record to authenticate.</p>
+    <p>Requiring users to authenticate by entering a password or code in a different format from which it was originally created is a failure to meet Success Criteria 3.3.8 Accessible Authentication (Minimum) and 3.3.9 Accessible Authentication (Enhanced) (unless alternative authentication methods are available). The string to be entered could include a password, verification code, or any string of characters the user has to remember or record to authenticate.</p>
 
     <p>If a user is required to enter individual characters across multiple fields in a way that prevents pasting the password in a single action, it prevents use of a password manager or pasting from local copy of the password. This means users cannot avoid transcription, resulting in a <a>cognitive function test</a>. This applies irrespective of whether users are required to enter all characters in the string, or just a subset.</p>
 
@@ -42,7 +42,7 @@ <h2>Examples</h2>
         <p>For each form field which accepts password or code entry:</p>
          <ol>
             <li>Check if the structure of the input field(s) prevents the user from pasting or auto-filling the entire password or code in the format in which it was originally created.</li>
-            <li>Confirm that no other acceptable authentication methods are present that satisfy Success Criteria 3.3.8 or 3.3.9 (such as an authentication method that does not rely on a cognitive function test).</li>
+            <li>Confirm that no other acceptable authentication methods are present that satisfy Success Criteria 3.3.8 Accessible Authentication (Minimum) or 3.3.9 Accessible Authentication (Enhanced) (such as an authentication method that does not rely on a cognitive function test).</li>
          </ol>
       </section>
       <section class="results"><h3>Expected Results</h3>