|
| 1 | +--- |
| 2 | +title: Accessible colors in PowerApps | Microsoft Docs |
| 3 | +description: Color contrast guidelines for PowerApps |
| 4 | +services: '' |
| 5 | +suite: powerapps |
| 6 | +documentationcenter: na |
| 7 | +author: tahoon |
| 8 | +manager: anneta |
| 9 | +editor: '' |
| 10 | +tags: '' |
| 11 | + |
| 12 | +ms.service: powerapps |
| 13 | +ms.devlang: na |
| 14 | +ms.topic: article |
| 15 | +ms.tgt_pltfrm: na |
| 16 | +ms.workload: na |
| 17 | +ms.date: 04/23/2018 |
| 18 | +ms.author: tahoon |
| 19 | + |
| 20 | +--- |
| 21 | +# Accessible colors in PowerApps |
| 22 | +Colors used in an app should be accessible to color-blind and low-vision users. All PowerApps themes are accessible by default. When modifying colors used in an app, follow these guidelines to ensure that they remain accessible. |
| 23 | + |
| 24 | +## Minimum contrast for text |
| 25 | +* Text and its background must have a contrast ratio of at least 4.5:1 |
| 26 | +* Large text must have a contrast ratio of at least 3:1 |
| 27 | +* Disabled text has no contrast requirements |
| 28 | + |
| 29 | +In practical terms, all interactive controls must have adequate color contrast between: |
| 30 | +* **[Color](controls/properties-color-border.md)** and **[Fill](controls/properties-color-border.md)** |
| 31 | +* **[PressedColor](controls/properties-color-border.md)** and **[PressedFill](controls/properties-color-border.md)** |
| 32 | +* **[HoverColor](controls/properties-color-border.md)** and **[HoverFill](controls/properties-color-border.md)** |
| 33 | + |
| 34 | +## Minimum contrast for non-text |
| 35 | + |
| 36 | +> [!NOTE] |
| 37 | +> In the [WCAG 2.0](https://www.w3.org/TR/UNDERSTANDING-WCAG20/visual-audio-contrast-contrast.html) standard, contrast requirements only applies to text. For greater accessibility, consider the upcoming [WCAG 2.1 contrast guidelines](https://www.w3.org/TR/WCAG21/#non-text-contrast) for essential user interface components like icon buttons. A minimum ratio of 3:1 is recommended for these components. The guidelines descibed in this section are **optional** for WCAG 2.0 compliance. |
| 38 | +
|
| 39 | +### User interface components |
| 40 | +All interactive controls must have adequate color contrast between: |
| 41 | +* **[FocusedBorderColor](controls/properties-color-border.md)** and color outside the control |
| 42 | + |
| 43 | +Additional color contrast checks apply for controls where the entire area is interactive or informative. For example, a **[Button](controls/control-button.md)** or an **[Icon](controls/control-shapes-icons.md)** used as a button. This ensures that the boundaries of the control are clear and users know where they can click or tap. |
| 44 | + |
| 45 | +If there is a border for such controls, there should be adequate color contrast between: |
| 46 | +* **[BorderColor](controls/properties-color-border.md)** and color outside the control |
| 47 | +* **[PressedBorderColor](controls/properties-color-border.md)** and color outside the control |
| 48 | +* **[HoverBorderColor](controls/properties-color-border.md)** and color outside the control |
| 49 | + |
| 50 | +If there is no border, there should be adequate color contrast between: |
| 51 | +* **[Fill](controls/properties-color-border.md)** and color outside the control |
| 52 | +* **[PressedFill](controls/properties-color-border.md)** and color outside the control |
| 53 | +* **[HoverFill](controls/properties-color-border.md)** and color outside the control |
| 54 | + |
| 55 | +### Graphical objects |
| 56 | +If an image conveys important information, consider checking it for contrast issues. This applies to controls where an image can be shown: **[Audio](controls/control-audio-video.md)**, **[Image](controls/control-image.md)**, **[Microphone](controls/control-microphone.md)**, and **[Video](controls/control-audio-video.md)**. |
| 57 | + |
| 58 | +For video content, consider checking it for contrast issues. Alternatively or additionally, provide [closed captions](controls/control-audio-video.md) that describe the video. |
| 59 | + |
| 60 | +## Provide other visual cues |
| 61 | +Ensure that the app does not convey information with just color. For example, users with red-green color blindness will not be able to distinguish a red error message from a green success message. |
| 62 | + |
| 63 | +Additional cues like an **[Icon](controls/control-shapes-icons.md)** or text styles like **[Italic](controls/properties-text.md)** and **[Underline](controls/properties-text.md)** can help convey meaning. |
0 commit comments