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

terra-dropdown-button UX Audit #3185

Open
2 of 12 tasks
ryanthemanuel opened this issue Oct 8, 2020 · 0 comments
Open
2 of 12 tasks

terra-dropdown-button UX Audit #3185

ryanthemanuel opened this issue Oct 8, 2020 · 0 comments

Comments

@ryanthemanuel
Copy link
Contributor

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

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.
    • We need a good guide for when you use a drop down button vs. when you use a split button
  • Deprecation guide

Accessibility Guides

  • Missing Accessibility Guides

Behaviours

  • Missing behaviours
  • Contains bad practice behaviours that should be removed
    • May need to validate whether or not the block drop down button makes sense
    • Evaluate whether ghost is needed

Accessibility

  • Meets wcag 2.0/section 508 standards
    • Does not read the thing that was selected when something is selected
    • May be some additional nuances that we need to work through
    • Split button needs to have its keyboard navigability evaluated
    • Wording of the alt text for split button's caret could be reevaluated
  • Meets wcag 2.1/en 301 549 standards

Deprecation

  • Component is a bad pattern and should be deprecated.

Related Issues

Other Considerations

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