- From: Ms J <ms.jflz.woop@gmail.com>
- Date: Mon, 5 Feb 2024 13:13:26 +0000
- To: "w3c-wai-ig@w3.org" <w3c-wai-ig@w3.org>
- Message-ID: <DB4P250MB0927B799EDAA6D7E0EBCA288AE472@DB4P250MB0927.EURP250.PROD.OUTLOOK.COM>
Sorry for following up immediately, I just wanted to clarify that I didn't consider 1.1.1 because it is literally text content, but that does feel like a loophole has they are using it as non-text content: for its physical characteristics and not its semantic text meaning Thanks Sarah Sent from Outlook for iOS<https://aka.ms/o0ukef> ________________________________ From: Ms J <ms.jflz.woop@gmail.com> Sent: Monday, February 5, 2024 12:53:59 PM To: w3c-wai-ig@w3.org <w3c-wai-ig@w3.org> Subject: Unicode characters used as images Hello If I had a shopping list and each item had a 'cross' next to it to indicate it was completed but the unicode 'heavy multiplication x' character was used for the cross, is this a failure of any sc? They're basically using a text character like an image because they're using it for its physical characteristics, but they're not marking it up as an image (for example with an aria img role) and giving it an alt. It's read with JAWS as 'heavy multiplication x'. My thoughts are - could it fail name, role, value because it's used as an image but doesnt have that role? Could it fail info and relationships because it coveys information visually but not programmatically? (But then thats like saying images with unclear alts should fail 1.3.1) I don't think it fails sensory characteristics because there's no corresponding instructions that refer to it by its appearance Thanks Sarah Sent from Outlook for iOS<https://aka.ms/o0ukef>
Received on Monday, 5 February 2024 13:14:02 UTC