It looks like the Tabs component supports automatic activation out of the box. Is there a way to make it work with manual activation?
ZebraFlesh
All 7 comments
Can you elaborate on this a little more? "Manual activation"?
bradwestfall
on 1 Oct 2019
Sure, here's the manual activation example: https://www.w3.org/TR/wai-aria-practices-1.1/examples/tabs/tabs-2/tabs.html
If the contents of every tab panel are the result of an ajax call, then you don't want to automatically activate every tab. Instead you want the user to be able to navigate to the desired tab and then manually activate it.
ZebraFlesh
on 2 Oct 2019
Thanks @ZebraFlesh, I just wanted more info for @mjackson and @chancestrickland who are going through issues
bradwestfall
on 2 Oct 2019
@ZebraFlesh Have you found a workaround for manual activation in the meantime?
@chancestrickland Big +1 for this!
oyeanuj
on 28 Mar 2020
No work around at this time that I鈥檓 aware of
ZebraFlesh
on 28 Mar 2020
BTW this was introduced with the keyboardActivation prop. https://reacttraining.com/reach-ui/tabs#tabs-keyboardactivation
chaance
on 20 Apr 2020
Awesome, thank you for this!
ZebraFlesh
on 20 Apr 2020
Related issues
arackaf
路
6Comments
sanderfish
路
5Comments
chaance
路
5Comments
denkristoffer
路
5Comments
rumsky
路
6Comments
Most helpful comment
Sure, here's the manual activation example: https://www.w3.org/TR/wai-aria-practices-1.1/examples/tabs/tabs-2/tabs.html
If the contents of every tab panel are the result of an ajax call, then you don't want to automatically activate every tab. Instead you want the user to be able to navigate to the desired tab and then manually activate it.