This links to my post about Enter / Space behavior on a native button:
https://css-tricks.com/explaining-the-accessible-benefits-of-using-semantic-html-elements/
My post also reminds about WHCM.
Also, he cites a disabled state…
@… I somehow missed this crucial piece of web components lore but I also found it https://marcysutton.github.io/accessibility-of-web-com…
False choice (with a value judgment in its wording).
You can, & should, continue to raise demonstrable & valid concerns about the accessibility of LLM output and _also_ consider if (or how) you can improve it (he offers options).
But no free labor from me.
https://www.
I think I’m more offended it attributes a metaphor to me that I can find no record of me saying or writing.
https://elementor.com/blog/web-accessibility-myths/#myth-6-overlays-or-plugins-are-enough-to-make-my-site-accessibl…
Me, a hammer salesman: “Let's fix that window, you know, for accessibility.”
[ smashes glass ]
you: “Why did you do that?”
me: “For accessibility.
you: “It wasn’t broken.”
me: “I made it better for accessibility.
you: “But how does th—”
me: “FOR ACCESSIBILITY!”
[ waggles hammer overhead ]
TIL: The Japanese Blind ICT Network (JBICT) runs AT surveys (kind of like WebAIM’s).
#accessibility
My loose process for evaluating an ACR (VPAT®):
https://adrianroselli.com/2026/01/how-i-evaluate-an-acr-vpat.html
You may have your own thoughts / ideas. Add them to the comments.
I was also torn between the meat grinder and a Plinko metaphor.
I appreciate posts that give approaches with reasoning:
https://www.a11y-collective.com/blog/visually-hidden/
But I wish these posts would reference prior art, such as:
• Scott’s
424-word hot take: “You Can’t Make Something Accessible to Everyone”
#accessibility