Unknown ARIA attribute

Why does it matter?

WCAG 4.1.2 asks that assistive technology gets a control's name, role and state; this attribute is not in WAI-ARIA, so browsers ignore it and whatever it was meant to say is lost.

Who it affects: Screen reader and keyboard users, who depend on ARIA and focus order being correct to understand and operate the page.

What does Lumtera flag?

Attributes that start with aria- but are not in WAI-ARIA, often a spelling mistake. For review.

Check ID aria-unknown-attribute — use it to filter the content report or with wp lumtera issues --rule.

How do I fix it in WordPress?

Correct the spelling (aria-labelledby has two Ls), or remove the attribute. If a theme or plugin writes it, report it to its developer.

Example

<nav aria-labeledby="menu-title">…</nav>

<nav aria-labelledby="menu-title">…</nav>

How do I check the fix?

1. Update the post. The issue disappears from the Lumtera Accessibility sidebar on the next check, and from the site report on the next scan.
2. Press Tab from the top of the page. Focus should move in reading order and never land on something invisible or silent.