Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update input-purposes for syntax highlighting #3380

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update input-purposes for syntax highlighting #3380

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
108 changes: 54 additions & 54 deletions guidelines/input-purposes.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,64 +2,64 @@
<h2>Input Purposes for User Interface Components</h2>
<p>This section contains a listing of common <a>user interface component</a> input purposes. The terms below are not keywords that must be used, but instead represent purposes that must be captured in the taxonomy adopted by a webpage. Where applicable, authors mark up controls with the chosen taxonomy to indicate the semantic purpose. This provides the potential for user agents and assistive technologies to apply personalized presentations that can enable more people to understand and use the content.</p>

<p class="note">The list of input type purposes is based on the control purposes defined in the <a href="https://html.spec.whatwg.org/multipage/form-control-infrastructure.html#autofill">HTML specification's Autofill section</a>, but it is important to understand that a different technology may have some or all of the same concepts defined in its specification and only the concepts that are mapped to the meanings below are required.</p>
<p class="note">The list of input type purposes is based on the control purposes defined in the <a href="https://html.spec.whatwg.org/multipage/form-control-infrastructure.html#autofill"><abbr title="HyperText Markup Language">HTML</abbr> specification's Autofill section</a>, but it is important to understand that a different technology may have some or all of the same concepts defined in its specification and only the concepts that are mapped to the meanings below are required.</p>

<p>The following input control purposes are intended to relate to the user of the content and pertain only to information related to that individual.</p>

