One important point—special thanks to “Jason Kiss”:http://accessibleculture.org for his work with “ARIA Tabbed panels”:http://www.accessibleculture.org/research/aria-tabs/. His research and testing was referenced and used heavily in the tabbed panels section of this article. We based our code on his, because… well, because it was so very thorough and well-thought out.
I’m curious if there is a specific reason for using JavaScript to insert some of the ARIA attibutes (role=“tabpanel”, role=“tab”, role=“presentation”, etc.) instead of hard-coding it into the HTML? I understand the reasoning for (aria-selected, aria-hidden and tabindex).
I would also suggest preventing the default scrolling action of the arrow keys on the tabList keydown events.
12 Reader Comments
Back to the ArticleDerek Featherstone
One important point—special thanks to “Jason Kiss”:http://accessibleculture.org for his work with “ARIA Tabbed panels”:http://www.accessibleculture.org/research/aria-tabs/. His research and testing was referenced and used heavily in the tabbed panels section of this article. We based our code on his, because… well, because it was so very thorough and well-thought out.
Thanks, Jason!
blg002
I’m curious if there is a specific reason for using JavaScript to insert some of the ARIA attibutes (role=“tabpanel”, role=“tab”, role=“presentation”, etc.) instead of hard-coding it into the HTML? I understand the reasoning for (aria-selected, aria-hidden and tabindex).
I would also suggest preventing the default scrolling action of the arrow keys on the tabList keydown events.