Change "alternate" to "alternative"

guidelines/index.html

@@ -15,7 +15,7 @@
         <section id="abstract">
             <p>Web Content Accessibility Guidelines (WCAG) 2.2 covers a wide range of recommendations for making web content more accessible. Following these guidelines will make content more accessible to a wider range of people with disabilities, including accommodations for blindness and low vision, deafness and hearing loss, limited movement, speech disabilities, photosensitivity, and combinations of these, and some accommodation for learning disabilities and cognitive limitations; but will not address every user need for people with these disabilities. These guidelines address accessibility of web content on any kind of device (including desktops, laptops, kiosks, and mobile devices). Following these guidelines will also often make web content more usable to users in general.</p>
         	<p>WCAG 2.2 success criteria are written as testable statements that are not technology-specific. Guidance about satisfying the success criteria in specific technologies, as well as general information about interpreting the success criteria, is provided in separate documents. See <a href="https://www.w3.org/WAI/standards-guidelines/wcag/">Web Content Accessibility Guidelines (WCAG) Overview</a> for an introduction and links to WCAG technical and educational material.</p>
-            <p>WCAG 2.2 extends <a href="https://www.w3.org/TR/WCAG21/">Web Content Accessibility Guidelines 2.1</a> [[WCAG21]], which was published as a W3C Recommendation June 2018. Content that conforms to WCAG 2.2 also conforms to WCAG 2.0 and WCAG 2.1. The WG intends that for policies requiring conformance to WCAG 2.0 or WCAG 2.1, WCAG 2.2 can provide an alternate means of conformance. The publication of WCAG 2.2 does not deprecate or supersede WCAG 2.0 or WCAG 2.1. While WCAG 2.0 and WCAG 2.1 remain W3C Recommendations, the W3C advises the use of WCAG 2.2 to maximize future applicability of accessibility efforts. The W3C also encourages use of the most current version of WCAG when developing or updating web accessibility policies.</p>
+            <p>WCAG 2.2 extends <a href="https://www.w3.org/TR/WCAG21/">Web Content Accessibility Guidelines 2.1</a> [[WCAG21]], which was published as a W3C Recommendation June 2018. Content that conforms to WCAG 2.2 also conforms to WCAG 2.0 and WCAG 2.1. The WG intends that for policies requiring conformance to WCAG 2.0 or WCAG 2.1, WCAG 2.2 can provide an alternative means of conformance. The publication of WCAG 2.2 does not deprecate or supersede WCAG 2.0 or WCAG 2.1. While WCAG 2.0 and WCAG 2.1 remain W3C Recommendations, the W3C advises the use of WCAG 2.2 to maximize future applicability of accessibility efforts. The W3C also encourages use of the most current version of WCAG when developing or updating web accessibility policies.</p>
         </section>
         <section id="sotd">
           <p>To comment, <a href="https://github.com/w3c/wcag/issues/new">file an issue in the

guidelines/terms/20/assistive-technology.html

@@ -50,7 +50,7 @@
       <li>speech recognition software, which may be used by people who have some physical disabilities;</li>
 
       <li>alternative keyboards, which are used by people with certain physical disabilities
-         to simulate the keyboard (including alternate keyboards that use head pointers, single
+         to simulate the keyboard (including alternative keyboards that use head pointers, single
          switches, sip/puff and other special input devices.);
       </li>
 

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

@@ -38,25 +38,25 @@
       page unless the user had just come from the conforming version.
    </p>
 
-   <p class="note">The alternate version does not need to be matched page for page with the original
+   <p class="note">The alternative version does not need to be matched page for page with the original
       (e.g., the conforming alternate version may consist of multiple pages).
    </p>
 
    <p class="note">If multiple language versions are available, then conforming alternate versions are
       required for each language offered.
    </p>
 
-   <p class="note">Alternate versions may be provided to accommodate different technology environments
+   <p class="note">Alternative versions may be provided to accommodate different technology environments
       or user groups. Each version should be as conformant as possible. One version would
       need to be fully conformant in order to meet <a href="#cc1">conformance requirement 1</a>.
    </p>
 
-   <p class="note">The conforming alternative version does not need to reside within the scope of conformance,
+   <p class="note">The conforming alternate version does not need to reside within the scope of conformance,
       or even on the same website, as long as it is as freely available as the non-conforming
       version.
    </p>
 
-   <p class="note">Alternate versions should not be confused with <a>supplementary content</a>, which support the original page and enhance comprehension.
+   <p class="note">Alternative versions should not be confused with <a>supplementary content</a>, which support the original page and enhance comprehension.
    </p>
 
    <p class="note">Setting user preferences within the content to produce a conforming version is an

guidelines/terms/20/media-alternative-for-text.html

@@ -5,7 +5,7 @@
       or via text alternatives)
    </p>
 
