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 <ac@alastc.com>
(cherry picked from commit a2c3cb3)

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, Fa’afafine)</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

@@ -341,7 +341,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>
 

guidelines/sc/20/focus-order.html

@@ -4,7 +4,7 @@ <h4>Language of Page</h4>
 
    <p class="conformance-level">A</p>
 
-   <p>The default <a>human language</a> of each <a>Web page</a> can be <a>programmatically determined</a>.
+   <p>The default <a>human language</a> of each <a>web page</a> can be <a>programmatically determined</a>.
    </p>
 
 </section>

guidelines/sc/20/language-of-page.html

@@ -4,7 +4,7 @@ <h4>Location</h4>
 
    <p class="conformance-level">AAA</p>
 
-   <p>Information about the user's location within a <a>set of Web pages</a> is available.
+   <p>Information about the user's location within a <a>set of web pages</a> is available.
    </p>
 
 </section>

guidelines/sc/20/location.html

@@ -4,7 +4,7 @@ <h4>Multiple Ways</h4>
 
    <p class="conformance-level">AA</p>
 
-   <p>More than one way is available to locate a <a>Web page</a> within a <a>set of Web pages</a> except where the Web Page is the result of, or a step in, a <a>process</a>.
+   <p>More than one way is available to locate a <a>web page</a> within a <a>set of web pages</a> except where the web page is the result of, or a step in, a <a>process</a>.
    </p>
 
 </section>

guidelines/sc/20/multiple-ways.html

@@ -8,7 +8,7 @@ <h4>Name, Role, Value</h4>
       the <a>name</a> and <a>role</a> can be <a>programmatically determined</a>; states, properties, and values that can be set by the user can be <a>programmatically set</a>; and notification of changes to these items is available to <a>user agents</a>, including <a>assistive technologies</a>.
    </p>
 
-   <p class="note">This success criterion is primarily for Web authors who develop or script their own
+   <p class="note">This success criterion is primarily for web authors who develop or script their own
       user interface components. For example, standard HTML controls already meet this success
       criterion when used according to specification.
    </p>

guidelines/sc/20/name-role-value.html

@@ -10,7 +10,7 @@ <h4>No Keyboard Trap</h4>
    </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 it is used to
+      ability to use the whole page, all content on the web page (whether it is used to
       meet other success criteria or not) must meet this success criterion. See <a href="#cc5">Conformance Requirement 5: Non-Interference</a>.
    </p>
 

guidelines/sc/20/no-keyboard-trap.html

@@ -39,7 +39,7 @@ <h4>Pause, Stop, Hide</h4>
    </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 it is used to
+      ability to use the whole page, all content on the web page (whether it is used to
       meet other success criteria or not) must meet this success criterion. See <a href="#cc5">Conformance Requirement 5: Non-Interference</a>.
    </p>
 

guidelines/sc/20/pause-stop-hide.html

@@ -9,7 +9,7 @@ <h4>Three Flashes or Below Threshold</h4>
    </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 it is used to
+      ability to use the whole page, all content on the web page (whether it is used to
       meet other success criteria or not) must meet this success criterion. See <a href="#cc5">Conformance Requirement 5: Non-Interference</a>.
    </p>
 

guidelines/sc/20/three-flashes-or-below-threshold.html

@@ -3,16 +3,16 @@
 
    <p>supported by users' <a>assistive technologies</a> as well as the accessibility features in browsers and other <a>user agents</a></p>
 
