Accessibility checking

Rocket Validator looks for accesibility violations on your pages using the axe-core accessibility engine, hosted on our own servers and integrated into our web crawler. You don't need to buy an additional license, everything's already included in your Pro account at Rocket Validator.

WCAG: 2.5.3: Label and name from content mismatch

Interactive elements labeled through their content must have their visible label as part of their accessible name

This rule applies to any element that has:

  • a semantic role that is a widget that supports name from content, and

  • visible text content, and

  • an aria-label or aria-labelledby attribute.

Note: widget roles that supports name from content are: button, checkbox, gridcell, link, menuitem, menuitemcheckbox, menuitemradio, option, radio, searchbox, switch, tab, treeitem.

Expectation

The complete visible text content of the target element either matches or is contained within its accessible name.

Note: Leading and trailing whitespace and difference in case sensitivity should be ignored.

Speech input users can interact with a webpage by speaking the visible text labels of menus, links, and buttons that appear on the screen. It is confusing to speech input users when they say a visible text label they see, but the speech command does not work because the component's accessible (programmatic) name does not match the visible label. When a user interface component has a visible text label — whether it be real text or an image of text — that text must also be found in the component's accessible (programmatic) name. When the visible label and accessible (programmatic) name for interactive components are in sync, speech input users can effectively interact with those components.

Learn more about this accessibility rule at Deque University >>

Validate accessibility and HTML5 on large sites, starting at $24/week. Start here