label and name from content mismatch
Interactive elements labelled through their content must have their visible label as part of their accessible name
This conformance rule relates to:
This rule applies to any element that has:
Note: Leading and trailing whitespace and difference in case sensitivity should be ignored.
There are currently no assumptions
There are no major accessibility support issues known for this rule.
Visible label and accessible name matches when trailing white spaces are removed.
Character insensitivity between visible label and accessible name.
Full visible label is contained in the accessible name.
Visible label doesn’t match accessible name.
Not all of visible label is included in accessible name.
Not a widget role.
Widget role that does not support name from content.
Non-widget role that supports name from content.
No rendered text in name from content.
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.
Note: These elements should also be ensured to meet the color contrast and visibility requirements.
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.
The programatically 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 and SVG Accessibility API Mappings, Name and Description.
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!