We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Select
zpl://screen?pid=5acd19ff49a1429169c3128b&sid=5cf0449804fcd97a2fe8a9cb
TBD
@owendodd
Adds custom dropdown implementation to Select element.
Buttons, links, loaders, inputs, dropdowns, etc
Is it using up-to-date tokens from above?
Have all states been captured? (hover, selected, disabled, focused, normal, thinking, errors)
Have all transitions/animations been defined?
Is it useable? (Considering touch targets, screen sizes)
Is it consistent with the rest of the visual system? (Corner radius, stroke weight, form, shadow, opacity, etc)
Does it meet accessibility standards? (is it keyboard navigable, does it have required accessibility markup)
Does it render and function properly in Artsy supported browsers?
Do all images and multimedia have alt or title tags?
alt
title
Are semantic elements used appropriately (nav, button, etc)?
nav
button
Are new components keyboard-navigable?
Are hover interactions available by other means?
Are aria- attributes included where appropriate?
aria-
Has a Chrome Devtools accessibility audit been performed?
Has the new component been reviewed in Browserstack:
Desktop Chrome
Desktop Edge
Desktop Safari
Desktop Firefox
Android
iOS
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Component Name
Select
Zeplin link
zpl://screen?pid=5acd19ff49a1429169c3128b&sid=5cf0449804fcd97a2fe8a9cb
Product team
TBD
Design lead
@owendodd
Additional info
Adds custom dropdown implementation to
Select
element.Checklists
Design
For Elements
Buttons, links, loaders, inputs, dropdowns, etc
Is it using up-to-date tokens from above?
Have all states been captured? (hover, selected, disabled, focused, normal, thinking, errors)
Have all transitions/animations been defined?
Is it useable? (Considering touch targets, screen sizes)
Is it consistent with the rest of the visual system? (Corner radius, stroke weight, form, shadow, opacity, etc)
Does it meet accessibility standards? (is it keyboard navigable, does it have required accessibility markup)
Does it render and function properly in Artsy supported browsers?
Engineering
Accessibility
Do all images and multimedia have
alt
ortitle
tags?Are semantic elements used appropriately (
nav
,button
, etc)?Are new components keyboard-navigable?
Are hover interactions available by other means?
Are
aria-
attributes included where appropriate?Has a Chrome Devtools accessibility audit been performed?
Compatibility
Has the new component been reviewed in Browserstack:
Desktop Chrome
Desktop Edge
Desktop Safari
Desktop Firefox
Android
iOS
The text was updated successfully, but these errors were encountered: