Skip to content
This repository has been archived by the owner on May 24, 2024. It is now read-only.

terra-time-input UX Audit #1340

Open
12 tasks
ryanthemanuel opened this issue Dec 2, 2020 · 0 comments
Open
12 tasks

terra-time-input UX Audit #1340

ryanthemanuel opened this issue Dec 2, 2020 · 0 comments

Comments

@ryanthemanuel
Copy link
Contributor

terra-time-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.

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 behaviours
  • Contains bad practice behaviours that should be removed

Accessibility

  • Meets wcag 2.0/section 508 standards
    • Needs a field set label that makes sure the user knows that there is auto advancement to the next field and other context about how we're inputting the entire set of options
  • Meets wcag 2.1/en 301 549 standards

Deprecation

  • Component is a bad pattern and should be deprecated.

Related Issues

Other Considerations

There is some weirdness around keyboard interactions and deletions.

Any keys other than the hot keys (t and n) should provide some feedback to the user that they are not being used.

Need to resolve the field version of this.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant