MAiD, ableism, cognitive accessibility, and more
Nic Steenhout about MAiD (the Canadian euthanasia program), improving for cognitive disabilities. and more!
Accessibility
Accessible design is digital infrastructure
By the always inspiring @annaecook@mastodon.social
Wishcessibility - Nic Chan
The brilliant @NicMakesStuff@indieweb.social on how good intentions can make stuff inaccessible.
A word with the accessibility egg – Eric Eggert – HTML Accessibility
So happy to sit with @SteveFaulkner@mastodon.social and talk about accessibility. It was a pleasure. (Transcript available.)
Accessibility For Everyone by Laura Kalbag
This essential book by @laura@mastodon.laurakalbag.com is now available for free. Relevant as ever. Read it!
Why I Don’t Call Myself an Accessibility Expert
I (@yatil@yatil.social) think this is a narrow definition of expert that includes completeness of knowledge. I think an exert knows what they don’t know and when research is important. It’s time that accessibility experts are proud to have the expertise.
You probably shouldn’t be annotating focus order
There are important accessibility annotations but in many cases developers should pick appropriate (usually the default) interactions. @eric@social.ericwbailey.website on annotating focus order in particular.
Common misconceptions about testing accessibility - TetraLogical
Testing for accessibility is often misunderstood. Teams either overestimate what tools can do, underestimate their own role, or assume testing is something that happens once only, at completion of the development process. In this post we tackle some of the most frequent misconceptions about accessibility testing.
Accessible faux-nested interactive controls
@eric@social.ericwbailey.website explains how to do nested controls that look nested but are not nested. It’s a clever technique I use all the time, too!
Live Region Support
@aardrian@toot.cafe investigates the support for live regions
Designing accessibility for real use, not dashboards
In this article, @annaecook@mastodon.social explains the phenomenon of putting work, especially accessibility work, in quantifiable metrics. This often creates bad incentives.
5 accessibility checks to run on every component - zeroheight
As important as testing whole sites and processes is, a lot of issues can be caught with simple tests when testing individual components, as @hdv@front-end.social shows in this article.
You Can't Opt-Out of Accessibility
By @vale@fedi.vale.rocks
After years and years of successive abstractions, we have prioritised the comfort of the person writing the code over the survival and agency of the people using it. Innovation that excludes people isn’t innovation; it’s just shiny exclusion.
How Button Traits can make a chaotic iOS app accessible | Axess Lab
Great article by my colleague Diogo Melo.
Meeting WCAG is an achievement
Let’s not talk ourselves down. By @yatil@yatil.social
You Can’t Make Something Accessible to Everyone
By @aardrian@toot.cafe.
Can AI write accessibility specs?
Great article by @gerireid@social.design.systems. The answer to the question in the title is “no”, but the process to getting there is interesting.
Simple One-Time Passcode Inputs
So simple and yet so powerful. HTML is great!
By @tylersticka@social.lol
Toasts | Primer
GitHub no longer uses toasts because of their accessibility and usability issues.
A powerful rebuttal of the “Toast” paradigm.
Common misconceptions about screen readers
By TetraLogical’s Ela Gorla.
Stop inviting overlay employees & bad actors into Accessibility spaces
By Chris Yoong.
100% agree!
A threat model for accessibility on the web
@sundress@eigenmagic.net with an excellent article about accessibility and why and how it is so neglected.
WCAG’s Longevity · Eric Eggert
I, @yatil@yatil.social, wrote about WCAG’s longevity and audio descriptions.
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.
Screen readers do not need saved by AI
Great article by @craigabbott@a11y.info
Empowering humans to communicate in a more accessible way prevents the problem at its source, avoiding the need to rely on expensive, unreliable machines to try and patch it in real-time afterwards.
About “best practices”
By @yatil@yatil.social
The first thing I noticed when reading his piece is that how he experienced the term is different from how I have. Which means we’re off to a good start. 😃
"Best practice" is just your opinion
@craigabbott@a11y.info about the term “best practice”