Closed giacomo-petri closed 8 months ago
The presentation roles conflict resolution does apply. You are mixing up something being tabbable with something being focusable. tabindex=-1 is still focusable so to then is the conflict resolution. This isn't just aria in html saying no, it's ARIA's rule that this spec is only clarifying.
In the context of the ARIA in HTML document, the
a
HTML element withhref
attribute accepts only specific roles, and these roles do not includepresentation
ornone
.However, there may be scenarios where an author intends to create a large clickable area for pointer device users while maintaining a meaningful and concise link for assistive technology users, such as screen reader users. To address this, a solution has been implemented as follows:
From an ARIA in HTML perspective, this approach is not currently considered acceptable. The Presentational Roles Conflict Resolution does not apply in this case, as the
a
element, even if with anhref
attribute, is not focusable.Should we consider this scenario as acceptable by adding a note to the "ARIA role, state, and property allowances" column and clarifying that if the
a
element is not included in sequential focus navigation (indicated by a negative tabindex attribute value) it should be treated differently allowing any role?I don't see any compelling reason for this approach to fail in terms of accessibility, and if you agree, I'm more than happy to propose changes in a pull request.