-   <p class="note">A media alternative for text is provided for those who benefit from alternate representations
+   <p class="note">A media alternative for text is provided for those who benefit from alternative representations
       of text. Media alternatives for text may be audio-only, video-only (including sign-language
       video), or audio-video.
    </p>

techniques/client-side-script/SCR38.html

@@ -18,10 +18,10 @@ <h2>Description</h2>
 			<p>This objective of this technique is to offer a conforming alternate version for a web page designed with progressive enhancement. The technique demonstrates how to use a scripting technique to accomplish this by:</p>
       <ol>
          <li>Storing the initial pre-enhanced version of the web page so that it can act as a "conforming alternate version" for any later enhanced versions of the content; and</li>
-         <li>Inserting a mechanism into all enhanced versions of the web page which allows a user to revert the content back to the stored pre-enhanced Alternate Version.</li>
+         <li>Inserting a mechanism into all enhanced versions of the web page which allows a user to revert the content back to the stored pre-enhanced Alternative Version.</li>
       </ol>
 			<p>Web pages designed with progressive enhancement detect features in the web-enabled accessing device (size, capability and software) to allow those supported web technologies to be applied in layers on top of an HTML foundation. The basic content and functionality of such a web page are available through the HTML foundation to anyone using a more simple web-enabled accessing device, whilst enhanced versions of the page are created to suit the different features in more advanced accessing devices.</p>
-			<p>The current guidance for web pages delivered in alternate versions reads: "Note 4: Alternate versions may be provided to accommodate different technology environments or user groups. Each version should be as conformant as possible. One version would need to be fully conformant in order to meet conformance requirement 1." With regard to web pages designed with progressive enhancement this leaves the problem of which version to select as the one fully conformant version - all whilst trying to ensure that no set of users is disadvantaged by that choice.</p>
+			<p>The current guidance for web pages delivered in alternative versions reads: "Note 4: Alternative versions may be provided to accommodate different technology environments or user groups. Each version should be as conformant as possible. One version would need to be fully conformant in order to meet conformance requirement 1." With regard to web pages designed with progressive enhancement this leaves the problem of which version to select as the one fully conformant version - all whilst trying to ensure that no set of users is disadvantaged by that choice.</p>
 			<p>One solution to this challenge is to select the pre-enhanced version of the web page (e.g. the DOM state created solely from the HTML in the source code in the absence of support for scripts, styles or non-HTML plugins) as the "fully conformant version", due to its broad reach, with regard to support, across all the possible web-enabled devices accessing the content.</p>
 			<div class="note"><p>This technique removes all scripts, styles, and plugins, but it is important to state that this is not required for conformance with WCAG 2.x. An author could use a similar technique, but retain a reduced set of styles and scripts in the "pre-enhanced" version.</p></div>
 			<p>While this technique offers a way to base conformance claims on a single version, authors should continue to work to ensure that each enhanced version of the web page is as conformant as possible.</p>
@@ -122,7 +122,7 @@ <h2>Tests</h2>
 			<h3>Procedure</h3>
 			<ol>
 				<li>Check enhanced versions of the web page contain a link to the "Conforming Alternate Version".</li>