<ul>
<li><strong>name</strong> - Full name</li>
<li><strong>honorific-prefix</strong> - Prefix or title (e.g., "Mr.", "Ms.", "Dr.", "M<sup>lle</sup>")</li>
<li><strong>given-name</strong> - Given name (in some Western cultures, also known as the <i>first name</i>)</li>
<li><strong>additional-name</strong> - Additional names (in some Western cultures, also known as <i>middle names</i>, forenames other than the first name)</li>
<li><strong>family-name</strong> - Family name (in some Western cultures, also known as the <i>last name</i> or <i>surname</i>)</li>
<li><strong>honorific-suffix</strong> - Suffix (e.g., "Jr.", "B.Sc.", "MBASW", "II")</li>
<li><strong>nickname</strong> - Nickname, screen name, handle: a typically short name used instead of the full name</li>
<li><strong>organization-title</strong> - Job title (e.g., "Software Engineer", "Senior Vice President", "Deputy Managing Director")</li>
<li><strong>username</strong> - A username</li>
<li><strong>new-password</strong> - A new password (e.g., when creating an account or changing a password)</li>
<li><strong>current-password</strong> - The current password for the account identified by the <strong>username</strong> field (e.g., when logging in)</li>
<li><strong>organization</strong> - Company name corresponding to the person, address, or contact information in the other fields associated with this field</li>
<li><strong>street-address</strong> - Street address (multiple lines, newlines preserved)</li>
<li><strong>address-line1</strong> - Street address (one line per field, line 1)</li>
<li><strong>address-line2</strong> - Street address (one line per field, line 2)</li>
<li><strong>address-line3</strong> - Street address (one line per field, line 3)</li>
<li><strong>address-level4</strong> - The most fine-grained administrative level, in addresses with four administrative levels</li>
<li><strong>address-level3</strong> - The third administrative level, in addresses with three or more administrative levels</li>
<li><strong>address-level2</strong> - The second administrative level, in addresses with two or more administrative levels; in the countries with two administrative levels, this would typically be the city, town, village, or other locality within which the relevant street address is found</li>
<li><strong>address-level1</strong> - The broadest administrative level in the address, i.e., the province within which the locality is found; for example, in the US, this would be the state; in Switzerland it would be the canton; in the UK, the post town</li>
<li><strong>country</strong> - Country code</li>
<li><strong>country-name</strong> - Country name</li>
<li><strong>postal-code</strong> - Postal code, post code, ZIP code, CEDEX code (if CEDEX, append "CEDEX", and the <i lang="fr">dissement</i>, if relevant, to the <strong>address-level2</strong> field)</li>
<li><strong>cc-name</strong> - Full name as given on the payment instrument</li>
<li><strong>cc-given-name</strong> - Given name as given on the payment instrument (in some Western cultures, also known as the <i>first name</i>)</li>
<li><strong>cc-additional-name</strong> - Additional names given on the payment instrument (in some Western cultures, also known as <i>middle names</i>, forenames other than the first name)</li>
<li><strong>cc-family-name</strong> - Family name given on the payment instrument (in some Western cultures, also known as the <i>last name</i> or <i>surname</i>)</li>
<li><strong>cc-number</strong> - Code identifying the payment instrument (e.g., the credit card number)</li>
<li><strong>cc-exp</strong> - Expiration date of the payment instrument</li>
<li><strong>cc-exp-month</strong> - Month component of the expiration date of the payment instrument</li>
<li><strong>cc-exp-year</strong> - Year component of the expiration date of the payment instrument</li>
<li><strong>cc-csc</strong> - Security code for the payment instrument (also known as the card security code (CSC), card validation code (CVC), card verification value (CVV), signature panel code (SPC), credit card ID (CCID), etc)</li>
<li><strong>cc-type</strong> - Type of payment instrument</li>
<li><strong>transaction-currency</strong> - The currency that the user would prefer the transaction to use</li>
<li><strong>transaction-amount</strong> - The amount that the user would like for the transaction (e.g., when entering a bid or sale price)</li>
<li><strong>language</strong> - Preferred language</li>
<li><strong>bday</strong> - Birthday</li>
<li><strong>bday-day</strong> - Day component of birthday</li>
<li><strong>bday-month</strong> - Month component of birthday</li>
<li><strong>bday-year</strong> - Year component of birthday</li>
<li><strong>sex</strong> - Gender identity (e.g., Female, <span lang="sm">Fa’afafine</span>)</li>
<li><strong>url</strong> - Home page or other Web page corresponding to the company, person, address, or contact information in the other fields associated with this field</li>
<li><strong>photo</strong> - Photograph, icon, or other image corresponding to the company, person, address, or contact information in the other fields associated with this field</li>
<li><strong>tel</strong> - Full telephone number, including country code</li>
<li><strong>tel-country-code</strong> - Country code component of the telephone number</li>
<li><strong>tel-national</strong> - Telephone number without the country code component, with a country-internal prefix applied if applicable</li>
<li><strong>tel-area-code</strong> - Area code component of the telephone number, with a country-internal prefix applied if applicable</li>
<li><strong>tel-local</strong> - Telephone number without the country code and area code components</li>
<li><strong>tel-local-prefix</strong> - First part of the component of the telephone number that follows the area code, when that component is split into two components</li>
<li><strong>tel-local-suffix</strong> - Second part of the component of the telephone number that follows the area code, when that component is split into two components</li>
<li><strong>tel-extension</strong> - Telephone number internal extension code</li>
<li><strong>email</strong> - E-mail address</li>
<li><strong>impp</strong> - URL representing an instant messaging protocol endpoint (for example, "<strong>aim:goim?screenname=example</strong>" or "<strong>xmpp:fred@example.net</strong>")</li>
<li><code class="language-html">name</code> - Full name</li>
<li><code class="language-html">honorific-prefix</code> - Prefix or title (e.g., "Mr.", "Ms.", "Dr.", "M<sup>lle</sup>")</li>
<li><code class="language-html">given-name</code> - Given name (in some Western cultures, also known as the <i>first name</i>)</li>
<li><code class="language-html">additional-name</code> - Additional names (in some Western cultures, also known as <i>middle names</i>, forenames other than the first name)</li>
<li><code class="language-html">family-name</code> - Family name (in some Western cultures, also known as the <i>last name</i> or <i>surname</i>)</li>
<li><code class="language-html">honorific-suffix</code> - Suffix (e.g., "Jr.", "B.Sc.", "MBASW", "II")</li>
<li><code class="language-html">nickname</code> - Nickname, screen name, handle: a typically short name used instead of the full name</li>
<li><code class="language-html">organization-title</code> - Job title (e.g., "Software Engineer", "Senior Vice President", "Deputy Managing Director")</li>
<li><code class="language-html">username</code> - A username</li>
<li><code class="language-html">new-password</code> - A new password (e.g., when creating an account or changing a password)</li>
<li><code class="language-html">current-password</code> - The current password for the account identified by the <code class="language-html">username</code> field (e.g., when logging in)</li>
<li><code class="language-html">organization</code> - Company name corresponding to the person, address, or contact information in the other fields associated with this field</li>
<li><code class="language-html">street-address</code> - Street address (multiple lines, newlines preserved)</li>
<li><code class="language-html">address-line1</code> - Street address (one line per field, line 1)</li>
<li><code class="language-html">address-line2</code> - Street address (one line per field, line 2)</li>
<li><code class="language-html">address-line3</code> - Street address (one line per field, line 3)</li>
<li><code class="language-html">address-level4</code> - The most fine-grained administrative level, in addresses with four administrative levels</li>
<li><code class="language-html">address-level3</code> - The third administrative level, in addresses with three or more administrative levels</li>
<li><code class="language-html">address-level2</code> - The second administrative level, in addresses with two or more administrative levels; in the countries with two administrative levels, this would typically be the city, town, village, or other locality within which the relevant street address is found</li>
<li><code class="language-html">address-level1</code> - The broadest administrative level in the address, i.e., the province within which the locality is found; for example, in the US, this would be the state; in Switzerland it would be the canton; in the UK, the post town</li>
<li><code class="language-html">country</code> - Country code</li>
<li><code class="language-html">country-name</code> - Country name</li>
<li><code class="language-html">postal-code</code> - Postal code, post code, ZIP code, CEDEX code (if CEDEX, append "CEDEX", and the <i lang="fr">dissement</i>, if relevant, to the <code class="language-html">address-level2</code> field)</li>
<li><code class="language-html">cc-name</code> - Full name as given on the payment instrument</li>
<li><code class="language-html">cc-given-name</code> - Given name as given on the payment instrument (in some Western cultures, also known as the <i>first name</i>)</li>
<li><code class="language-html">cc-additional-name</code> - Additional names given on the payment instrument (in some Western cultures, also known as <i>middle names</i>, forenames other than the first name)</li>
<li><code class="language-html">cc-family-name</code> - Family name given on the payment instrument (in some Western cultures, also known as the <i>last name</i> or <i>surname</i>)</li>
<li><code class="language-html">cc-number</code> - Code identifying the payment instrument (e.g., the credit card number)</li>
<li><code class="language-html">cc-exp</code> - Expiration date of the payment instrument</li>
<li><code class="language-html">cc-exp-month</code> - Month component of the expiration date of the payment instrument</li>
<li><code class="language-html">cc-exp-year</code> - Year component of the expiration date of the payment instrument</li>
<li><code class="language-html">cc-csc</code> - Security code for the payment instrument (also known as the card security code (CSC), card validation code (CVC), card verification value (CVV), signature panel code (SPC), credit card ID (CCID), etc)</li>
<li><code class="language-html">cc-type</code> - Type of payment instrument</li>
<li><code class="language-html">transaction-currency</code> - The currency that the user would prefer the transaction to use</li>
<li><code class="language-html">transaction-amount</code> - The amount that the user would like for the transaction (e.g., when entering a bid or sale price)</li>
<li><code class="language-html">language</code> - Preferred language</li>
<li><code class="language-html">bday</code> - Birthday</li>
<li><code class="language-html">bday-day</code> - Day component of birthday</li>
<li><code class="language-html">bday-month</code> - Month component of birthday</li>
<li><code class="language-html">bday-year</code> - Year component of birthday</li>
<li><code class="language-html">sex</code> - Gender identity (e.g., Female, <span lang="sm">Fa’afafine</span>)</li>
<li><code class="language-html">url</code> - Home page or other Web page corresponding to the company, person, address, or contact information in the other fields associated with this field</li>
<li><code class="language-html">photo</code> - Photograph, icon, or other image corresponding to the company, person, address, or contact information in the other fields associated with this field</li>
<li><code class="language-html">tel</code> - Full telephone number, including country code</li>
<li><code class="language-html">tel-country-code</code> - Country code component of the telephone number</li>
<li><code class="language-html">tel-national</code> - Telephone number without the country code component, with a country-internal prefix applied if applicable</li>
<li><code class="language-html">tel-area-code</code> - Area code component of the telephone number, with a country-internal prefix applied if applicable</li>
<li><code class="language-html">tel-local</code> - Telephone number without the country code and area code components</li>
<li><code class="language-html">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 class="language-html">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 class="language-html">tel-extension</code> - Telephone number internal extension code</li>
<li><code class="language-html">email</code> - E-mail address</li>
<li><code class="language-html">impp</code> - <abbr title="Uniform Resource Locator">URL</abbr> representing an instant messaging protocol endpoint (for example, "<code class="language-html">aim:goim?screenname=example</code>" or "<code class="language-html">xmpp:fred@example.net</code>")</li>
</ul>

</section>