You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: success-criteria-problematic-for-closed-functionality.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -31,7 +31,7 @@ For non-web software on ICT with closed functionality, those who implement this
31
31
<li><ahref="#non-text-contrast">1.4.11 Non-text Contrast</a> — There are cases where applying this success criterion to non-web software on ICT with closed functionality is problematic:
32
32
<ul>
33
33
<li>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.
34
-
<divclass="note">Hardware requirements for contrast are out of scope for WCAG2ICT (and this success criterion).</div></li>
34
+
<divclass="note">Contrast requirements for hardware are out of scope for WCAG2ICT (and this success criterion).</div></li>
35
35
<li>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.
36
36
<divclass="note">Photographs 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.</div></li>
0 commit comments