Accessibility question about tabs kit #12630
-
|
Hi -- I am wondering if you could help me understand the accessibility approach for your Tabs kit. I'm not seeing the ARIA properties I'd expect to see in the rendered HTML in your examples. Are the tabs intended to follow WCAG tab patterns? Is the user supposed to implement accessibility themselves using an activeIndex? Thanks for any help you can provide here. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
There are currently no ARIA attributes/roles defined for tabs, you can file an issue for improving this part. Keyboard navigation, however, works as expected with tab key focusing the active tab element and arrows navigation within the tabs. The library as a whole should be fully keyboard accessible but roles and ARIA attributes are lacking and we plan to address this in the future |
Beta Was this translation helpful? Give feedback.
There are currently no ARIA attributes/roles defined for tabs, you can file an issue for improving this part. Keyboard navigation, however, works as expected with tab key focusing the active tab element and arrows navigation within the tabs. The library as a whole should be fully keyboard accessible but roles and ARIA attributes are lacking and we plan to address this in the future