From 9367aa9955345409499f81ea0131d956542dbfd7 Mon Sep 17 00:00:00 2001 From: "Patrick H. Lauke" Date: Wed, 7 May 2025 23:23:52 +0100 Subject: [PATCH] Replace "e-mail" with "email" --- _includes/help-improve.html | 4 ++-- guidelines/input-purposes.html | 2 +- guidelines/terms/22/cognitive-function-test.html | 2 +- techniques/pdf/PDF15.html | 2 +- understanding/20/error-identification.html | 2 +- understanding/21/identify-input-purpose.html | 2 +- 6 files changed, 7 insertions(+), 7 deletions(-) diff --git a/_includes/help-improve.html b/_includes/help-improve.html index 340acedf69..70bf396f71 100644 --- a/_includes/help-improve.html +++ b/_includes/help-improve.html @@ -6,10 +6,10 @@

Help improve this page

-

Please share your ideas, suggestions, or comments via e-mail to the publicly-archived list public-agwg-comments@w3.org or via GitHub

+

Please share your ideas, suggestions, or comments via email to the publicly-archived list public-agwg-comments@w3.org or via GitHub

E-mail + class="button">Email Fork & Edit on GitHub New GitHub Issue
diff --git a/guidelines/input-purposes.html b/guidelines/input-purposes.html index 8c6baf14ad..2633fcd2d7 100644 --- a/guidelines/input-purposes.html +++ b/guidelines/input-purposes.html @@ -58,7 +58,7 @@

Input Purposes for User Interface Components

  • tel-local-prefix - First part of the component of the telephone number that follows the area code, when that component is split into two components
  • tel-local-suffix - Second part of the component of the telephone number that follows the area code, when that component is split into two components
  • tel-extension - Telephone number internal extension code
    • -
  • email - E-mail address
    • +
  • email - Email address
  • impp - URL representing an instant messaging protocol endpoint (for example, "aim:goim?screenname=example" or "xmpp:fred@example.net")
    • diff --git a/guidelines/terms/22/cognitive-function-test.html b/guidelines/terms/22/cognitive-function-test.html index e2674ea400..f248f380d3 100644 --- a/guidelines/terms/22/cognitive-function-test.html +++ b/guidelines/terms/22/cognitive-function-test.html @@ -3,7 +3,7 @@

    New

    A task that requires the user to remember, manipulate, or transcribe information. Examples include, but are not limited to:

    -
  • In the Add dialog, enter a URL to collect data on a server or collect form data as e-mail attachments.
    • +
  • In the Add dialog, enter a URL to collect data on a server or collect form data as email attachments.
    • diff --git a/understanding/20/error-identification.html b/understanding/20/error-identification.html index c365e8f300..0b2de0ed0a 100644 --- a/understanding/20/error-identification.html +++ b/understanding/20/error-identification.html @@ -103,7 +103,7 @@

    Examples of Error Identification

    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.

    diff --git a/understanding/21/identify-input-purpose.html b/understanding/21/identify-input-purpose.html index 81cf6387ec..de668082e9 100644 --- a/understanding/21/identify-input-purpose.html +++ b/understanding/21/identify-input-purpose.html @@ -23,7 +23,7 @@

    Intent of this Success Criterion

    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.

    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.

    -

    For some input fields, the type attribute already offers a way to broadly specify the intention of the input field, for example, <input type="tel">, <input type="email">, or <input type="password">. 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, type="email" 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.

    +

    For some input fields, the type attribute already offers a way to broadly specify the intention of the input field, for example, <input type="tel">, <input type="email">, or <input type="password">. 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, type="email" 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.

    This success criterion defines the types of user interface component input purposes, found in Section 7 of the WCAG 2.1 Recommendation, 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.

    The HTML autocomplete 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 (autocomplete="name"), Given Name (autocomplete="given-name"), Family Name (autocomplete="family-name"), as well as Username (autocomplete="username"), and Nickname (autocomplete="nickname").

    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 autocomplete="bday", or the icon of a telephone in front of an input field with autocomplete="tel".