Designing Power Apps for colour blindness
Diesen Beitrag auf Deutsch lesen
Use icons, text labels, accessible error messages, contrast checks and grayscale testing so Power Apps do not rely on colour alone.
Original article from February 7, 2026: Designing for Color Blindness in Power Apps, by Paulien Buskens, on Pauliens Blog. Read the original
Source may be outdated. The original article is more than 60 days old. Dates and availability refer to the state of the source.
This is our own summary, not a republication or full translation.
TL;DR
Power Apps makers can make status, validation and dashboard signals clearer by pairing colour with icons or text, adding AccessibleLabel values to errors, using data labels and testing screens in grayscale. The guidance also recommends at least 4.5:1 contrast for body text and testing high-contrast themes.
Why it matters
- Makers: Pair approval, rejection and pending colours with icons or text so gallery and button states remain understandable.
- Makers: Add clear error messages and AccessibleLabel values instead of relying on a red border or red text.
- BI/Data teams: Add labels, trend icons or a small data table to red and green dashboard comparisons.
- Makers: Test screens in grayscale and with high-contrast themes to reveal signals that disappear.
Frequently asked questions
How can Power Apps status indicators work for colour-blind users?
Pair every status colour with an icon or text label. Approved, rejected and pending states can use distinct icons alongside supportive colour.
What should a Power Apps validation error include besides a red border?
Include a clear error message and an AccessibleLabel for screen readers. Red text or a red border alone does not communicate the problem reliably.
How do I test whether a Power Apps dashboard relies too much on colour?
View the app in grayscale or use a browser simulator. Add direct data labels, trend icons or a small table when chart meaning disappears.