Success Criterion 1.4.6 Contrast (Enhanced) (Level AAA)

[maryjom]

1.4.6 Contrast (Enhanced)

(Level AAA)

The visual presentation of text and images of text has a contrast ratio of at least 7:1, except for the following:

Large Text

Large-scale text and images of large-scale text have a contrast ratio of at least 4.5:1;

Incidental

Text or images of text that are part of an inactive user interface component, that are pure decoration, that are not visible to anyone, or that are part of a picture that contains significant other visual content, have no contrast requirement.

Logotypes

Text that is part of a logo or brand name has no contrast requirement.

Applying SC 1.4.6 Contrast (Enhanced) to Non-Web Documents and Software

This applies directly as written, and as described in Intent from Understanding Success Criterion 1.4.6.

---

For WCAG2ICT consideration: Doesn't seem that any additional notes are needed. Comment on the issue if something should be added.

---

[maryjom]

Looking further at this, 1.4.3 Contrast (Minimum) has significant content in the SC problematic for Closed Functionality which are exactly the same. So at the very least, we'd have to repeat this info for 1.4.6 and have a Non-web software note on Closed Functionality.

For non-web docs and non-web software that isn't closed, this would apply as written.

[pday1]

SC problematic for Closed Functionality has the following comments for 1.4.3 in current editor's draft:

1.4.3 Contrast (Minimum) — There are cases where applying this success criterion to non-web software on ICT with closed functionality is problematic:
When the contrast of the content is determined by the hardware and not modifiable by the software author, it may not be possible to meet this success criterion.
NOTE 1
Contrast requirements for hardware are out of scope for WCAG2ICT (and this success criterion).
When the color contrast ratio cannot be programmatically measured due to system limitations (e.g. lockdown), precise quantifiable testing of color contrast cannot be performed by a third party. In such cases, the software author would need to confirm that the color combinations used meet the contrast requirement.
NOTE 2
Photographs (e.g., of a hardware display) are not sufficient for testing that content meets this success criterion. This is because the quality of the lighting, camera, and physical aspects of the hardware display can dramatically affect the ability to capture the content for testing purposes.

[pday1]

Suggested content for SC 1.4.6 in Comments on Level AAA Success Criteria.

Applying SC 1.4.6 Contrast (Enhanced) to Non-Web Documents and Software

This applies directly as written, and as described in Intent from Understanding Success Criterion 1.4.6.

NOTE (FOR NON-WEB SOFTWARE)
See also the Comments on Closed Functionality.

--
Suggested content for SC 1.4.6 in Success Criteria Problematic for Closed Functionality. This replicates exactly what we had for 1.4.3 Contrast (Minimum).

1.4.6 Contrast (Enhanced) - There are cases where applying this success criterion to non-web software on ICT with closed functionality is problematic:
When the contrast of the content is determined by the hardware and not modifiable by the software author, it may not be possible to meet this success criterion.
NOTE 1
Contrast requirements for hardware are out of scope for WCAG2ICT (and this success criterion).
When the color contrast ratio cannot be programmatically measured due to system limitations (e.g. lockdown), precise quantifiable testing of color contrast cannot be performed by a third party. In such cases, the software author would need to confirm that the color combinations used meet the contrast requirement.
NOTE 2
Photographs (e.g., of a hardware display) are not sufficient for testing that content meets this success criterion. This is because the quality of the lighting, camera, and physical aspects of the hardware display can dramatically affect the ability to capture the content for testing purposes.