terra-tabs UX Audit

[ryanthemanuel]

terra-tabs

Tabs need to be revamped in general due to their current inaccessible nature. Prototypes exist here:

https://github.com/cerner/terra-framework/tree/tabs-2-all-or-nothing
https://github.com/cerner/terra-framework/tree/tabs-2-rollup
https://github.com/cerner/terra-framework/tree/tabs-2-the-tabbening

Icons and Notification Breadcrumb states (Error, Warning, etc.) need to be revisited and determined how best to handle in all versions of responsive tabs (large and small viewport versions).

Known Aliases

Document any known aliases of the component, decide if another name makes more sense.

• Has known aliases
• Requires name change

Design Standard Doc

Any documentation needed to be added to terra-ui describing the make up and usage of the component
Any doc examples that need to be updated?

• Missing design standard documentation linkage.

Guides

Any guides needed to be added to terra-ui describing the usage of this component when used with other components.

• Missing Guides
• Missing UX recommended Usage.
• Deprecation guide

Accessibility Guides

• Missing Accessibility Guides

Behaviours

• Missing behaviors
• Contains bad practice behaviors that should be removed (disabled tabs, custom tab display also problematic)

Accessibility

• Meets wcag 2.0/section 508 standards
• Meets wcag 2.1/en 301 549 standards

Deprecation

• Component is a bad pattern and should be deprecated.

Related Issues

Other Considerations

[benbcai]

An addition change that needs to be made to improve accessibility is to add aria-disabled on the tab pane if isDisabled is true to convey appropriate accessibility information.