-				<li>Check that the alternate version is a <a>conforming alternate version</a> of the original page and that it conforms to WCAG 2.0 at the claimed conformance level.</li>
+				<li>Check that the alternative version is a <a>conforming alternate version</a> of the original page and that it conforms to WCAG 2.0 at the claimed conformance level.</li>
 			</ol>
     </section>
     <section class="results">

techniques/css/C29.html

@@ -16,7 +16,7 @@ <h2>When to Use</h2>
 	</section>
 	<section id="description">
 		<h2>Description</h2>
-		<p>When some aspect of the default presentation of a web page does not meet a Success Criterion, it is possible to meet that requirement using the "Alternate Version" clause in the conformance requirements (Conformance Requirement 1). For some requirements, invoking a style switcher via a link or control on the page that can adjust the presentation so that all aspects of the page conform at the level claimed allows authors to avoid having to provide multiple versions of the same information.</p>
+		<p>When some aspect of the default presentation of a web page does not meet a Success Criterion, it is possible to meet that requirement using the "Alternative Version" clause in the conformance requirements (Conformance Requirement 1). For some requirements, invoking a style switcher via a link or control on the page that can adjust the presentation so that all aspects of the page conform at the level claimed allows authors to avoid having to provide multiple versions of the same information.</p>
 		<p>The objective of this technique is to demonstrate how CSS can be used in combination with scripting to provide conforming alternate versions of a web page. In this technique, an author provides alternative views of the content by providing controls that adjust the CSS that is used to control the visual presentation of content. Controls provided within the web page allow users to select or modify the presentation in a way that meets the success criterion at the level claimed. This makes it possible for different visual presentations to be selected by users in situations such as the following:</p>
 		<ul>
 			<li>the user may not be able to adjust browser or operating system settings, due to a lack of familiarity or rights</li>
@@ -25,9 +25,9 @@ <h2>Description</h2>
 		</ul>
 		<p>For this technique to be used successfully, three things must be true.</p>
 		<ol>
-			<li>The link or control on the original page must itself meet the success criterion to be met via the alternate presentation. For example, if a style switcher is used to provide increased font sizes and the control is presented using a small font, users may not be able to activate the control and view the alternate presentation.</li>
+			<li>The link or control on the original page must itself meet the success criterion to be met via the alternative presentation. For example, if a style switcher is used to provide increased font sizes and the control is presented using a small font, users may not be able to activate the control and view the alternative presentation.</li>
 			<li>The new page must contain all the same information and functionality as the original page.</li>
-			<li>The new page must conform to all of the success criteria for the desired level of conformance. For example, an alternate stylesheet can not be used to meet one requirement if it causes a different requirement to no longer conform.</li>
+			<li>The new page must conform to all of the success criteria for the desired level of conformance. For example, an alternative stylesheet can not be used to meet one requirement if it causes a different requirement to no longer conform.</li>
 		</ol>
 		<p>When using a style switcher, it is important to consider the following challenges and limitations:</p>
 		<ul>
@@ -333,8 +333,8 @@ <h2>Tests</h2>
 		<section class="procedure">
 			<h3>Procedure</h3>
 			<ol>
-				<li>Check that the web page contains controls that allow users to select alternate presentations. </li>
-				<li>Check that the control changes the presentation by modifying individual CSS style properties or by activating an alternate style sheet.</li>
+				<li>Check that the web page contains controls that allow users to select alternative presentations. </li>
+				<li>Check that the control changes the presentation by modifying individual CSS style properties or by activating an alternative style sheet.</li>
 				<li>Verify that the resulting page is a conforming alternate version for the original page. </li>
 			</ol>
 		</section>

techniques/css/C30.html

