Is there a good reason that the AUI Button docs state the use of aria-disabled

[Mark Gibson]

An example given in the AUI docs:

<button class="aui-button" aria-disabled="true" disabled="">Button</button>

What is the point in the aria-disabled attribute on a button? I understand what ARIA is btw, but this seems like someone has just got a bit too eager with their use of it in this specific case.

The button appears to style fine without it. It just seems to be an over-complication of markup and any JS code required to switch states.

I'd say that the First rule of ARIA use makes this redundant.

[Sean Curtis · Accepted solution]

@Mark Gibson it is indeed a little overkill, and is redundant if you also have the disabled attribute on the button. However aui-button is not limited to <button> and <input> elements, it can also appear on a hyperlink. Sometimes these will be disabled (for whatever reason), and rather than use the disabled attribute on links (which does nothing), we opted to be more explicit and use the aria attribute across all instances.

Soon we will be using web components for most things, so developers won't need to worry about maintaining all these accessibility-related attributes. They will be handled by the component itself.

[Mark Gibson]

Thanks for the clarification Sean.