"Web" to "web", "Success criteria" to "success criteria"

_includes/understanding/intro/advisory.html

@@ -5,7 +5,7 @@
   If there are techniques, however, for addressing this guideline that do not fall under
   any of the success criteria, they are listed here.
   These techniques are not required or sufficient for meeting any success criteria,
-  but can make certain types of Web content more accessible to more people.
+  but can make certain types of web content more accessible to more people.
 </p>
 {%- else -%}
 <p>

conformance-challenges/index.html

@@ -407,16 +407,16 @@ <h2>Challenge #5: Accessibility Supported</h2>
 		<a href="https://www.w3.org/TR/UNDERSTANDING-WCAG20/conformance.html#uc-accessibility-supported-definition-head">
 			 first Note under the definition of Accessibility Supported</a> states that: <q>The WCAG 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
+technologies there must be for a particular use of a web technology in
 order for it to be classified as accessibility supported.</q>
 This is further expanded upon in the section
 			<a href="https://www.w3.org/TR/UNDERSTANDING-WCAG20/conformance.html#uc-support-level-head">
 				Level of Assistive Technology Support Needed for <q>Accessibility Support:</q></a>
 <q>This topic raises the question of how many
-or which assistive technologies must support a Web technology in order
-for that Web technology to be considered <q>accessibility supported.</q> The
+or which assistive technologies must support a web technology in order
+for that web technology to be considered <q>accessibility supported.</q> The
 WCAG Working group and the W3C do not specify which or how many
-assistive technologies must support a Web technology in order for it to
+assistive technologies must support a web technology in order for it to
 be classified as accessibility supported. This is a complex topic and
 one that varies both by environment and by language.</q></p>
 
@@ -464,7 +464,7 @@ <h3>Mitigations</h3>
 
 		<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.
+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>
 	</section>
 	</section>

guidelines/index.html

@@ -116,7 +116,7 @@ <h4>Numbering in WCAG 2.2</h4>
 				</section>
 				<section id="conformance-to-wcag-2-2">
 					<h4>Conformance to WCAG 2.2</h4>
-					<p>WCAG 2.2 uses the same conformance model as WCAG 2.0. It is intended that sites that conform to WCAG 2.2 also conform to WCAG 2.0 and WCAG 2.1, which means they meet the requirements of any policies that reference WCAG 2.0 or WCAG 2.1, while also better meeting the needs of users on the current Web. </p>
+					<p>WCAG 2.2 uses the same conformance model as WCAG 2.0. It is intended that sites that conform to WCAG 2.2 also conform to WCAG 2.0 and WCAG 2.1, which means they meet the requirements of any policies that reference WCAG 2.0 or WCAG 2.1, while also better meeting the needs of users on the current web. </p>
 				</section>
 			</section>
         	<section id="later-versions-of-accessibility-guidelines">
@@ -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 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 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 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 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/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>
 

requirements/21/index.html

@@ -113,7 +113,7 @@
 <section id="introduction">
 	<h2>Introduction</h2>
 	<p><a href="https://www.w3.org/TR/WCAG20/">Web Content Accessibility Guidelines 2.0 (WCAG 2.0)</a> [[WCAG20]] explains how to make Web content accessible to people with disabilities. Since the release of WCAG 2.0 in December 2008 WCAG 2.0 has been widely adopted and implemented. As a result of both feedback from implementers and significant changes in technologies, the WCAG WG is pursuing the development of dot.x specifications and support materials to address special topic areas as needed, including (but not limited to) mobile devices, cognitive impairments and learning disabilities, and low vision.</p>
-			<p>The underlying goal of dot.x requirements are the same as for WCAG 2.0 – to promote accessibility of Web content. Dot.x requirements must satisfy additional goals addressed in this document including:</p>
+			<p>The underlying goal of dot.x requirements are the same as for WCAG 2.0 – to promote accessibility of web content. Dot.x requirements must satisfy additional goals addressed in this document including:</p>
 			<ul>
 				<li>Pre-existing requirements for WCAG 2.0.</li>
 				<li>Ensure that web pages which conform to WCAG 2.1 conform to WCAG 2.0.</li>

