Elements with braille ARIA attributes must have equivalent non-braille labels
Content available in English only.
Accessibility isn’t just about avoiding violations — it’s about ensuring that everyone can use your product with confidence. This guide explains each rule’s intent, highlights common issues, and shows how to fix them according to WCAG and the European Accessibility Act (EAA).
These guidelines do not replace the official WCAG standards. They’re concise, developer-focused notes to help you identify and fix issues effectively.
Braille ARIA attributes alone are not enough; always provide a standard accessible name.
Why this matters and how to fix it
Why this matters
Braille-specific ARIA attributes (like `aria-braillelabel` and `aria-brailleroledescription`) are only read on braille displays. Without a standard accessible name (`aria-label` or `aria-labelledby`), screen reader users miss the information, creating inconsistent or confusing experiences.
How to fix this issue
Pair braille-specific attributes with a standard accessible name. For example, add `aria-label` or `aria-labelledby` when using `aria-braillelabel`, and a corresponding `aria-roledescription` when using `aria-brailleroledescription`.
Developer guidance
Only use braille attributes when supporting braille devices. Always ensure the component exposes a standard accessible name. Validate using screen readers and accessibility tree inspections. Include checks in CI and component reviews.
Code examples
Incorrect Implementation
<div aria-braillelabel="Submit"></div>Correct Implementation
<div aria-braillelabel="Submit" aria-label="Submit"></div>Real-World Examples
Before
<button aria-braillelabel="Save"></button> <!-- Speech users hear nothing -->After
<button aria-braillelabel="Save" aria-label="Save"></button> <!-- All users hear/see the label -->Manual testing
- 1. Identify elements with `aria-braillelabel` or `aria-brailleroledescription`.
- 2. Confirm they also have `aria-label` or `aria-labelledby` for speech users.
- 3. Test with a screen reader to ensure the name is announced.
- 4. Test on a braille display if available.
- 5. Run automated accessibility checks to enforce presence of standard accessible names.
Trusted by organizations across Europe working toward WCAG and EAA conformance