-   <p>To qualify as an accessibility-supported use of a Web content technology (or feature
-      of a technology), both 1 and 2 must be satisfied for a Web content technology (or
+   <p>To qualify as an accessibility-supported use of a web content technology (or feature
+      of a technology), both 1 and 2 must be satisfied for a web content technology (or
       feature):
    </p>
 
    <ol>
 
       <li>
 
-         <p><strong>The way that the <a>Web content technology</a> is used must be supported by users' assistive technology (AT). </strong> This means that the way that the technology is used has been tested for interoperability
+         <p><strong>The way that the <a>web content technology</a> is used must be supported by users' assistive technology (AT). </strong> This means that the way that the technology is used has been tested for interoperability
             with users' assistive technology in the <a>human language(s)</a> of the content,
          </p>
 
@@ -22,7 +22,7 @@
 
       <li>
 
-         <p><strong>The Web content technology must have accessibility-supported user agents that are
+         <p><strong>The web content technology must have accessibility-supported user agents that are
                available to users. </strong> This means that at least one of the following four statements is true:
          </p>
 
@@ -79,29 +79,29 @@
    </ol>
 
    <p class="note">The Accessibility Guidelines Working Group and the W3C do not specify which or how much support by assistive
-      technologies there must be for a particular use of a Web technology in order for it
+      technologies there must be for a particular use of a web technology in order for it
       to be classified as accessibility supported. (See <a href="https://www.w3.org/WAI/WCAG21/Understanding/conformance#support-level">Level of Assistive Technology Support Needed for "Accessibility Support"</a>.)
    </p>
 
    <p class="note">Web technologies can be used in ways that are not accessibility supported as long
       as they are not <a>relied upon</a> and the page as a whole meets the conformance requirements, including <a href="#cc4">Conformance Requirement 4</a> and <a href="#cc5">Conformance Requirement 5</a>.
    </p>
 
-   <p class="note">When a <a>Web Technology</a> is used in a way that is "accessibility supported," it does not imply that the entire
+   <p class="note">When a <a>web technology</a> is used in a way that is "accessibility supported," it does not imply that the entire
       technology or all uses of the technology are supported. Most technologies, including
       HTML, lack support for at least one feature or use. Pages conform to WCAG only if
       the uses of the technology that are accessibility supported can be relied upon to
       meet WCAG requirements.
    </p>
 
-   <p class="note">When citing Web content technologies that have multiple versions, the version(s) supported
+   <p class="note">When citing web content technologies that have multiple versions, the version(s) supported
       should be specified.
    </p>
 
    <p class="note">One way for authors to locate uses of a technology that are accessibility supported
       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
+      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
       content technologies above.
    </p>

guidelines/terms/20/accessibility-supported.html

@@ -1,7 +1,7 @@
 <dt><dfn id="dfn-ambiguous-to-users-in-general">ambiguous to users in general</dfn></dt>
 <dd>
 
-   <p>the purpose cannot be determined from the link and all information of the Web page
+   <p>the purpose cannot be determined from the link and all information of the web page
       presented to the user simultaneously with the link (i.e., readers without disabilities
       would not know what a link would do until they activated it)
    </p>

guidelines/terms/20/ambiguous-to-users-in-general.html

@@ -23,7 +23,7 @@
       target narrowly defined populations of users with specific disabilities. The assistance
       provided by an assistive technology is more specific and appropriate to the needs
       of its target users. The mainstream user agent may provide important functionality
-      to assistive technologies like retrieving Web content from program objects or parsing
+      to assistive technologies like retrieving web content from program objects or parsing
       markup into identifiable bundles.
    </p>
 

guidelines/terms/20/assistive-technology.html

@@ -17,7 +17,7 @@
 
       <li>focus;</li>
 
-      <li><a>content</a> that changes the meaning of the <a>Web page</a>
+      <li><a>content</a> that changes the meaning of the <a>web page</a>
       </li>
 
    </ul>

guidelines/terms/20/changes-of-context.html

@@ -52,7 +52,7 @@
    </p>
 
    <p class="note">The conforming alternative version does not need to reside within the scope of conformance,
-      or even on the same Web site, as long as it is as freely available as the non-conforming
+      or even on the same website, as long as it is as freely available as the non-conforming
       version.
    </p>
 

guidelines/terms/20/conforming-alternate-version.html

@@ -1,4 +1,4 @@
-<dt><dfn id="dfn-content">content</dfn> (Web content)
+<dt><dfn id="dfn-content">content</dfn> (web content)
 </dt>
 <dd>
 

guidelines/terms/20/content.html

@@ -35,7 +35,7 @@
       viewing distance) on a side does not violate the thresholds.
    </p>
 