requirements/22/index.html

@@ -119,13 +119,13 @@
   <section id="introduction">
     <h2>Introduction</h2>
     <p><a href="https://www.w3.org/TR/WCAG20/">Web Content Accessibility Guidelines 2.0 (WCAG 2.0)</a> [[WCAG20]]
-      explains how to make Web content accessible to people with disabilities. Since the release of WCAG 2.0 in December
+      explains how to make web content accessible to people with disabilities. Since the release of WCAG 2.0 in December
       2008 and the release of WCAG 2.1 in June 2018, these standards have been widely adopted and implemented. As a
       result of feedback from implementers, ongoing changes in technologies, and responding to the need for regular
       updates in accessibility content standards, the Accessibility Guidelines Working Group (AGWG) is pursuing the
       development of WCAG 2.2.</p>
     <p>The underlying goal of WCAG 2.2 requirements are the same as for WCAG 2.0 and WCAG 2.1 – to promote accessibility
-      of Web content. WCAG 2.2 must satisfy additional requirements addressed in this document including:</p>
+      of web content. WCAG 2.2 must satisfy additional requirements addressed in this document including:</p>
     <ul>
       <li>Web pages which conform to WCAG 2.2 conform to WCAG 2.1 (which conforms to WCAG 2.0).</li>
       <li>WCAG 2.2 success criteria continue support additional use-cases.</li>

techniques/client-side-script/SCR27.html

@@ -151,7 +151,7 @@ <h2>Tests</h2>
     <section class="procedure">
       <h3>Procedure</h3>
       <ol>
-        <li>Find all components in the Web Unit which can be reordered via drag and drop.</li>
+        <li>Find all components in the web unit which can be reordered via drag and drop.</li>
         <li>Check that there is also a mechanism to reorder them using menus build of lists of links.</li>
         <li>Check that the menus are contained within the re-orderable items in the DOM.</li>
         <li>Check that scripts for reordering are triggered only from the onclick event of links.</li>

techniques/css/C9.html

@@ -16,7 +16,7 @@ <h2>When to Use</h2>
    </section>
 	 <section id="description">
 		<h2>Description</h2>
-		<p> The objective of this technique is to provide a mechanism to add purely decorative images and images used for visual formatting to Web content without requiring additional markup within the content. This makes it possible for assistive technologies to ignore the non-text content. Some user agents can ignore or turn off CSS at the user's request, so that background images included with CSS simply "disappear" and do not interfere with display settings such as enlarged fonts or high contrast settings.</p>
+		<p> The objective of this technique is to provide a mechanism to add purely decorative images and images used for visual formatting to web content without requiring additional markup within the content. This makes it possible for assistive technologies to ignore the non-text content. Some user agents can ignore or turn off CSS at the user's request, so that background images included with CSS simply "disappear" and do not interfere with display settings such as enlarged fonts or high contrast settings.</p>
 		<p>Background images can be included with the following CSS properties:</p>
       <ul>
          <li><code class="language-css">background</code>;</li>

techniques/failures/F2.html

@@ -31,7 +31,7 @@ <h3>Images of text used as headings where the images are not marked up with head
             <p>Chapter1.gif is an image of the words, "Chapter One" in a Garamond font sized at 20 pixels. This is a failure because at a minimum the img element should be enclosed within a header element. A better solution would be to eliminate the image and to enclose the text within a header element which has been styled using CSS.</p>
 
 <pre xml:space="preserve"><code class="language-html">&lt;img src="Chapter1.gif" alt="Chapter One"&gt;
-&lt;p&gt;Once upon a time in the land of the Web...&lt;/p&gt;</code></pre>
+&lt;p&gt;Once upon a time in the land of the web...&lt;/p&gt;</code></pre>
       </section>
 
    </section><section id="tests"><h2>Tests</h2>

techniques/failures/F33.html

@@ -26,10 +26,10 @@
 issues and recommendations for making     difficulties, cognitive limitations, limited 
 Web content more accessible. This         movement, speech difficulties, and 
 document contains principles,             others. Following these guidelines will 
