Why it matters
Browsers ignore misspelled or invented role values, so the element exposes its native semantics instead of the widget you intended.
How to fix it
Use a valid WAI-ARIA role. Better still, use the native element (button, a, input) that already has the role.
References
More accessibility rules
void a11y reports 48 rules in this category. WCAG 2.2 AA through axe-core, plus checks axe can't do alone: visible keyboard focus, 24/44px target size on mobile, 320px reflow and disabled zoom.
aria-allowed-attrARIA attribute is not allowed on this rolearia-required-attrRequired ARIA attribute is missingaria-required-childrenARIA role is missing required childrenaria-required-parentARIA role is missing its required parentaria-valid-attrInvalid ARIA attribute namearia-valid-attr-valueInvalid ARIA attribute valuearia-hidden-focusFocusable element inside aria-hiddenaria-hidden-bodyaria-hidden on <body>