3 ms·
What accessibility problems, specifically? It's all operable and navigable by keyboard. It could be further enhanced with ARIA tab panel attributes.
by extra88 10y ago
What accessibility problems, specifically? It's all operable and navigable by keyboard. It could be further enhanced with ARIA tab panel attributes.
- grahamel 10y agoWell the final example[1] isn't usable via keyboard at all [1]http://codepen.io/CiTA/pen/ALVWzg http://codepen.io/CiTA/pen/ALVWzg
- extra88 10y agoSure it is, I did so before I posted.
- deadcast 10y agoI had to first click on one of the tabs before it started letting me use the keyboard.
- grahamel 10y agobut that's tabbing with the left/right keys instead of the tab key, which is how I tab through a website ignoring the fact that there's no :active styling in the css, there is nothing to indicate that to change the tab you need to use different keys
- TylerH 10y agoYes it is; I can switch between tabs just fine with arrow keys.
- aplummer 10y agoI have had a WCAG AA 2.0 audit failure doing this because this approach is not obvious to a sighted keyboard only use that space bar and arrow keys and not tab + enter is the control mechanism. Also a non sighted user will need hidden text before the tabs at a minimum to explain how they work.