Product

axe-core

Question

When an input element has type="range" (i.e. a slider input), the presence of the attribute aria-required="true" triggers the Axe rule Elements must only use allowed ARIA attributes. This rule has the impact level "Critical" (the highest level), i.e. "Results in blocked content for people with disabilities, and will definitely prevent them from accessing fundamental features or content."

I understand that incorrect roles can be blocking in certain cases, but why would aria-required="true" be blocking on a slider / range input? I also understand that marking a slider input as required makes little sense, since the input always has a default value, even without user interaction. In fact, the HTML 5 specification even prohibits the native attribute required on a slider. But that still does not explain why aria-required="true" would be a blocking issue on a range input.

Is this really a blocking issue or does the rule "Elements must only use allowed ARIA attributes" catch too many things?