User Experience Stack Exchange is a question and answer site for user experience researchers and experts. It only takes a minute to sign up.
Sign up to join this community
My organization currently uses red buttons for destructive actions, e.g. Delete A or Revoke X.
I'm wondering if this hurts accessibility, given that our primary CTA buttons are blue and our secondary buttons are gray. I believe colorblind users can make that distinction.
Is there a best practices guide on destruction patterns? One that takes into account accessibility?
Disclaimer: The software I produce is not required to be WCAG compliant, so I cannot speak to any official requirements. However, my dad is colorblind, so there's that...
One of the most important accessibility considerations for colorblindness is that meaning is not communicated through color alone.
A good use of color can help to speed up processing by providing subconscious hints (e.g. red is destructive, light blue is informative, green is successful, etc.), but it shouldn't be relied upon exclusively to communicate ideas.
A simple test to determine if an item is relying too much on color is to simply remove the color and evaluate if it still communicates the same message to the user. You can search online for a colorblind simulator that will take an image or sometimes a URL and render it in various ways to simulate different colorblindness conditions.
This means that your concern should be confirming that your labeling and iconography is descriptive and consistent. As long as your text-to-background contrast is acceptable, that should be sufficient.