-   <p class="note">For general software or Web content, using a 341 x 256 pixel rectangle anywhere on the displayed screen area when the content is viewed at 1024 x 768 pixels will provide a good estimate of a 10 degree visual field for standard screen sizes and viewing distances (e.g., 15-17 inch screen at 22-26 inches). This resolution of 75 - 85 ppi is known to be lower, and thus more conservative than the nominal CSS pixel resolution of 96 ppi in CSS specifications. Higher resolutions displays showing the same rendering of the content yield smaller and safer images so it is lower resolutions that are used to define the thresholds.
+   <p class="note">For general software or web content, using a 341 x 256 pixel rectangle anywhere on the displayed screen area when the content is viewed at 1024 x 768 pixels will provide a good estimate of a 10 degree visual field for standard screen sizes and viewing distances (e.g., 15-17 inch screen at 22-26 inches). This resolution of 75 - 85 ppi is known to be lower, and thus more conservative than the nominal CSS pixel resolution of 96 ppi in CSS specifications. Higher resolutions displays showing the same rendering of the content yield smaller and safer images so it is lower resolutions that are used to define the thresholds.
    </p>
 
    <p class="note">A transition is the change in relative luminance (or relative luminance/color for

guidelines/terms/20/general-flash-and-red-flash-thresholds.html

@@ -8,7 +8,7 @@
 
      <ol>
 
-      <li>Information that is required by the <a>Web page</a> but omitted by the user
+      <li>Information that is required by the <a>web page</a> but omitted by the user
       </li>
 
       <li>Information that is provided by the user but that falls outside the required data

guidelines/terms/20/input-error.html

@@ -1,7 +1,7 @@
 <dt><dfn id="dfn-labels" data-lt="labels">label</dfn></dt>
 <dd>
 
-   <p><a>text</a> or other component with a <a>text alternative</a> that is presented to a user to identify a component within Web <a>content</a></p>
+   <p><a>text</a> or other component with a <a>text alternative</a> that is presented to a user to identify a component within web <a>content</a></p>
 
    <p class="note">A label is presented to all users whereas the <a>name</a> may be hidden and only exposed by assistive technology. In many (but not all) cases
       the name and the label are the same.

guidelines/terms/20/label.html

@@ -1,7 +1,7 @@
 <dt><dfn id="dfn-name">name</dfn></dt>
 <dd>
 
-   <p>text by which software can identify a component within Web content to the user</p>
+   <p>text by which software can identify a component within web content to the user</p>
 
    <p class="note">The name may be hidden and only exposed by assistive technology, whereas a <a>label</a> is presented to all users. In many (but not all) cases, the label and the name are
       the same.

guidelines/terms/20/name.html

@@ -3,7 +3,7 @@
 
    <p>series of user actions where each action is required in order to complete an activity</p>
 
-   <aside class="example"><p>Successful use of a series of Web pages on a shopping site requires users to view
+   <aside class="example"><p>Successful use of a series of web pages on a shopping site requires users to view
       alternative products, prices and offers, select products, submit an order, provide
       shipping information and provide payment information.
    </p></aside>

guidelines/terms/20/process.html

@@ -43,7 +43,7 @@
 
   <p class="note">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>
 
-   <p class="note">Almost all systems used today to view Web content assume sRGB encoding. Unless it
+   <p class="note">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/WCAG21/Understanding/contrast-minimum">Understanding Success Criterion 1.4.3</a>.
    </p>

guidelines/terms/20/relative-luminance.html

@@ -3,8 +3,8 @@
 
    <p>same result when used</p>
 
-   <aside class="example"><p>A submit "search" button on one Web page and a "find" button on another Web page may
-      both have a field to enter a term and list topics in the Web site related to the term
+   <aside class="example"><p>A submit "search" button on one web page and a "find" button on another web page may
+      both have a field to enter a term and list topics in the website related to the term
       submitted. In this case, they would have the same functionality but would not be labeled
       consistently.
    </p></aside>