This is an unpublished draft preview that might include content that is not yet approved. The published website is at w3.org/WAI/.

Form field has non-empty accessible name

Rule Type:
atomic
Rule ID:
e086e5
Last Modified:
Oct 1, 2020
Accessibility Requirements Mapping:
4.1.2 Name, Role, Value (Level A)
  • Required for conformance to WCAG 2.0 and later on level A and higher
  • Outcome mapping:
    • Any failed outcomes: success criterion is not satisfied
    • All passed outcomes: success criterion needs further testing
    • An inapplicable outcome: success criterion needs further testing
Input Aspects:
Accessibility Tree
CSS styling
DOM Tree

Description

This rule checks that each form field element has a non-empty accessible name.

Applicability

This rule applies to any element that is included in the accessibility tree, and that has one of the following [semantic roles][]: checkbox, combobox (select elements), listbox, menuitemcheckbox, menuitemradio, radio, searchbox, slider, spinbutton, switch, textbox.

Expectation

Each target element has an accessible name that is not empty ("").

Assumptions

There are currently no assumptions

Accessibility Support

Background

The list of roles in the applicability is derived by taking all the roles from WAI-ARIA Specifications that:

Note that this rule does not test other control-like roles such as button and menuitem, because these do not inherit from input or select. These should be tested separately.

This rule does not map to 3.3.2 Labels or Instructions as there are sufficient techniques within 3.3.2 that don’t need the elements to have an accessible name. For example “G131: Providing descriptive labels” AND “G162: Positioning labels to maximize predictability of relationships” would be sufficient.

Test Cases

Passed

Passed Example 1

This input element has an accessible name because of its programmatic label.

<label>
	first name
	<input />
</label>

Passed Example 2

This input element has an accessible name because of its aria-label attribute.

<div>last name</div>
<input aria-label="last name" disabled />

Passed Example 3

This select element has an accessible name because of its programmatic label.

<label for="country">Country</label>
<select id="country">
	<option>England</option>
	<option>Scotland</option>
	<option>Wales</option>
	<option>Northern Ireland</option>
</select>

Passed Example 4

This textarea element has an accessible name because of its aria-labelledby attribute.

<div id="country">Country</div>
<textarea aria-labelledby="country"></textarea>

Passed Example 5

This input element has an accessible name because of its placeholder attribute.

Note: While the placeholder attribute is sufficient to provide an accessible name, a [visible][] [label][] that does not disappear when a users starts to enter data is still required for [success criterion 3.3.2 Labels or Instructions][sc332].

<input placeholder="Your search query" /> <button type="submit">search</button>

Passed Example 6

This element with a combobox [role][semantic role] has an accessible name because of its aria-label attribute.

<div>Country</div>
<div aria-label="country" role="combobox" aria-disabled="true">England</div>

Failed

Failed Example 1

This input element does not have an attribute that gives an accessible name to it.

<div>last name</div>
<input />

Failed Example 2

This disabled input element does not have an attribute that gives an accessible name to it.

<input disabled />

Failed Example 3

This input element has an empty ("") accessible name because the space in the aria-label attribute value is trimmed.

<input aria-label=" " />

Failed Example 4

This select element has an empty ("") accessible name because the div has no text content.

<div id="country"></div>
<select aria-labelledby="country">
	<option>England</option>
</select>

Failed Example 5

This element with a textbox [role][semantic role] has an empty ("") accessible name. The parent label element does not give it an accessible name, this only works for native form fields.

<label>
	first name
	<div role="textbox"></div>
</label>

Failed Example 6

This element with a textbox [role][semantic role] has an empty ("") accessible name. The label element does not give it an accessible name, this only works for native form fields.

<label for="lastname">first name</label>
<div role="textbox" id="lastname"></div>

Inapplicable

Inapplicable Example 1

This input element is not included in the accessibility tree because of its style attribute which sets display to none.

<input aria-label="firstname" style="display:none;" />

Inapplicable Example 2

This input element is not included in the accessibility tree because of its aria-hidden attribute.

<input disabled aria-hidden="true" aria-label="firstname" />

Inapplicable Example 3

This select element is not included in the accessibility tree because it is disabled and has a role attribute value of “presentation”.

<select role="none" disabled>
	<option value="volvo">Volvo</option>
	<option value="saab">Saab</option>
	<option value="opel">Opel</option>
</select>

Glossary

Accessible Name

The accessible name is the programmatically determined name of a user interface element that is included in the accessibility tree.

The accessible name is calculated using the accessible name and description computation.

For native markup languages, such as HTML and SVG, additional information on how to calculate the accessible name can be found in HTML Accessibility API Mappings 1.0, Accessible Name and Description Computation (working draft) and SVG Accessibility API Mappings, Name and Description (working draft).

For more details, see examples of accessible name.

Note: As per the accessible name and description computation, each element always has an accessible name. When no accessible name is provided, the element will nonetheless be assigned an empty ("") one.

Note: As per the accessible name and description computation, accessible names are flat string trimmed of leading and trailing whitespace. Notably, it is not possible for a non-empty accessible name to be composed only of whitespace since these must be trimmed.

Attribute value

The attribute value of a content attribute set on an HTML element is the value that the attribute gets after being parsed and computed according to specifications. It may differ from the value that is actually written in the HTML code due to trimming whitespace or non-digits characters, default values, or case-insensitivity.

