Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Accessibility Recommendations #15

Open
jpobojewski opened this issue Aug 14, 2023 · 1 comment
Open

Accessibility Recommendations #15

jpobojewski opened this issue Aug 14, 2023 · 1 comment

Comments

@jpobojewski
Copy link

What are you trying to do?

Screenshot 2023-08-14 at 2 30 54 PM

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

@engram-design
Copy link
Member

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".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants