UISeeds - Tabs Component

[emilyjablonski]

Transfer the Tabs component from UIC to UISeeds. (Audit Link) (Figma Docs Link)

We should make a few changes to the component on transfer:

• Tabs needs V2 styling
• This component is pulling in a 3rd party library, and is fairly clean, so should be any minimal cleanup discovered along the way
• Keep desktop/mobile flavors as is
• Ensure react-tabs library is still maintained / that there aren't other preferable tab libraries

[jaredcwhite]

@slowbot Do we know for sure if we should support counters on the Tabs component? It's not a use case we have currently AFAIK. I guess it could be argued that if Menu supports counters, Tabs should, but I could also see an argument that if there needs to be counters on various tabs, maybe that's a content structure which would be better served by separate pages & menus anyway. Thoughts?

[slowbot]

@jaredcwhite If counters are more complex then we drop them from tabs.

[jaredcwhite]

@slowbot This should be ready for a final QA in zeroheight now.

[slowbot]

@jaredcwhite

• Can we add a code sample for state in zeroheight? Or did you intentionally not include one?
• Is responsive an optional property?

[jaredcwhite]

@slowbot

• All the tabs examples show the selected state I guess, not sure what I would include there.
• It's automatically responsive, no props required

[slowbot]

@jaredcwhite I guess the current state is about being explicit about the aria labeling but can remove if it seems redundant.

In the future let me know if you recommend changes to the zeroheight docs in the ticket

[jaredcwhite]

@slowbot Sure, maybe we remove that then. For this particular component we're leveraging react-tabs which provides the right ARIA states (to the best of my knowledge).

I think it'd be cool if we could leverage zeroheight comments, but I guess we'd need to set up multiple user accounts there for that to work. (Right now when I modify things there I'm Jesse 😬)

[slowbot]

@jaredcwhite LGTM!