Some notable case of attribute value, among others:

This list is not exhaustive, and only serves as an illustration for some of the most common cases.

The attribute value of an IDL attribute is the value returned on getting it. Note that when an IDL attribute reflects a content attribute, they have the same attribute value.

Explicit Semantic Role

The explicit semantic role of an element is determined by its role attribute (if any).

The role attribute takes a list of tokens. The explicit semantic role is the first valid role in this list. The valid roles are all non-abstract roles from WAI-ARIA Specifications. If the element has no role attribute, or if it has one with no valid role, then this element has no explicit semantic role.

Other roles may be added as they become available. Not all roles will be supported in all assistive technologies. Testers are encouraged to adjust which roles are allowed according to the accessibility support base line. For the purposes of executing test cases in all rules, it should be assumed that all roles are supported by assistive technologies so that none of the roles fail due to lack of accessibility support.

Focusable

Elements that can become the target of keyboard input as described in the HTML specification of focusable and can be focused.

Hidden State

An HTML element’s hidden state is “true” if at least one of the following is true for itself or any of its ancestors in the flat tree:

In any other case, the element’s hidden state is “false”.

Implicit Semantic Role

The implicit semantic role of an element is a pre-defined value given by the host language which depends on the element and its ancestors.

Implicit roles for HTML and SVG, are documented in the HTML accessibility API mappings (working draft) and the SVG accessibility API mappings (working draft).

Included in the accessibility tree

Elements included in the accessibility tree of platform specific accessibility APIs. Elements in the accessibility tree are exposed to assistive technologies, allowing users to interact with the elements in a way that meet the requirements of the individual user.

The general rules for when elements are included in the accessibility tree are defined in the core accessibility API mappings. For native markup languages, such as HTML and SVG, additional rules for when elements are included in the accessibility tree can be found in the HTML accessibility API mappings (working draft) and the SVG accessibility API mappings (working draft).

For more details, see examples of included in the accessibility tree.

Note: Users of assistive technologies might still be able to interact with elements that are not included in the accessibility tree. An example of this is a focusable element with an aria-hidden attribute with a value of true. Such an element could still be interacted using sequential keyboard navigation regardless of the assistive technologies used, even though the element would not be included in the accessibility tree.

Marked as decorative

An element is marked as decorative if one of the following conditions is true:

Elements are marked as decorative as a way to convey the intention of the author that they are pure decoration. It is different from the element actually being pure decoration as authors may make mistakes. It is different from the element being effectively ignored by assistive technologies as rules such as presentational roles conflict resolution may overwrite this intention.

Elements can also be ignored by assistive technologies if their hidden state is true. This is different from marking the element as decorative and does not convey the same intention. Notably, the hidden state of an element may change as users interact with the page (showing and hiding elements) while being marked as decorative should stay the same through all states of the page.

Outcome

An outcome is a conclusion that comes from evaluating an ACT Rule on a test subject or one of its constituent test target. An outcome can be one of the three following types:

Note: A rule has one passed or failed outcome for every test target. When there are no test targets the rule has one inapplicable outcome. This means that each test subject will have one or more outcomes.

Note: Implementations using the EARL10-Schema can express the outcome with the outcome property. In addition to passed, failed and inapplicable, EARL 1.0 also defined an incomplete outcome. While this cannot be the outcome of an ACT Rule when applied in its entirety, it often happens that rules are only partially evaluated. For example, when applicability was automated, but the expectations have to be evaluated manually. Such “interim” results can be expressed with the incomplete outcome.

Programmatic Label

Element L is a programmatic label of target element T if either:

For more details, see examples of programmatic label.

Note: a given element may have more than one programmatic label.

Semantic Role

The semantic role of an element is determined by the first of these cases that applies:

  1. Conflict If the element is marked as decorative, but the element is included in the accessibility tree; or would be included in the accessibility tree when its hidden state is false, then its semantic role is its implicit role.
  2. Explicit If the element has an explicit role, then its semantic role is its explicit role.
  3. Implicit The semantic role of the element is its implicit role.

Visible

Content perceivable through sight.

Content is considered visible if making it fully transparent would result in a difference in the pixels rendered for any part of the document that is currently within the viewport or can be brought into the viewport via scrolling.

Content is defined in WCAG.

For more details, see examples of visible.

WAI-ARIA specifications

The WAI ARIA Specifications group both the WAI ARIA W3C Recommendation and ARIA modules, namely:

Note: depending on the type of content being evaluated, part of the specifications might be irrelevant and should be ignored.

Acknowledgements

This rule was written in the ACT Rules community group, with the support of the EU-funded WAI-Tools Project.

Authors

Changelog

This is the first version of this ACT rule.

presentational roles conflict resolution: https://www.w3.org/TR/wai-aria-1.1/#conflict_resolution_presentation_none ‘Presentational Roles Conflict Resolution’ [semantic role]: #semantic-role ‘Definition of Semantic Role’ [semantic roles]: #semantic-role ‘Definition of semantic role’ [visible]: #visible ‘Definition of Visible’ [label]: https://www.w3.org/TR/WCAG21/#dfn-labels ‘WCAG definition of Labels’ [sc332]: https://www.w3.org/TR/WCAG21/#labels-or-instructions

Back to Top

This is an unpublished draft preview that might include content that is not yet approved. The published website is at w3.org/WAI/.