https://xitter.cf/t.co/dkYhRadEeD • Javascript developer and cat herder, working on #a11y at Microsoft. Longer form thoughts at https://xitter.cf/t.co/SAadixXpUa. She/her.

Seattle, WA
Joined March 2013
Good thread. Though not mentioned, I think accessibility fits squarely in this phenomenon — to value it, one must appreciate the complexity of the world we’re building for, and care about social good. Viewpoints antithetical to the sort of company these people want to run.
Replying to @uberpreeya
That's where the "incompetence" comes in. It's an owner class looking at products that have become far more complicated than they ever imagined, and going, "That can't possibly be right????"
1
7
Seems like a good time to convene a workhop on Mastodon basics. Blind and #a11Y allied folks - anyone actually - let's do this! nypl.zoom.us/meeting/registe…
3
20
25
Dear @Meetup: Alert! I've spoken at #Meetups in SF, Chicago, Toronto about digital accessibility + disability inclusion. It is SO DISAPPOINTING to find an overlay on your site. Please take it down ASAP if you care about Meetups being inclusive overlayfactsheet.com/ #a11y 1/2
2
10
1
18
For anyone here who wants to try mastodon but finds the whole process a bit much, I wrote a very simple step-by-step guide to starting up: sarahmhigley.com/writing/mas… Includes semantic descriptions and accessibility info on the signup process :)
1
8
2
36
Replying to @jaffathecake
It's confusing because sometimes the thing behind a flag is 'ready' to the point where we want developers to tell us everything that's wrong with it. But sometimes devs see that, say, a11y isn't correctly implemented, and assume we don't care about a11y. But it just isn't ready.
1
2
1
14
Just to clarify, I think a good-faith example of a v0 thing is it lacking features, or still having bugs — even accessibility bugs. A bad-faith “just isn’t ready” is a thing whose very design has fundamental unaddressed accessibility concerns.
1
7
These were very good slides 😊
This Post is from an account that no longer exists. Learn more
4
For those asking for my slides from the #A11YTO conference here they are! Sorry for the wait but I feel like I just literally got home with all the travel lately. bit.ly/3SS52gu
1
4
2
6
I had the most fun making this slide 😁
Thanks for the super engaging talk @codingchaos! So fun and informative! #a11ytoconf
2
1
11
I know how to do hosting. And words. 🙈
Replying to @codingchaos
@codingchaos gives the best instructions. 😂 #a11yTOconf
2
8
Love @annaecook killing her talk and calling out that ARIA often doesn’t need to be included in design accessibility annotations
2
30
“We shouldn’t hold back the web just because screen readers/assistive tech/ARIA aren’t there yet” has a subtext of: “I fundamentally see the web as a platform designed for sighted mouse users, that is then adapted for disabled people” which is, in fact, ableism.
5
81
4
280
I’ve never heard anyone suggest a core feature that only works for keyboard or screen reader users, but doesn’t work with a mouse. “We’ll roll out mouse support when mouse hardware and APIs improve”
1
15
2
50
That sounds ridiculous, but only because everything is so firmly centered around pointer access. People then assume assistive tech and accessibility apis are the problem, rather than that our entire approach to web design and the web platform is ableist.
8
36
Updated today: Quick(er) Note on ARIA and Windows High Contrast Mode scottohara.me/blog/2019/02/1… pruned out some outdated info, and provided an example of styling ARIA links and buttons with high contrast media queries (legacy -ms- and standard forced-colors)
Hiding content in alt text is not the point of alt text.
alt-text isn't a place to hide jokes 🙃
3
15
2
59