Repository navigation
Question: role presentation on non-semantic elements - why? #1647
Description
In the ARIA 1.2 Spec for Role Presentation Example 9 has the following example:
<!-- 3. Depending on styling and other factors, this role declaration is redundant in some implementations. --> <span role="presentation"> Sample Content </span>
I am finding a lot of seemingly unnecessary uses of role presentation/none on non-semantic elements in the wild and when accessibility testing. The 'Depending on styling and other factors' has no further explanation as to why styling or factors would require this role.
I have read that the Role Presentation/None can be used as a bug fix, but can't remember what it fixes.
I'd appreciate your opinion on this.
Metadata
Metadata
Assignees
Labels
No labels
Activity
pkra commentedon Nov 17, 2021
According to git, this line has not been changed in 7 years, so it's likely out of date. (Part 2 of that example is now also out of date since there's now a generic role.)
pkra commentedon Nov 18, 2021
From today's call: the third example is related to #1454 -- with some patterns (e.g., those needing aria-level), elements in between parent and children roles might require an explicit role=presentation. Otherwise, AT might get tripped up. [I hope I captured the group's discussion correctly.]
Once #1454 is done (on track for ARIA 1.3), we might be able to simply remove this. We might want to keep a note on the more complex situation as well.
(And again, the second example needs revisions as well.)
scottaohara commentedon Mar 4, 2022
Seems to me we should clean up this example, if not for the fact that a
spanin aria 1.2 is noted as an HTML equivalent forrole=generic, so this example is now not only unclear, but outdated in its accuracy.Update index.html
Update index.html (#1699)
Update index.html (#1699)
Update index.html (#1699)