This rule checks that the HTML autocomplete attribute has a correct value
This conformance rule relates to:
The rule applies to any HTML
textarea element with a non-empty
autocomplete attribute, except if one of the following is true:
inputelement with a
tabindex="-1"and has a semantic role that is not a widget
autocomplete attribute is a single term, or a space separated list of terms.
The autocomplete term(s) follow the HTML 5.2 specification, which requires that it/they match the following in the correct order:
Note: Autocomplete terms are case insensitive. When multiple terms are used, they must be used in the correct order.
For this rule, it is assumed that the
autocomplete attribute is not used on form fields that do not correspond to a autocomplete field described in the HTML 5.2 specification. If the
autocomplete field is used to describe “custom” taxonomy, rather than that described in the specification, this rule may produce incorrect results.
autocomplete in a promising technique for supporting personalisation in HTML, support for this is fairly limited.
The intent of this rule is to ensure that the
autocomplete attribute can be used to suport personalization. Many users may find it easier to fill out forms if those can be styled or layed out in a way that is familiar to them. Assistive technologies can do this when a form control is marked up in such a way that its purpose can be understood. For instance, assistive technologies could add familiar icons and colors to different fields, making it easier for the user to understand what the form does.
Single autocomplete term.
Single autocomplete term for select.
Autocomplete term, only valid for textarea.
Two autocomplete terms.
Autocomplete using section-*
Triple autocomplete terms.
Full length autocomplete terms.
Unknown autocomplete term.
work not allowed before
Invalid order of terms.
Comma seperated rather than space separated list.
Autocomplete is inappropriate for the type of field.
Off screen and hidden to assistive technologies
A string of characters (text) is considered “non-empty” if it contains 1 or more characters that are contained within any of the following unicode categories:
For more details on unicode categories, check out www.fileformat.info/info/unicode/category/
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 and the SVG accessibility API mappings.
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-hiddenattribute with a value of
true. Such an element could still be interacted with using sequential keyboard navigation regardless of the assistive technologies used, even though the element would not be included in the accessibility tree.
Elements should be visible on the page, and also meet the requirements for color contrast and visibility when focused. For more details, check out:
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.
A semantic role is a semantic association that indicates an object’s type. This allows tools to present and support interaction with the object in a manner that is consistent with user expectations about other objects of that type.
The role attribute takes a list of tokens. The semantic role is the first valid role in this list. If none of the tokens are valid, the implicit role will be used instead.
Non-abstract roles defined in the following specifications are considered valid:
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.
Note: For HTML elements the implicit roles are documented in ARIA in HTML.
Any field name listed in the autocomplete fields table from the HTML 5.2 specification: https://www.w3.org/TR/html52/sec-forms.html#autofill-field
The field name listed in the autocomplete fields table from the HTML 5.2 specification is used in the
autocomplete attribute of an element: https://www.w3.org/TR/html52/sec-forms.html#inappropriate-for-the-control
Contributing is open to anyone. We welcome any new issues or pull requests for changes. Auto WCAG Rules has conference calls every 4 weeks. If you are interested in becoming an active contributor or reviewer, we ask that you join the Auto WCAG Rules community group through the W3C Website. This requires setting up a W3C account, may require approval by the organization you work for if they are a W3C member.Learn more about contributing to Auto WCAG Rules Join the Auto WCAG Rules community group now!