E-mail List Archives
Re: Is it ok to intentionally break WCAG 2.5.3?
From: Steve Green
Date: Aug 20, 2022 1:09PM
- Next message: glen walker: "Re: Is it ok to intentionally break WCAG 2.5.3?"
- Previous message: Patrick H. Lauke: "Re: Is it ok to intentionally break WCAG 2.5.3?"
- Next message in Thread: glen walker: "Re: Is it ok to intentionally break WCAG 2.5.3?"
- Previous message in Thread: Patrick H. Lauke: "Re: Is it ok to intentionally break WCAG 2.5.3?"
- View all messages in this Thread
More generally, the WCAG definition of text is "sequence of characters that can be programmatically determined, where the sequence is expressing something in human language" and human language is defined as "language that is spoken, written or signed (through visual or tactile means) to communicate with humans".
https://www.w3.org/WAI/WCAG21/Understanding/label-in-name.html#dfn-text
https://www.w3.org/WAI/WCAG21/Understanding/label-in-name.html#dfn-human-language
This explains why "aA" is not considered to be text. Likewise, an "x" character is not text when used as a "Close" button, so that would not fail SC 2.5.3. The same applies in other scenarios, such as "i" icons for information popups.
A further consequence is that the non-text colour contrast requirement of 3:1 applies to those characters, not the 4.5:1 ratio required for text.
Steve Green
Managing Director
Test Partners Ltd
- Next message: glen walker: "Re: Is it ok to intentionally break WCAG 2.5.3?"
- Previous message: Patrick H. Lauke: "Re: Is it ok to intentionally break WCAG 2.5.3?"
- Next message in Thread: glen walker: "Re: Is it ok to intentionally break WCAG 2.5.3?"
- Previous message in Thread: Patrick H. Lauke: "Re: Is it ok to intentionally break WCAG 2.5.3?"
- View all messages in this Thread