Replace archaic-looking "e-mail" with "email" (#4385)

Noticed this as part of #4384 but then
found a few more occurrences.

The predominant use across all documents is "email" (not hyphenated),
but there are a few stragglers that use "e-mail".
Strangely, this is not covered in
https://www.w3.org/guide/manual-of-style/ but in various places across
W3C the non-hyphenated version is used.

Note: this PR contains changes to both normative and non-normative
documents

Co-authored-by: Mike Gower <[email protected]>

Author: patrickhlauke

_includes/help-improve.html

@@ -6,10 +6,10 @@
     <h2> Help improve this page </h2>
   </header>
   <div class="box-i">
-  <p>Please share your ideas, suggestions, or comments via e-mail to the publicly-archived list <a href="mailto:[email protected]?subject=%5BUnderstanding%20and%20Techniques%20Feedback%5D">[email protected]</a> or via GitHub</p>
+  <p>Please share your ideas, suggestions, or comments via email to the publicly-archived list <a href="mailto:[email protected]?subject=%5BUnderstanding%20and%20Techniques%20Feedback%5D">[email protected]</a> or via GitHub</p>
     <div class="button-group">
       <a href="mailto:[email protected]?subject=%5BUnderstanding%20and%20Techniques%20Feedback%5D"
-        class="button"><span>E-mail</span></a>
+        class="button"><span>Email</span></a>
       <a href="https://github.com/w3c/wcag/issues/" class="button"><span>Fork &amp; Edit on GitHub</span></a>
       <a href="https://github.com/w3c/wcag/issues/new" class="button"><span>New GitHub Issue</span></a>
     </div>

guidelines/input-purposes.html

@@ -58,7 +58,7 @@ <h2>Input Purposes for User Interface Components</h2>
 		<li><code>tel-local-prefix</code> - First part of the component of the telephone number that follows the area code, when that component is split into two components</li>
 		<li><code>tel-local-suffix</code> - Second part of the component of the telephone number that follows the area code, when that component is split into two components</li>
 		<li><code>tel-extension</code> - Telephone number internal extension code</li>
-		<li><code>email</code> - E-mail address</li>
+		<li><code>email</code> - Email address</li>
 		<li><code>impp</code> - <abbr title="Uniform Resource Locator">URL</abbr> representing an instant messaging protocol endpoint (for example, "<code>aim:goim?screenname=example</code>" or "<code>xmpp:[email protected]</code>")</li>
 	</ul>
 

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

@@ -3,7 +3,7 @@
     <p class="change">New</p>
     <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 websites;</li>
+        <li>memorization, such as remembering a username, password, set of characters, images, or patterns. The common identifiers name, email, 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>

techniques/pdf/PDF15.html

@@ -38,7 +38,7 @@ <h3>Adding a submit button using Adobe Acrobat Pro</h3>
               <li>Click Add.</li>
           	</ul>
           </li>
-          <li>In the Add dialog, enter a <abbr title="Uniform Resource Locator">URL</abbr> to collect data on a server or collect form data as e-mail attachments.</li>
+          <li>In the Add dialog, enter a <abbr title="Uniform Resource Locator">URL</abbr> to collect data on a server or collect form data as email attachments.</li>
         </ol>
 			</section>
 			<section class="example">

understanding/20/error-identification.html

@@ -103,7 +103,7 @@ <h2>Examples of Error Identification</h2>
          <dd>
             <p>An airline website offers a special promotion on discounted flights. The user is
                asked to complete a simple form that asks for personal information such as name, address,
-               phone number, seating preference and e-mail address. If any of the fields of the form
+               phone number, seating preference and email address. If any of the fields of the form
                are either not completed or completed incorrectly, an alert is displayed notifying
                the user which field or fields were missing or incorrect.</p>
 

understanding/21/identify-input-purpose.html

@@ -22,7 +22,7 @@ <h2>Intent of this Success Criterion</h2>
 
   <p>The intent of this success criterion is to ensure that the purpose of a form input collecting information about the user can be programmatically determined, so that user agents can extract and present this purpose to users using different modalities. The ability to programmatically declare the specific kind of data expected in a particular field makes filling out forms easier, especially for people with certain cognitive disabilities.</p>
   <p>Appropriate visible labels and instruction can help users understand the purpose of form input fields, but users may benefit from having fields that collect specific types of information be rendered in an unambiguous, consistent, and possibly customized way for different modalities - either through defaults in their user agent, or through the aid of assistive technologies.</p>
-  <p>For some input fields, the <code>type</code> attribute already offers a way to broadly specify the intention of the input field, for example, <code>&lt;input type="tel"&gt;</code>, <code>&lt;input type="email"&gt;</code>, or <code>&lt;input type="password"&gt;</code>. However, these are only very broad categories, describing the type of input, but not necessarily its purpose, especially as it relates to user-specific input fields. As an example, <code>type="email"</code> indicates that the field is for an e-mail address but does not clarify if the purpose is for entering the user's e-mail address or some other person's e-mail.</p>
+  <p>For some input fields, the <code>type</code> attribute already offers a way to broadly specify the intention of the input field, for example, <code>&lt;input type="tel"&gt;</code>, <code>&lt;input type="email"&gt;</code>, or <code>&lt;input type="password"&gt;</code>. However, these are only very broad categories, describing the type of input, but not necessarily its purpose, especially as it relates to user-specific input fields. As an example, <code>type="email"</code> indicates that the field is for an email address but does not clarify if the purpose is for entering the user's email address or some other person's email.</p>
   <p>This success criterion defines the types of user interface component input purposes, found in <a href="https://www.w3.org/TR/WCAG21/#input-purposes">Section 7 of the WCAG 2.1 Recommendation</a>, that must be programmatically identifiable. When these user input purposes are present, and if the technology supports doing so, the field purpose must be programmatically identifiable.</p>
   <p>The HTML <code>autocomplete</code> attribute only accepts a certain number of specific well-defined fixed values. This allows a more fine-grained definition or identification of purpose than the type attribute, for example, by allowing the author to specify a specific type of name: Name (<code>autocomplete="name"</code>), Given Name (<code>autocomplete="given-name"</code>), Family Name (<code>autocomplete="family-name"</code>), as well as Username (<code>autocomplete="username"</code>), and Nickname (<code>autocomplete="nickname"</code>).</p>
   <p>By adopting and repurposing this predefined taxonomy of definitions, user agents and assistive technologies can now present the purpose of the inputs to users in different modalities. For example, assistive technologies may display familiar icons next to input fields to help users who have difficulties reading. An icon of a birthday cake may be shown in front of an input field with <code>autocomplete="bday"</code>, or the icon of a telephone in front of an input field with <code>autocomplete="tel"</code>.</p>