Toasts | Primer
GitHub no longer uses toasts because of their accessibility and usability issues.
A powerful rebuttal of the “Toast” paradigm.
How I, a non-developer, read the tutorial you, a developer, wrote for me, a beginner
By @annie@social.lol – This must be like non-accessibility people read accessibility advice when things are not properly explained!
Custom Carets and Users: When The Caret Is No Longer a Stick (Yes, That’s a Poor Attempt at a Pun)
@aardrian@toot.cafe shining light on a new CSS property with accessibility implications
I’d feel better if the CSSWG did a better job of outlining risks and best practices, at least beyond stale WCAG links and suggestions that user style sheets are the best approach to get around forcing animations on users. Granted, the CSSWG had shown a certain amount of ignoring the Priority of Constituencies of late, so I’m also not terribly surprised.
Taking a shot at the double focus ring problem using modern CSS
@eric@social.ericwbailey.website with the goods regarding the double focus ring!
forced-color-adjust: none is an unavoidable foot gun | Sarah Higley
A very long treatise on why text backplates were a bad idea. Most of the time.
My Request to Google on Accessibility
By @aardrian@toot.cafe
Please, if your team cannot explain how the thing satisfies all WCAG Success Criteria at Level AA, then don’t release the thing.
If the thing is a new feature for the web platform (HTML, CSS, ARIA, SVG, etc.), then don’t even propose the thing until you have its WCAG conformance sorted.
The true path to garbage code: Figma Sites
By @joedolson@toot.io
The Accessibility Blame Game: The Fallacy of the "Lazy Developer"
In the digital accessibility industry, a pervasive narrative persists: "If only developers cared more about accessibility..
Accessibility Is Easy … Except for When It Isn’t | State of the Browser 2023 | Presentations | A11y Tools
By @lloydi@mastodon.social