Consolidation on the usage of website.

conformance-challenges/index.html

@@ -217,7 +217,7 @@ <h3>Additional Background</h3>
             <li>Any additional challenges, or further illustration of challenges in the existing identified areas below;</li>
             <li>Contributions to the mitigation approaches, and questions or concerns about the mitigation approaches;</li>
         </ul>
-	<p>We seek to gain a thorough understanding of the challenges faced by large, complex, and dynamic websites who are attempting to provide accessible services to their web site users. It is expected that a more thorough understanding of these challenges can lead to either a new conformance model, or an alternative model that is more appropriate for large, complex, and/or dynamic websites (in <a href="https://www.w3.org/WAI/wcag3">WCAG 3.0</a>).</p>
+	<p>We seek to gain a thorough understanding of the challenges faced by large, complex, and dynamic websites who are attempting to provide accessible services to their website users. It is expected that a more thorough understanding of these challenges can lead to either a new conformance model, or an alternative model that is more appropriate for large, complex, and/or dynamic websites (in <a href="https://www.w3.org/WAI/wcag3">WCAG 3.0</a>).</p>
 
         <p class="silver">This document also includes previously published research from the Silver Task Force and Community Group that is related to Challenges with Accessibility Guidelines Conformance and Testing. There is some
 	    overlap between the challenges captured in this published research and the challenges enumerated in the first 4 sections of this document. The research findings have been folded into other sections of this document as appropriate.
@@ -316,7 +316,7 @@ <h3>Mitigations</h3>
         </section>
 	<section id="Challenge-3">
             <h2>Challenge #3: 3rd party content</h2>
-            <p>Very large, highly dynamic web sites generally aggregate content provided by multiple entities. Many of these are third parties with the ability to add content directly to the website&mdash;including potentially every website visitor. The relationship to the 3rd party can be that of a user, a customer, or a professional provider of content such as an advertiser. While the website can provide guidance on how to post content so that it meets accessibility guidance, it is ultimately up to those third parties to understand and correctly implement that guidance. Constraints on page templates and editing facilities can greatly help minimize accessibility issues but, even with automated checks prior to accepting the post, some Success Criteria require human assessment.</p>
+            <p>Very large, highly dynamic websites generally aggregate content provided by multiple entities. Many of these are third parties with the ability to add content directly to the website&mdash;including potentially every website visitor. The relationship to the 3rd party can be that of a user, a customer, or a professional provider of content such as an advertiser. While the website can provide guidance on how to post content so that it meets accessibility guidance, it is ultimately up to those third parties to understand and correctly implement that guidance. Constraints on page templates and editing facilities can greatly help minimize accessibility issues but, even with automated checks prior to accepting the post, some Success Criteria require human assessment.</p>
             <p>Copyright, commercial agreements, and similar constraints that restrict the ability to modify or impose requirements on third party content can also make full conformance claims infeasible.</p>
 	    <section id="Challenge-3.1">
 <h3>Treatment of 3rd party content and Statements of Partial Conformance</h3>
@@ -489,7 +489,7 @@ <h3>Silver Research Findings</h3>
 	<section class="mitigation">
 		<h3>Mitigations</h3>
 
-		<p>We know of no useable mitigations to achieve the <q>Accessibility Supported</q> conformance requirement for public facing web sites. <a href="https://www.w3.org/TR/WCAG-EM/#step1c">WCAG-EM's Second Note</a> suggests that: <q>For some websites in closed networks, such as an intranet website, where both the users and the computers used to access the website are known, this baseline may be limited to the operating systems, web browsers and assistive
+		<p>We know of no useable mitigations to achieve the <q>Accessibility Supported</q> conformance requirement for public facing websites. <a href="https://www.w3.org/TR/WCAG-EM/#step1c">WCAG-EM's Second Note</a> suggests that: <q>For some websites in closed networks, such as an intranet website, where both the users and the computers used to access the website are known, this baseline may be limited to the operating systems, web browsers and assistive
 technologies used within this closed network.</q> It continues saying: <q>However, in most cases this baseline is ideally broader to cover the majority of current user agents used by people with disabilities in any applicable particular geographic region and
 language community.</q> Beyond placing the responsibility on the evaluator to establish this baseline, <a href="https://www.w3.org/TR/UNDERSTANDING-WCAG20/conformance.html#uc-accessibility-support-head">Note 5 in Understanding Conformance 2.0</a> suggests that: <q>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. &#x2026; Authors, companies, technology vendors, or others may document accessibility-supported ways of using Web content technologies.</q> Unfortunately, we know of no such public repository.
 	</p>
@@ -1186,7 +1186,7 @@ <h3>Silver Research Problem Statements</h3>
 			<li>Constraints on <q>What is Strictly Testable</q> provides an obstacle to including guidance that meets the needs of people with disabilities but is not conducive to a pass/fail test.</li>
                     <li>Human Testable (related to Ambiguity) also relates to differences in knowledge and priorities of different testers achieve different results.</li>
                     <li>Accessibility Supported is a conformance requirement of WCAG 2  that is poorly understood and incompletely implemented.</li>