-guidelines, Success Criteria, benefits,   also make your Web content more 
+guidelines, Success Criteria, benefits,   also make your web content more 
 and examples that define and explain      accessible to the vast majority of users, 
 the requirements for making Web-based     including older users. It will also enable
-information and applications accessible.  people to access Web content using 
+information and applications accessible.  people to access web content using 
 "Accessible" means usable to a wide       many different devices - including a 
 range of people with disabilities,        wide variety of assistive technologies.
 </pre>

techniques/failures/F43.html

@@ -57,7 +57,7 @@ <h3>Using <code class="language-html">blockquote</code> elements to provide addi
    the following common problem.&lt;/p&gt;
 
 &lt;blockquote&gt;
-  &lt;p&gt;The use of markup for presentational effects made Web 
+  &lt;p&gt;The use of markup for presentational effects made web 
    pages confusing to screen reader users.&lt;/p&gt;
 &lt;/blockquote&gt;
 

techniques/general/G10.html

@@ -8,7 +8,7 @@
       <p>Programming technologies that have standard components programmed to interface with accessibility APIs.</p>
    </section><section id="description"><h2>Description</h2>
       <p>The objective of this technique is to allow assistive technology to
-            understand Web content so that it can convey equivalent information to the
+            understand web content so that it can convey equivalent information to the
             user through an alternate user interface.</p>
       <p>Sometimes content is not created using markup language but rather using a
             programming language or tools. In many cases, these technologies have

techniques/general/G101.html

@@ -14,7 +14,7 @@
       <section class="example">
          <h3>A term used in a restricted way</h3>
 
-            <p>The word "technology" is widely used to cover everything from the stone tools used by early humans to contemporary digital devices such as cell phones.  But in WCAG 2.0, the word technology is used in a more restricted way:  it means a mechanism for encoding instructions to be rendered, played or executed by user agents, including  markup languages, data formats, and programming languages used in producing and delivering Web content.</p>
+            <p>The word "technology" is widely used to cover everything from the stone tools used by early humans to contemporary digital devices such as cell phones.  But in WCAG 2.0, the word technology is used in a more restricted way:  it means a mechanism for encoding instructions to be rendered, played or executed by user agents, including  markup languages, data formats, and programming languages used in producing and delivering web content.</p>
 
       </section>
       <section class="example">

techniques/general/G108.html

@@ -4,7 +4,7 @@
             changes.</p>
    </section><section id="description"><h2>Description</h2>
       <p>The objective of this technique is to allow assistive technology to
-            understand Web content so that it can convey equivalent information to the
+            understand web content so that it can convey equivalent information to the
             user through an alternate user interface and allow them to operate controls
             through the AT.</p>
       <p>This technique involves using standard, documented and supported features to

techniques/general/G115.html

@@ -16,7 +16,7 @@ <h2>When to Use</h2>
    </section>
 	 <section id="description">
 		<h2>Description</h2>
-		<p>The objective of this technique is to mark up the structure of the Web content using the appropriate semantic elements. In other words, the elements are used according to their meaning, not because of the way they appear visually.</p>
+		<p>The objective of this technique is to mark up the structure of the web content using the appropriate semantic elements. In other words, the elements are used according to their meaning, not because of the way they appear visually.</p>
 		<p>Using the appropriate semantic elements will make sure the structure is available to the user agent. This involves explicitly indicating the role that different units have in understanding the meaning of the content. The nature of a piece of content as a paragraph, header, emphasized text, table, etc. can all be indicated in this way. In some cases, the relationships between units of content should also be indicated, such as between headings and subheadings, or amongst the cells of a table. The user agent can then make the structure perceivable to the user, for example using a different visual presentation for different types of structures or by using a different voice or pitch in an auditory presentation.</p>
 		<p>In HTML, for example, phrase-level elements such as <code class="language-html">em</code>, <code class="language-html">abbr</code>, and <code class="language-html">cite</code> add semantic information within sentences, marking text for emphasis and identifying abbreviations and citations, respectively. MathML, a markup language designed to maintain important distinctions between structure and presentation in mathematics, includes special "presentation" markup for the complex notations used to represent mathematical ideas as well as "content" (semantic) markup for the mathematical ideas themselves.</p>
 	</section>