
HTML in Canvas
I am interested in this as I always expected it to happen at some point, but appreciate that in this proposal (and experimental implementation) content drawn to the canvas is expressed in the canvas sub-DOM as HTML which makes it usable by assistive tech. I don’t envisage, or found in limited testing, any issues for Screen Reader software. I don’t know how robustly it works with screen magnifiers, so I contacted a former colleague at Vispero and asked them to get their technical folk to review and feedback.
Need a clarification of color requirements for images *with* text
The argument (by authority), put forward by one commenter on this discussion, I find bizarre and totally disagree with:
The commenter makes the following claim:
Image of text only applies to an image that only contains text.
Otherwise it is “text in an image” and follows other rules – like alt text.
source: https://github.com/w3c/wcag/discussions/5012
Take this as an example: An image containing only text fails WCAG 2.2 SC 1.4.3 as the text contrast in the image does not meet the contrast requirements
![]()
<img src="textimage.jpg" alt="A stylish but illegal monkey wandering around in Toronto IKEA">
If a separate image is added that is the subject of the text, the text still fails.
![]()

<img src="textimage.jpg" alt="A stylish but illegal monkey wandering around in Toronto IKEA"> <img src="stylishMonkey.jpg" alt="A monkey wearing a puffy wool jacket">
Now if the 2 images are combined (a single image with both text and picture) according to the commenter the image of text is no longer required to conform to WCAG 2.2 SC 1.4.3 contrast:

<img src="textimage+stylishMonkey.jpg" alt="A stylish but illegal monkey wandering around in Toronto IKEA text above a picture of the stylish but illegal monkey wearing a wool jacket.">
My reaction to this claim continues to be: what a load of bollocks which is why I have not commented on the discussion, as yet I find it impossible to fathom the reasoning, others may have a more measured response…
Make of this what you will:
WCAG 3.0 Working Draft — Comment on Autonomous Agents as Primary and Proxy Users
I have developed the AGAG — Agent Accessibility Guidelines — a dual-legibility framework extending WCAG 3.0 to explicitly include autonomous agents as first-class users. AGAG v1.0 organizes guidance around six pillars that map directly to the POUR principles: Detectable, Observable, Navigable, Economic, Verifiable, and Consent & Control.
Lyrics
Lancelot Link, Secret Chimp! He stands for justice. He has no fear. He's the agent to call when trouble is near. Lance Link, ya gotta come through. Everybody at APE is countin' on you! Here's pretty Mata Hairi, an agent and friendly. She'll stick by his side right to the end. Darwin is the leader on the side of good. He fights CHUMP agents like a good ape should. Oh, Lance Link, whatcha gonna do? You gotta stop CHUMP! The job is up to you! Here's Baron Von Butcher; you better beware! He's ruthless and he's cunning and he don't play fair! He's got an evil chauffeur, and Creto's his name. And Dragon Woman's lovely, but she's wicked all the same! Oh, Lance Link, whatcha gonna do, When mad Dr. Strangemind comes up to you? There's Ali Assa Seen, and wicked Wang Fu, And The Duchess, whose looks can really fool you! Whoa, Lancelot Link, Secret Chimp! He stands for justice, he has no fear, He's the agent to call when trouble is near. Lance Link, whatcha gonna do?!