-                    <li>Evolving Technology of the rapidly changing web must constantly be evaluated against the capabilities of assistive technology and evolving assistive technology must be evaluated against the backward compatibility of existing web sites.</li>
+                    <li>Evolving Technology of the rapidly changing web must constantly be evaluated against the capabilities of assistive technology and evolving assistive technology must be evaluated against the backward compatibility of existing websites.</li>
                 </ul>
             </section>
             <section>

guidelines/index.html

@@ -80,7 +80,7 @@ <h3>WCAG 2.2 Supporting Documents</h3>
 					</li>
           <li><p><strong><a href="https://www.w3.org/WAI/standards-guidelines/wcag/new-in-22/">What's New in WCAG 2.2</a></strong> introduces the new success criteria with persona quotes that illustrate the accessibility issues. </p></li>
 				</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>
+				<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 websites, and accessibility policies are listed in <a href="https://www.w3.org/WAI/Resources/Overview">WAI Resources</a>.</p>
 			</section>
         	<section>
         		<h3>Requirements for WCAG 2.2</h3>
@@ -485,7 +485,7 @@ <h3>Required Components of a Conformance Claim</h3>
                         <li>
                             <p><strong>A concise description of the Web pages</strong>, such as a list of URIs for which the claim is made, including whether subdomains are included in the claim.</p>
                             <p class="note">The Web pages may be described by list or by an expression that describes all of the URIs included in the claim.</p>
-                            <p class="note">Web-based products that do not have a URI prior to installation on the customer's Web site may have a statement that the product would conform when installed.</p>
+                            <p class="note">Web-based products that do not have a URI prior to installation on the customer's website may have a statement that the product would conform when installed.</p>
                         </li>
                         <li>A list of the <strong>
                                 <a>Web content technologies</a>
@@ -539,7 +539,7 @@ <h2>Statement of Partial Conformance - Language</h2>
 
             <section class="informative" id="privacy-summary">
                 <h2>Privacy Considerations</h2>
-                <p>Success Criteria within this specification which the Working Group has identified possible implications for privacy, either by providing protections for end users or which are important for web site providers to take in to consideration when implementing features designed to protect user privacy, are listed below. This list reflects the current understanding of the Working Group but other Success Criteria may have privacy implications that the Working Group is not aware of at the time of publishing.</p>
+                <p>Success Criteria within this specification which the Working Group has identified possible implications for privacy, either by providing protections for end users or which are important for website providers to take in to consideration when implementing features designed to protect user privacy, are listed below. This list reflects the current understanding of the Working Group but other Success Criteria may have privacy implications that the Working Group is not aware of at the time of publishing.</p>
                 <p>Success Criteria within this specification that may relate to privacy are:</p>
                 <ul>
                     <li><a href="#timeouts">2.2.6 Timeouts (AAA)</a></li>
@@ -550,7 +550,7 @@ <h2>Privacy Considerations</h2>
 
             <section class="informative" id="security-summary">
                 <h2>Security Considerations</h2>
-                <p>Success Criteria within this specification which the Working Group has identified possible implications for security, either by providing protections for end users or which are important for web site providers to take in to consideration when implementing features designed to protect user security, are listed below. This list reflects the current understanding of the Working Group but other Success Criteria may have security implications that the Working Group is not aware of at the time of publishing.</p>
+                <p>Success Criteria within this specification which the Working Group has identified possible implications for security, either by providing protections for end users or which are important for website providers to take in to consideration when implementing features designed to protect user security, are listed below. This list reflects the current understanding of the Working Group but other Success Criteria may have security implications that the Working Group is not aware of at the time of publishing.</p>
                 <p>Success Criteria within this specification that may relate to security are:</p>
                 <ul>
                     <li><a href="#non-text-content">1.1.1 Non-text Content (A)</a></li>

guidelines/sc/22/accessible-authentication-minimum.html

@@ -14,7 +14,7 @@ <h4>Accessible Authentication (Minimum)</h4>
         <dt>Object Recognition</dt>
         <dd>The cognitive function test is to recognize objects.</dd>
         <dt>Personal Content</dt>
-      <dd>The cognitive function test is to identify <a>non-text content</a> the user provided to the Web site.</dd>
+      <dd>The cognitive function test is to identify <a>non-text content</a> the user provided to the website.</dd>
     </dl>
 
     <p class="note">"Object recognition" and "Personal content" may be represented by images, video, or audio.</p>

guidelines/terms/20/conforming-alternate-version.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/same-functionality.html

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

guidelines/terms/20/web-page.html

@@ -28,8 +28,8 @@
       interactive shopping environment where you visually move around in a store dragging
       products off of the shelves around you and into a visual shopping cart in front of
       you. Clicking on a product causes it to be demonstrated with a specification sheet
