Style updates

conformance-challenges/index.html

@@ -95,7 +95,7 @@ <h3>Problem Statement</h3>
 algorithms and code happen multiple times per week). It is incumbent on websites - especially for large, complex, dynamic websites - to do everything they can to conform. However, to date, no large, complex software has been bug free.  Similarly, authors of large, dynamic, and complex sites have struggled to claim conformance with no accessibility defects on any page.
 		    </p>
 
-		    <p>Assessing conformance of such large, highly complex, dynamic sites to the <a href="https://www.w3.org/TR/WCAG20/">Web Content Accessibility Guidelines (WCAG) 2.0</a> [[wcag20]] or <a href="https://www.w3.org/TR/WCAG21/">2.1</a> [[wcag21]] has proved difficult. The <a href="https://www.w3.org/TR/WCAG20/#conformance">Web Content Accessibility Guidelines 2.0 include a set of normative requirements</a> <q>in order for a web page to conform to WCAG 2.0,</q> including that conformance <q>is for full Web page(s) only, and cannot be achieved if part of a Web page is excluded,</q> along with a Note that states <q>If a page cannot conform (for example, a conformance test page or an example page), it cannot be included in the scope of conformance or in a conformance claim.</q> The conformance requirements also state what is allowed in any optional <q>Conformance Claims,</q> starting with: <q>Conformance is defined only for  <a href="https://www.w3.org/TR/WCAG20/#webpagedef">Web pages</a>. However, a conformance claim may be made to cover one page, a series of pages, or multiple related Web pages.</q>  For the purposes of this document, we use the term <q>WCAG 2.x conformance model</q> to refer to the normative text in the <a href="https://www.w3.org/TR/WCAG20/#conformance">Conformance section</a> of WCAG 2.0 and WCAG 2.1.
+		    <p>Assessing conformance of such large, highly complex, dynamic sites to the <a href="https://www.w3.org/TR/WCAG20/">Web Content Accessibility Guidelines (WCAG) 2.0</a> [[wcag20]] or <a href="https://www.w3.org/TR/WCAG21/">2.1</a> [[wcag21]] has proved difficult. The <a href="https://www.w3.org/TR/WCAG20/#conformance">Web Content Accessibility Guidelines 2.0 include a set of normative requirements</a> <q>in order for a web page to conform to WCAG 2.0,</q> including that conformance <q>is for full web page(s) only, and cannot be achieved if part of a web page is excluded,</q> along with a Note that states <q>If a page cannot conform (for example, a conformance test page or an example page), it cannot be included in the scope of conformance or in a conformance claim.</q> The conformance requirements also state what is allowed in any optional <q>Conformance Claims,</q> starting with: <q>Conformance is defined only for  <a href="https://www.w3.org/TR/WCAG20/#webpagedef">web pages</a>. However, a conformance claim may be made to cover one page, a series of pages, or multiple related web pages.</q>  For the purposes of this document, we use the term <q>WCAG 2.x conformance model</q> to refer to the normative text in the <a href="https://www.w3.org/TR/WCAG20/#conformance">Conformance section</a> of WCAG 2.0 and WCAG 2.1.
 		    </p>
 
 <p>This WCAG 2.x conformance model contains a mitigation related to partial conformance for 3rd party content (see <a href="#Challenge-3.1">Sec. 3.1: Treatment of 3rd party content and Statements of Partial Conformance</a> below). Further in recognition of these challenges, the W3C Note <a href="http://www.w3.org/tr/wcag-em/">Website Accessibility Conformance Evaluation Methodology (WCAG-EM) 1.0</a> [[wcag-em]] was published in 2014 to provide <q>guidance on evaluating how well websites conform to the Web Content Accessibility Guidelines.</q> This W3C document <q>describes a procedure to evaluate websites and includes considerations to guide evaluators and to promote good practice,</q> which can help organizations to make a conformance claim, while acknowledging that there may be errors on pages not in the sample set or that were not picked up by automated evaluation tools on pages that were not in the human evaluation sample. While WCAG-EM provides a practical method for claiming conformance for a website, it doesn&apos;t fully address the challenges in making every part of every page in a large, dynamic website conform to every success criterion.
@@ -211,7 +211,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.</p>
 
@@ -291,7 +291,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>
@@ -462,7 +462,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>
@@ -1159,7 +1159,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>

techniques/aria/ARIA8.html

@@ -1,7 +1,7 @@
 <!DOCTYPE html><html lang="en" xml:lang="en" xmlns="http://www.w3.org/1999/xhtml"><head><title>Using aria-label for link purpose</title><link rel="stylesheet" type="text/css" href="../../css/editors.css" class="remove"/></head><body><h1>Using aria-label for link purpose</h1><section class="meta"><p class="id">ID: ARIA8</p><p class="technology">Technology: aria</p><p class="type">Type: Technique</p></section><section id="applicability"><h2>When to Use</h2>
       <p>Technologies that support <a href="https://www.w3.org/TR/wai-aria/">Accessible Rich Internet Applications (WAI-ARIA)</a>. </p>
    </section><section id="description"><h2>Description</h2>
