terra-button UX Audit

[ryanthemanuel]

terra-button

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.
  • Compact buttons need to be addressed in the design standard

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.
  • If we keep the older transitionary props, we should add guides about only using those in hybrid type scenarios
  • Evaluate the various events and set expectations for when which ones should be used and remove ones that aren't needed
  • Either evaluate isReversed as something to be deprecated or give guidance on when it should be used
• Deprecation guide

Accessibility Guides

• Missing Accessibility Guides

Behaviours

• Missing behaviours
• Contains bad practice behaviours that should be removed
  • De-emphasis has the potential to not meet accessibility standards and needs to be revisited
  • Ghost should go away long term
  • Ultimately, neutral and emphasis should only be used in OCS applications, however we need a solution for non-navigable link buttons. Probably move it to hyperlink.
  • Look into removing 'href' from buttons
  • Evaluate the various events and set expectations for when which ones should be used and hide ones that aren't needed
  • Need to evaluate compact - should it belong in the places it should be used (e.g. table), should it be a separate component, should it be a variant in and of itself (since we don't have an emphasis compact button).
  • Need to evaluate whether we should lock down isReversed somehow
  • HF says no reset buttons. Potentially remove it from the props table

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