@@ -18,7 +18,7 @@ <h2>When to Use</h2>
 		<section id="description">
 			<h2>Description</h2>
       <p>The objective of this technique is to demonstrate how CSS can be used to replace structured <abbr title="HyperText Markup Language">HTML</abbr> text with images of text in a way that makes it possible for users to view content according to their preferences. To use this technique, an author starts by creating an HTML page that uses semantic elements to mark up the structure of the page. The author then designs two or more stylesheets for that page. One stylesheet presents the HTML text as text and the second uses CSS features to replace some of the HTML text with images of text. Finally, through the use of server-side or client-side scripting, the author provides a control that allows the user to switch between the available views.</p>
-      <p>This technique can be used to meet Success Criterion 1.4.5 or 1.4.9 if a presentation that does not include images of text is available and as long as the user interface control that is provided to allow users to switch to an alternate presentation meets the relevant criteria. Where possible, authors should deliver the presentation that does not include images of text as the default presentation. In addition, the control used to switch should be located near the beginning of the page.</p>
+      <p>This technique can be used to meet Success Criterion 1.4.5 or 1.4.9 if a presentation that does not include images of text is available and as long as the user interface control that is provided to allow users to switch to an alternative presentation meets the relevant criteria. Where possible, authors should deliver the presentation that does not include images of text as the default presentation. In addition, the control used to switch should be located near the beginning of the page.</p>
       <p>A variety of "image replacement" techniques have been developed to address a variety of user agent, configuration and compatibility with assistive technology issues (See resources for more information). While there are a variety of approaches authors may use to replace text, it is important to consider compatibility with assistive technology, whether the technique will work correctly if scripting, CSS, images (or combinations of these) are turned off. Since it can be difficult to find a single solution that works in all cases, this technique recommends the use of a control that allows users to switch to a presentation that does not include an image replacement technique.</p>
       <div class="note">
 				<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="C29">C29</a> and <a href="../../Understanding/conformance#conforming-alt-versions">Understanding Conforming Alternate Versions</a> for more information.</p>
@@ -92,7 +92,7 @@ <h2>Tests</h2>
       <section class="procedure">
 				<h3>Procedure</h3>
 				<ol>
-					<li>Check that the web page includes a control that allows users to select an alternate presentation.</li>
+					<li>Check that the web page includes a control that allows users to select an alternative presentation.</li>
 					<li>Check that when the control is activated the resulting page includes text (programmatically determined text) wherever images of text had been used.</li>
          </ol>
       </section>

techniques/failures/F19.html

@@ -2,12 +2,12 @@
       <p> Sites that provide alternative, WCAG-conforming versions of nonconforming
                         primary content.</p>
    </section><section id="description"><h2>Description</h2>
-      <p> This failure technique describes the situation in which an alternate, conforming version of the content is provided, but there is no direct way for a user to tell that it is available or where to find it. Such content fails the success criterion because the user cannot find the conforming version.</p>
+      <p> This failure technique describes the situation in which an alternative, conforming version of the content is provided, but there is no direct way for a user to tell that it is available or where to find it. Such content fails the success criterion because the user cannot find the conforming version.</p>
    </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 website. There is neither an indication that an
-                                alternate page is available, nor a path to the alternate page from
+                                alternative page is available, nor a path to the alternative page from
                                 the nonconforming page. </li>
          <li> Nonconforming pages on the website inform the user that a
                                 conforming version is available and provide a link to the home page.

techniques/failures/F3.html

@@ -11,7 +11,7 @@
                         convey important information. Therefore, it is a failure to use this
                         property to add images to convey important information. This failure would apply equally in a case where the background image was declared in the HTML style attribute, as well as in a case where the background image declaration was created dynamically in a client script (see example 3 below).</p>
       <div class="note">
-         <p>Embedding information into a background image can also cause problems for people who use alternate backgrounds in order to increase legibility and for users of high contrast mode in some operating systems. These users, would lose the information in the background image due to lack of any alternative text.</p>
+         <p>Embedding information into a background image can also cause problems for people who use alternative backgrounds in order to increase legibility and for users of high contrast mode in some operating systems. These users, would lose the information in the background image due to lack of any alternative text.</p>
       </div>
    </section><section id="examples"><h2>Examples</h2>
       <section class="example">