Twitter | Search | |
This is the legacy version of twitter.com. We will be shutting it down on 15 December 2020. Please switch to a supported browser or device. You can see a list of supported browsers in our Help Center.
Ryan Florence
and . Work hard, be kind, help others.
60,853
Tweets
3
Following
97,335
Followers
Tweets
Ryan Florence 1h
Replying to @mpv
I know some turn off their display because their batter lasts twice as long that way.
Reply Retweet Like
Ryan Florence 4h
Replying to @ashr
Some people can’t use a keyboard but can use a mouse! Others need something like a mouse (like the Xbox accessible controller). There are no “right” input devices
Reply Retweet Like
Ryan Florence 6h
Replying to @jhicks154 @jhooks
Can't remember, we had two workshops that week, one was really far south almost at the bottom, the other was north of London. Lots of trains!
Reply Retweet Like
Ryan Florence 6h
Replying to @jhooks
I ate dinner at a pub that had been open since the 1600s in the UK once. My brain couldn't handle that idea. Even just the buildings being that old just doesn't compute.
Reply Retweet Like
Ryan Florence 8h
Replying to @rleggos
Cool. My goal here is to help people who care about building a great UX realize that accessibility isn't a different category of UI development: it's in their lane, learn it, implement, make it happen!
Reply Retweet Like
Ryan Florence 8h
Replying to @rleggos
Eh, that's not at all what I mean. I mean the job isn't done until its more accessible, and that people should stop thinking of accessibility as a separate thing where you can draw a line and say "Alright, the UX is done, now maybe we'll get to accessibility".
Reply Retweet Like
Ryan Florence 9h
Replying to @ryanflorence
You hear: "Keyboard accessibility" "Screen reader accessibility" But: "mouse accessibility" (?) I've never heard anybody say that because it's the default, so we lump the others into a special "accessibility box". But it's all just UX, only a matter of who you thought of.
Reply Retweet Like
Ryan Florence 9h
Replying to @DavidKPiano
Yes! This UX isn't some special "accessibility" thing. It's just UX. We just lump "accessibility" into stuff we don't use ourselves, like an aria live region announcing errors in the field you just blurred. But as soon as we want that UX, we just consider it UX. It's all UX!
Reply Retweet Like
Ryan Florence 10h
Replying to @ryanflorence
I remember building a drop down menu that didn't have mouse event handlers. I started with keyboard events, and just never used my mouse with it. Almost shipped it when somebody else used it and was like "this thing doesn't work at all?" 😂
Reply Retweet Like
Ryan Florence 10h
You could build a fully functional UI that's a blank page, but works perfectly for keyboard + screen reader users. But the app isn't accessible, not to visual mouse users. There's no line where UX ends and a11y begins. It's all UX. I think of accessibility as UX I don't use.
Reply Retweet Like
Ryan Florence 10h
For real though, I'd the crap out of that UI and pretty much all incidental complexity melts away.
Reply Retweet Like
Ryan Florence 10h
Now do it with only the DOM APIs instead.
Reply Retweet Like
Ryan Florence Dec 4
Replying to @rileyflorence0
Problem is dad would think both of those are "be a jerk"
Reply Retweet Like
Ryan Florence Dec 4
Reply Retweet Like
Ryan Florence Dec 4
Replying to @kentcdodds @TestingLib
When I lived in Rexburg there was a bed place called "The Bed Place". Every time I drove by it made me chuckle.
Reply Retweet Like
Ryan Florence Dec 4
Replying to @freezydorito
IN CSS BUTTON ACTIVATES YOU
Reply Retweet Like
Ryan Florence Dec 4
Replying to @kentcdodds @npmjs
Reply Retweet Like
Ryan Florence Dec 4
Replying to @rileyflorence0
I wonder if anybody calculated estimated brand dilution vs. vbucks revenue 😂
Reply Retweet Like
Ryan Florence Dec 4
Replying to @_developit
fine, margin-bottom: -1px;
Reply Retweet Like
Ryan Florence Dec 4
Replying to @cullophid
That single frame bump will be so much smoother! 😆
Reply Retweet Like