-      floating alongside. This might be a single-page Web site or just one page within a
-      Web site.
+      floating alongside. This might be a single-page website or just one page within a
+      website.
    </p></aside>
 
 </dd>

guidelines/terms/21/user-inactivity.html

@@ -1,5 +1,5 @@
 <dt><dfn>user inactivity</dfn></dt>
 <dd>
   <p>any continuous period of time where no user actions occur</p>
-	<p>The method of tracking will be determined by the web site or application.</p>
+	<p>The method of tracking will be determined by the website or application.</p>
 </dd>

guidelines/terms/22/cognitive-function-test.html

@@ -5,7 +5,7 @@
 
    <p>A task that requires the user to remember, manipulate, or transcribe information. Examples include, but are not limited to:</p>
    <ul>
-       <li>memorization, such as remembering a username, password, set of characters, images, or patterns. The common identifiers name, e-mail, and phone number are not considered cognitive function tests as they are personal to the user and consistent across Web sites;</li>
+       <li>memorization, such as remembering a username, password, set of characters, images, or patterns. The common identifiers name, e-mail, and phone number are not considered cognitive function tests as they are personal to the user and consistent across websites;</li>
        <li>transcription, such as typing in characters;</li>
        <li>use of correct spelling;</li>
        <li>performance of calculations;</li>

guidelines/wcag.json

@@ -7841,7 +7841,7 @@
 		},
 		{
 			"handle": "Personal Content",
-			"text": "The cognitive function test is to identify non-text content the user provided to the Web site."
+			"text": "The cognitive function test is to identify non-text content the user provided to the website."
 		}
 				]
 			}],

techniques/css/C7.html

@@ -21,7 +21,7 @@ <h2>Description</h2>
     <p>This technique works by creating a CSS selector to target text that is to be hidden. The rule set for the selector places the text to be hidden in a 1-pixel box with <code class="language-css">overflow:hidden</code>. This ensures the text does not display on screen but remains accessible to assistive technologies such as screen readers and braille displays. Note that the technique does not use <code class="language-css">visibility:hidden</code> or <code class="language-css">display:none</code> properties, since these have the effect of hiding the text from assistive technology in addition to preventing on-screen display.</p>
     <p>This technique is <strong>not</strong> a method for hiding complete links, only a section of text within a link. The <a href="#resources">resources</a> section includes methods for hiding and showing links aimed at screen reader users.</p>
 		<div class="note">
-			<p>This technique to hide link text has been advocated by some screen reader users and corporate Web authors. It has proved effective on some Web sites. Other screen reader users and accessibility experts don't recommend this as a general technique because the results can be overly chatty and constrain the ability of the experienced screen reader user to control the verbosity. The working group believes the technique can be useful for Web pages that do not have repetitive content in the hidden text areas.</p>
+			<p>This technique to hide link text has been advocated by some screen reader users and corporate Web authors. It has proved effective on some websites. Other screen reader users and accessibility experts don't recommend this as a general technique because the results can be overly chatty and constrain the ability of the experienced screen reader user to control the verbosity. The working group believes the technique can be useful for Web pages that do not have repetitive content in the hidden text areas.</p>
 			<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="../css/C29">C29</a> and <a href="https://www.w3.org/WAI/WCAG21/Understanding/conformance#conforming-alt-versions">Understanding Conforming Alternate Versions</a> for more information.</p>
 		</div>
    </section>

techniques/failures/F19.html

@@ -6,15 +6,15 @@
    </section><section id="examples"><h2>Examples</h2>
       <ul>
          <li> A link or a search takes a user directly to one of the nonconforming
-                                pages in the Web site. There is neither an indication that an
+                                pages in the website. There is neither an indication that an
                                 alternate page is available, nor a path to the alternate page from
                                 the nonconforming page. </li>
-         <li> Nonconforming pages on the Web site inform the user that a
+         <li> Nonconforming pages on the website inform the user that a
                                 conforming version is available and provide a link to the home page.
                                 However, the user must search the site for the conforming version of
                                 the page, so the functionality does not meet the requirements of the
                                 Success Criterion. </li>
-         <li> A user is able to use the nonconforming Web site for most pages. But
+         <li> A user is able to use the nonconforming website for most pages. But
                                 when the user is not able to access a particular page, there is no
                                 way to find the conforming version of the page. </li>
       </ul>

techniques/failures/F43.html

@@ -53,7 +53,7 @@ <h3>Using <code class="language-html">blockquote</code> elements to provide addi
                                 not a quotation to give it prominence by indenting it when displayed
                                 in graphical browsers.</p>
 
-<pre xml:space="preserve"><code class="language-html">&lt;p&gt;After extensive study of the company Web site, the task force identified 
+<pre xml:space="preserve"><code class="language-html">&lt;p&gt;After extensive study of the company website, the task force identified 
    the following common problem.&lt;/p&gt;
 
 &lt;blockquote&gt;