ARIA · WCAG 2.0 Level A
aria-braille attributes must have a non-braille equivalent
Ensure aria-braillelabel and aria-brailleroledescription have a non-braille equivalent.
What it means
The aria-braille-equivalent rule flags elements that fail this check. It maps to WCAG success criterion 4.1.2.
Who it affects
Screen reader and voice control users, who depend on ARIA roles and attributes being valid.
How to fix it
Use native HTML elements where possible. If you use ARIA, use only valid roles and attributes, with allowed values, on elements that support them.
Check it on your site
Run a free scan. If this rule fails, the results list the affected elements. Deque, which maintains axe-core, also documents this rule in detail: Deque University: aria-braille-equivalent.
Quick answers
What does the axe rule "aria-braille-equivalent" check?
Ensure aria-braillelabel and aria-brailleroledescription have a non-braille equivalent.
How do I fix "aria-braille attributes must have a non-braille equivalent"?
Use native HTML elements where possible. If you use ARIA, use only valid roles and attributes, with allowed values, on elements that support them.
Who is affected by aria-braille-equivalent failures?
Screen reader and voice control users, who depend on ARIA roles and attributes being valid.
Automated accessibility scan. Results are informational and may not identify every accessibility issue. This service is not legal advice, a compliance certification, or a substitute for comprehensive manual accessibility testing.