I would love to see such tools have some accessibility DX built-in. The idea is to define the color palette in such a way that we know whether a color combination is accessible just by looking at the color name. For example, using the USWDS design system, I know that blue-30 on gray-80 is accessible (WCAG AA), because the difference between both values is 50+. I once wrote a blog post about this (niche) concept: http…
Tailwind color palette generator
71–80 of 83 posts
Re: Tailwind color palette generator
#72Earlier quoted context omitted.
You identified the concept as niche, but I would argue this should be a first-class priority in web design. We will all be disabled at some point, permanently or temporarily. So many great tools are unusable due to accessibility reasons (like Streamlit!).
The concept of color contrast isn't niche, but building your color palette around the WCAG contrast algorithm kind of is. It's useful for checking boxes if you're required to do WCAG audits, but is neither necessary nor sufficient to ensure actual users with disabilities are able to read your text. For example, #F00 text on an #000 background passes WCAG AA, but will be unreadable for users with a common form of colo…
Re: Tailwind color palette generator
#73Earlier quoted context omitted.
The concept of color contrast isn't niche, but building your color palette around the WCAG contrast algorithm kind of is. It's useful for checking boxes if you're required to do WCAG audits, but is neither necessary nor sufficient to ensure actual users with disabilities are able to read your text. For example, #F00 text on an #000 background passes WCAG AA, but will be unreadable for users with a common form of colo…
This brings up another interesting point I haven't considered before: how to make things not only functional, but beautiful for folks with different kinds of color vision. I wonder if there's any research into the aesthetics of design for including color blind folks.
Re: Tailwind color palette generator
#74Earlier quoted context omitted.
What accessibility issues does the streamlit library have?
Loss of keyboard focus, no streamlined way to set tab order, no ability to set a specific ID components for screen readers, and more.
Re: Tailwind color palette generator
#75I would love to see such tools have some accessibility DX built-in. The idea is to define the color palette in such a way that we know whether a color combination is accessible just by looking at the color name. For example, using the USWDS design system, I know that blue-30 on gray-80 is accessible (WCAG AA), because the difference between both values is 50+. I once wrote a blog post about this (niche) concept: http…
I'm not aware of any tools though that leverage the concepts they laid out to generate new palettes.
Re: Tailwind color palette generator
#76Earlier quoted context omitted.
You identified the concept as niche, but I would argue this should be a first-class priority in web design. We will all be disabled at some point, permanently or temporarily. So many great tools are unusable due to accessibility reasons (like Streamlit!).
The concept of color contrast isn't niche, but building your color palette around the WCAG contrast algorithm kind of is. It's useful for checking boxes if you're required to do WCAG audits, but is neither necessary nor sufficient to ensure actual users with disabilities are able to read your text. For example, #F00 text on an #000 background passes WCAG AA, but will be unreadable for users with a common form of colo…
Re: Tailwind color palette generator
#77I would love to see such tools have some accessibility DX built-in. The idea is to define the color palette in such a way that we know whether a color combination is accessible just by looking at the color name. For example, using the USWDS design system, I know that blue-30 on gray-80 is accessible (WCAG AA), because the difference between both values is 50+. I once wrote a blog post about this (niche) concept: http…
Material 3, a pretty big spec used by Google, has a color system that works like this
Re: Tailwind color palette generator
#78Earlier quoted context omitted.
The concept of color contrast isn't niche, but building your color palette around the WCAG contrast algorithm kind of is. It's useful for checking boxes if you're required to do WCAG audits, but is neither necessary nor sufficient to ensure actual users with disabilities are able to read your text. For example, #F00 text on an #000 background passes WCAG AA, but will be unreadable for users with a common form of colo…
The wcag color contrast algorithm isn't great (and there is a proposal for a better one), but sufficient color contrast is necessary for a variety of visual conditions. That it's not good enough for some doesn't mean it's not more accessible than not doing it at all though.
Many users reported this was harder to read, even those without the form of color blindness which makes black and red hard to distinguish. Whether making this change was really "more accessible" than doing nothing is therefore pretty debatable, but it definitely helped them pass their WCAG audits.
Re: Tailwind color palette generator
#79I would love to see such tools have some accessibility DX built-in. The idea is to define the color palette in such a way that we know whether a color combination is accessible just by looking at the color name. For example, using the USWDS design system, I know that blue-30 on gray-80 is accessible (WCAG AA), because the difference between both values is 50+. I once wrote a blog post about this (niche) concept: http…
You identified the concept as niche, but I would argue this should be a first-class priority in web design. We will all be disabled at some point, permanently or temporarily. So many great tools are unusable due to accessibility reasons (like Streamlit!).
Re: Tailwind color palette generator
#80I would love to see such tools have some accessibility DX built-in. The idea is to define the color palette in such a way that we know whether a color combination is accessible just by looking at the color name. For example, using the USWDS design system, I know that blue-30 on gray-80 is accessible (WCAG AA), because the difference between both values is 50+. I once wrote a blog post about this (niche) concept: http…
You identified the concept as niche, but I would argue this should be a first-class priority in web design. We will all be disabled at some point, permanently or temporarily. So many great tools are unusable due to accessibility reasons (like Streamlit!).
Well put!