a[href][disabled] is still a focusable element

[WilcoFiers]

Noticed this in reviewing #3165. In determining if an element is focused, axe-core looks at the disabled attribute. However it doesn't check if that attribute is allowed for the node. So the following link is incorrectly determined as not focusable:

<a href="foo.html" disabled>Hello</a>

This bug exists in lib/commons/dom/focus-disabled.js. The fix is to check vNode.props.nodeName before looking for the disabled attribute.

[dan-tripp]

I would like to fix this one. But it might take me a few weeks to get around to it.

[WilcoFiers]

@dan-tripp You are welcome to it. Much appreciated!

[OmiCoding]

I was looking for issues to fix and I noticed this issue was already fixed in bb8b5ca, could a maintainer mark this as closed?

[padmavemulapati]

Verified with the latest dev branch code , role=text is allowing to have "tabindex=-1" as a descendants

and with the nested-interactive/aria-text allowing "tabindex=-1" on elements when role is not there.
and role conflict is appearing, when tabindex=-1 and role=presentation