Skip to content
Pandus

WCAG A/AA requirement Priority: Moderate

Some elements have a braille label but no normal name

Some elements carry a label meant only for braille displays (aria-braillelabel or aria-brailleroledescription) but lack the ordinary label or description it is supposed to accompany.

This text was translated automatically and has not been reviewed by a native speaker yet.

Why it matters to your customers

Customers who use speech output instead of a braille display get no name or a wrong description for the element, for example a button or a status badge, and cannot tell what it does.

Who is affected

  • screen reader users
  • blind customers

How to fix it

Use braille attributes only in addition to a normal name. An element with aria-braillelabel also needs a visible text, aria-label or aria-labelledby; an element with aria-brailleroledescription also needs aria-roledescription. In most shops the simplest fix is to remove the braille attributes.

On Shopify

Very rare in Shopify themes and apps. Search the theme code and app snippets for "aria-braille" and either add a normal name or remove the attribute.

On Shoptet (CZ)

Very rare in Shoptet templates. If it appears, it usually comes from custom code added to the template; ask a Shoptet partner to correct it.

On PrestaShop

Very rare. Search the theme .tpl files and module templates for "aria-braille" and add a normal name or remove the attribute.

On WooCommerce

Very rare. Search the child theme and plugin output for "aria-braille"; fix it in the theme or report it to the plugin author.

Standards

Standards
StandardClause
WCAG 2.2 4.1.2 (A) Name, Role, Value
WCAG 2.1 4.1.2 (A) Name, Role, Value
WCAG 2.0 4.1.2 (A) Name, Role, Value
EN 301 549 4.1.1 9.4.1.2
EN 301 549 3.2.1 9.4.1.2
Section 508 2017 E205.4
ДСТУ EN 301 549 2022 9.4.1.2

Automated check: axe-core rule aria-braille-equivalent. dequeuniversity.com, github.com, www.w3.org

All rules we check