terra-date-input UX Audit

[ryanthemanuel]

terra-date-input

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.
  • Missing the Date Input completely from 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
  • Need to update the guides to list fields up front and field-less pickers shouldn't display as if they are fields
  • Field documentation could be beefed up a bit
• Missing UX recommended Usage.
• Deprecation guide

Accessibility Guides

• Missing Accessibility Guides

Behaviours

• Missing behaviours
• Contains bad practice behaviours that should be removed
  • Remove isLegendHidden and require the legend prop

Accessibility

• Meets wcag 2.0/section 508 standards
  • Each input in the fieldset should describe the type and information about valid values for the input (past, future, etc.)
  • Have an aria-live span that writes out what has been filled out so far
  • Inter-input keyboard interactions need to be landed on
• Meets wcag 2.1/en 301 549 standards

Deprecation

• Component is a bad pattern and should be deprecated.

Related Issues

Other Considerations

Create the same behavior patterns across all date inputs (e.g. auto jumping between inputs as a possibility)