Closed shenanigans closed 7 years ago
That's a better question for @scottaohara. He'll hopefully chime in here, though I am going to close this issue.
There's plenty of resources and articles around the a11y implications of CSS-only approaches to things like this, and it's a bit off topic in the context of this specific script.
@shenanigans while CSS only solutions are often clever, they more often do not provide experiences that users of keyboard and/or assisitive technology would expect.
per tabs, you can see what the official ARIA best practices specification outlines as the necessary information/experience one needs to provide, to create an accessible tab component - https://www.w3.org/TR/wai-aria-practices/#tabpanel
I've just been doing this. Do you know of any accessibility issues with this method?