Cfc style updates (#4080)

Style changes to normative documents made to ensure consistency as part
of the republishing of WCAG 2.2
- Ensures all normative occurrences of "web page" are two words and
lower case.
- Ensures all normative occurrences of "website" are a single word, not
capitalized.
- Ensures all normative occurrences of "success criterion/criteria" that
do not specify SCs by name, are lower case
- Ensures all normative occurrences of "web content" and other uses of
"web" are lower case


<!--
    This comment and the below content is programmatically generated.
    You may add a comma-separated list of anchors you'd like a
    direct link to below (e.g. #idl-serializers, #idl-sequence):

    Don't remove this comment or modify anything below this line.
    If you don't want a preview generated for this pull request,
    just replace the whole of this comment's content by "no preview"
    and remove what's below.
-->
***
<a href="https://pr-preview.s3.amazonaws.com/w3c/wcag/pull/4080.html"
title="Last updated on Oct 4, 2024, 3:14 PM UTC (571cf14)">Preview</a> |
<a
href="https://pr-preview.s3.amazonaws.com/w3c/wcag/4080/bf4b123...571cf14.html"
title="Last updated on Oct 4, 2024, 3:14 PM UTC (571cf14)">Diff</a>

---------

Co-authored-by: Alastair Campbell <[email protected]>

Author: mbgower

guidelines/index.html

@@ -48,7 +48,7 @@ <h2>Input Purposes for User Interface Components</h2>
 		<li><strong>bday-month</strong> - Month component of birthday</li>
 		<li><strong>bday-year</strong> - Year component of birthday</li>
 		<li><strong>sex</strong> - Gender identity (e.g., Female, <span lang="sm">Fa’afafine</span>)</li>
-		<li><strong>url</strong> - Home page or other Web page corresponding to the company, person, address, or contact information in the other fields associated with this field</li>
+		<li><strong>url</strong> - Home page or other web page corresponding to the company, person, address, or contact information in the other fields associated with this field</li>
 		<li><strong>photo</strong> - Photograph, icon, or other image corresponding to the company, person, address, or contact information in the other fields associated with this field</li>
 		<li><strong>tel</strong> - Full telephone number, including country code</li>
 		<li><strong>tel-country-code</strong> - Country code component of the telephone number</li>

guidelines/input-purposes.html

@@ -340,7 +340,7 @@ <h1>MathML version of the relative luminance definition</h1>
         </div>
         <div class="note" role="note" id="issue-container-generatedID-129"><div role="heading" class="note-title marker" id="h-note-129" aria-level="3"><span>Note</span><!---0.410359%--></div><p class="">Before May 2021 the value of 0.04045 in the definition was different (0.03928). It was taken from an older version of the specification and has been updated. It has no practical effect on the calculations in the context of these guidelines.</p></div>
 
-        <div class="note" role="note" id="issue-container-generatedID-130"><div role="heading" class="note-title marker" id="h-note-130" aria-level="3"><span>Note</span><!---0.410359%--></div><p class="">Almost all systems used today to view Web content assume sRGB encoding. Unless it
+        <div class="note" role="note" id="issue-container-generatedID-130"><div role="heading" class="note-title marker" id="h-note-130" aria-level="3"><span>Note</span><!---0.410359%--></div><p class="">Almost all systems used today to view web content assume sRGB encoding. Unless it
           is known that another color space will be used to process and display the content,
           authors should evaluate using sRGB colorspace. If using other color spaces, see <a href="https://www.w3.org/WAI/WCAG22/Understanding/contrast-minimum">Understanding Success Criterion 1.4.3</a>.
         </p></div>

guidelines/relative-luminance.html

@@ -4,12 +4,12 @@ <h4>Audio Control</h4>
 
    <p class="conformance-level">A</p>
 
-   <p>If any audio on a Web page plays automatically for more than 3 seconds, either a <a>mechanism</a> is available to pause or stop the audio, or a mechanism is available to control audio
+   <p>If any audio on a web page plays automatically for more than 3 seconds, either a <a>mechanism</a> is available to pause or stop the audio, or a mechanism is available to control audio
       volume independently from the overall system volume level.
    </p>
 
    <p class="note">Since any content that does not meet this success criterion can interfere with a user's
-      ability to use the whole page, all content on the Web page (whether or not it is used
+      ability to use the whole page, all content on the web page (whether or not it is used
       to meet other success criteria) must meet this success criterion. See <a href="#cc5">Conformance Requirement 5: Non-Interference</a>.
    </p>
 

guidelines/sc/20/audio-control.html

@@ -4,7 +4,7 @@ <h4>Bypass Blocks</h4>
 
    <p class="conformance-level">A</p>
 
-   <p>A <a>mechanism</a> is available to bypass blocks of content that are repeated on multiple <a>Web pages</a>.
+   <p>A <a>mechanism</a> is available to bypass blocks of content that are repeated on multiple <a>web pages</a>.
    </p>
 
 </section>

guidelines/sc/20/bypass-blocks.html

@@ -4,7 +4,7 @@ <h4>Consistent Identification</h4>
 
    <p class="conformance-level">AA</p>
 
-   <p>Components that have the <a>same functionality</a> within a <a>set of Web pages</a> are identified consistently.
+   <p>Components that have the <a>same functionality</a> within a <a>set of web pages</a> are identified consistently.
    </p>
 
 </section>

guidelines/sc/20/consistent-identification.html

@@ -4,7 +4,7 @@ <h4>Consistent Navigation</h4>
 
    <p class="conformance-level">AA</p>
 
-   <p>Navigational mechanisms that are repeated on multiple <a>Web pages</a> within a <a>set of Web pages</a> occur in the <a>same relative order</a> each time they are repeated, unless a change is initiated by the user.
+   <p>Navigational mechanisms that are repeated on multiple <a>web pages</a> within a <a>set of web pages</a> occur in the <a>same relative order</a> each time they are repeated, unless a change is initiated by the user.
    </p>
 
 </section>

guidelines/sc/20/consistent-navigation.html

@@ -4,7 +4,7 @@ <h4>Error Prevention (All)</h4>
 
    <p class="conformance-level">AAA</p>
 
-   <p>For <a>Web pages</a> that require the user to submit information, at least one of the following is true:
+   <p>For <a>web pages</a> that require the user to submit information, at least one of the following is true:
    </p>
 
    <dl>

guidelines/sc/20/error-prevention-all.html

@@ -4,7 +4,7 @@ <h4>Error Prevention (Legal, Financial, Data)</h4>
 
    <p class="conformance-level">AA</p>
 
-   <p>For <a>Web pages</a> that cause <a>legal commitments</a> or financial transactions for the user to occur, that modify or delete <a>user-controllable</a> data in data storage systems, or that submit user test responses, at least one of
+   <p>For <a>web pages</a> that cause <a>legal commitments</a> or financial transactions for the user to occur, that modify or delete <a>user-controllable</a> data in data storage systems, or that submit user test responses, at least one of
       the following is true:
    </p>
 

guidelines/sc/20/error-prevention-legal-financial-data.html

@@ -4,7 +4,7 @@ <h4>Focus Order</h4>
 
    <p class="conformance-level">A</p>
 
-   <p>If a <a>Web page</a> can be <a>navigated sequentially</a> and the navigation sequences affect meaning or operation, focusable components receive
+   <p>If a <a>web page</a> can be <a>navigated sequentially</a> and the navigation sequences affect meaning or operation, focusable components receive
       focus in an order that preserves meaning and operability.
    </p>