-      <p>The objective of this technique is to describe the purpose of a link using the <code class="language-html">aria-label</code> attribute. The <code class="language-html">aria-label</code> attribute provides a way to place a descriptive text label on an object, such as a link, when there are no elements visible on the page that describe the object. If descriptive elements are visible on the page, the <code class="language-html">aria-labelledby</code> attribute should be used instead of <code class="language-html">aria-label</code>. Providing a descriptive text label lets a user distinguish the link from links in the Web page that lead to other destinations and helps the user determine whether to follow the link. In some assistive technologies the <code class="language-html">aria-label</code> value will show in the list of links instead of the actual link text.</p>
+      <p>The objective of this technique is to describe the purpose of a link using the <code class="language-html">aria-label</code> attribute. The <code class="language-html">aria-label</code> attribute provides a way to place a descriptive text label on an object, such as a link, when there are no elements visible on the page that describe the object. If descriptive elements are visible on the page, the <code class="language-html">aria-labelledby</code> attribute should be used instead of <code class="language-html">aria-label</code>. Providing a descriptive text label lets a user distinguish the link from links in the web page that lead to other destinations and helps the user determine whether to follow the link. In some assistive technologies the <code class="language-html">aria-label</code> value will show in the list of links instead of the actual link text.</p>
       <p>Per the <a href="https://www.w3.org/TR/accname/">Accessible Name and Description Computation</a> and the <a href="https://www.w3.org/TR/html-aam-1.0/#accessible-name-and-description-computation">Accessible Name and Description Computation</a> in the HTML Accessibility API Mappings 1.0, the <code class="language-html">aria-label</code> text will override the text supplied within the link. As such the text supplied will be used instead of the link text by assistive technology. Due to this it is recommended to start the text used in <code class="language-html">aria-label</code> with the text used within the link. This will allow consistent communication between users.</p>
    </section><section id="examples"><h2>Examples</h2>
       <section class="example">

techniques/client-side-script/SCR1.html

@@ -22,7 +22,7 @@ <h2>Description</h2>
 	 <section id="examples">
 		<h2>Examples</h2>
 		<ul>
-			<li>A Web page contains current stock market statistics and is set to refresh periodically. When the user is warned prior to refreshing the first time, the user is provided with an option to extend the time period between refreshes.</li>
+			<li>A web page contains current stock market statistics and is set to refresh periodically. When the user is warned prior to refreshing the first time, the user is provided with an option to extend the time period between refreshes.</li>
 			<li>In an online chess game, each player is given a time limit for completing each move. When the player is warned that time is almost up for this move, the user is provided with an option to increase the time.</li>
 		</ul>
 	</section>
@@ -31,7 +31,7 @@ <h2>Tests</h2>
 		<section class="procedure">
 			<h3>Procedure</h3>
 			<ol>
-				<li>On a Web page that uses scripts to enforce a time limit, wait until the time limit has expired.</li>
+				<li>On a web page that uses scripts to enforce a time limit, wait until the time limit has expired.</li>
 				<li>Determine if an option was provided to extend the time limit.</li>
 			</ol>
 		</section>

techniques/client-side-script/SCR14.html

@@ -88,16 +88,16 @@ <h4>The <abbr title="HyperText Markup Language">HTML</abbr></h4>
       </section>
    </section><section id="tests"><h2>Tests</h2>
       <section class="procedure"><h3>Procedure</h3>
-         <p>For a Web page that supports non-emergency interruptions:</p>
+         <p>For a web page that supports non-emergency interruptions:</p>
          <ol>
-            <li>Load the Web page and verify that no non-emergency alerts are displayed.</li>
+            <li>Load the web page and verify that no non-emergency alerts are displayed.</li>
             <li>Verify there is a mechanism to activate and deactivate the non-emergency interruptions.</li>
          </ol>
       </section>
       <section class="results">
 				<h3>Expected Results</h3>
          <ul>
-            <li>For a Web page that supports non-emergency interruptions, checks #1 and #2 are true.</li>
+            <li>For a web page that supports non-emergency interruptions, checks #1 and #2 are true.</li>
          </ul>
       </section>
    </section>

techniques/client-side-script/SCR16.html

@@ -66,7 +66,7 @@ <h2>Examples</h2>
    <section id="tests">
       <h2>Tests</h2>
       <section class="procedure"><h3>Procedure</h3>
-         <p>On a Web page that has a time limit controlled by a script:</p>
+         <p>On a web page that has a time limit controlled by a script:</p>
          <ol>
             <li>Load the page and start a timer that is 20 seconds less than the time limit.</li>
             <li>When the timer expires, check that a confirmation dialog is displayed warning of the impending time limit.</li>