You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When in use on a client website, accessibility audits are flagging the interactivity of the footnote <sup> elements.
What's your proposed solution?
The audit tool is requesting either using an alternative markup or making them more accessible to screen readers via a tabindex attribute. Is this possible to add?
Additional context
No response
The text was updated successfully, but these errors were encountered:
On its own, a <sup> isn't interactive. If you were to enable outputting of anchor links, these are accessible through keyboard navigation. My primary concern is that the default HTML Purified config will actually strip the attribute out.
Nevertheless, I've updated this for the next release. To get this early, run composer require verbb/footnotes:"dev-craft-4 as 4.0.1".
What are you trying to do?
When in use on a client website, accessibility audits are flagging the interactivity of the footnote
<sup>
elements.What's your proposed solution?
The audit tool is requesting either using an alternative markup or making them more accessible to screen readers via a
tabindex
attribute. Is this possible to add?Additional context
No response
The text was updated successfully, but these errors were encountered: