terra-status-view UX Audit

[ryanthemanuel]

terra-status-view

Known Aliases

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

• Has known aliases
  • Error view
  • No data view
• 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.
  • Call out how to handle multiple views on the page
  • Call out not to use the full page views for a smaller space
• Deprecation guide

Accessibility Guides

• Missing Accessibility Guides

Behaviours

• Missing behaviours
  • Have the ability to have show hide for more detailed information
  • Evaluate responsiveness at small breakpoints (e.g. font sizes)
  • Evaluate a max width on the message and title
• Contains bad practice behaviours that should be removed
  • Possibly split out a custom version and have this one completely locked down
  • Possibly change this one to custom only and use the application status view to be the locked down version

Accessibility

• Meets wcag 2.0/section 508 standards
  • Need to evaluate how we're presenting the title and the message. Both p's now and probably need to be hierarchical
  • Need to evaluate the expand collapse functionality when it gets added
• Meets wcag 2.1/en 301 549 standards

Deprecation

• Component is a bad pattern and should be deprecated.

Related Issues

• Enhance Status View to support being able to see more information about a given status #3000
• Provide Application Page Status View API terra-application#30

Other Considerations