-
Notifications
You must be signed in to change notification settings - Fork 16
Component checklist
Lloyd Humphreys edited this page Sep 25, 2019
·
4 revisions
As part of creating/changing a component, what should I consider?
- Font sizes
- Color contrast - Is your component usable for someone with poor eyesight?
- Color usage - Does your component have the same meaning to a color blind person?
- Alt-text - how would a screen reader process your component?
- Translations
- Right-to-left support
- Non-latin scripts
- Timezones
- Date-time-formats
- Sorting and string comparison
- Calendar differences
- Currency formatting
- Number formatting
- Address formatting
- Unit of measure
- How does your component work on a phone or tablet?
- How does your component work with touch events?
Aside support:
- How does your component work when contained within an aside?
- How does your component work when contained within a full-screen modal?
- How to use the component to build apps
- Acceptable / unacceptable design patterns for use of said component
- What happens when something goes wrong?
- What happens when there's no internet connection?
- Ensure your error messages and error handling is consistent with the rest of the component library / product
- Ensure your icon usage is consistent with the rest of the component library / product
- How might a power user interact with your component / interface?
- How does your component truncate text or numbers when there isn't enough space to show everything? (i18n.js truncate-numbers library, ellipsis for text, show it all in a tooltip on hover, etc.)