Exclude conformance-challenges/ and requirements/

Author: patrickhlauke

conformance-challenges/index.html

@@ -407,16 +407,16 @@ Challenge #5: Accessibility Supported
 		<a href="https://www.w3.org/TR/UNDERSTANDING-WCAG20/conformance.html#uc-accessibility-supported-definition-head">
 			 first Note under the definition of Accessibility Supporteda> 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 @@ Mitigations
 
 		<p>We know of no useable mitigations to achieve the <q>Accessibility Supportedq> conformance requirement for public facing websites. <a href="https://www.w3.org/TR/WCAG-EM/#step1c">WCAG-EM's Second Notea> 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.0a> 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. … 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.0a> 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. … 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>

requirements/21/index.html

@@ -113,7 +113,7 @@
 <section id="introduction">
 	<h2>Introductionh2>
 	<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>Introductionh2>
     <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>