Accessibility specialist and blogger. I post links to my articles here; if you have any questions I'd love to hear from you on Bluesky, Mastodon, or LinkedIn.
Every idea comes from a good place, but some well-intended features are actually bad for usability; limiting form field input is one of those things ✍️ https://t.co/QcUp4NT7Fk #accessibility#a11y
The whole point of VoiceOver is that it talks out loud, but sometimes you need it to be quiet for a moment… Here's how to get it to shut up when you need 📷 https://t.co/50iMJIBc2Q #accessibility#a11y
In order to make my website’s keyboard focus outlines pretty in Safari, I had inadvertently broken things for people who use Windows High Contrast Mode with the keyboard alone… ✍️ https://t.co/d6aSygLCvB
#a11y#accessibility
When an interactive element like a button, link, or form field sits on top of another interactive element, accessibility (and usability) problems arise ✍️ https://t.co/XEvCgvxN44 #accessibility#a11y
‘Alt’ text is vital for people who can’t see an image, but what about those who don’t use a screen reader but still struggle with low contrast images? ✍️ https://t.co/FrfGKLIAYr #accessibility#a11y
Day 26 of #A11yAdvent - confused about when to use html section elements?
@tempertemper gives a good explanation about how to make them accessible in this blog post https://t.co/My3c9Y7chY
@BlvckGodPsalmie Haha I stand all day long! Took a bit of getting used to, but sitting down to work feels weird now 🙃
Was great to meet you and the rest of the class!
@vavroom Yeah I guess so, having just re-reading Understanding too. As long as you can spot what has focus, consistency isn’t vital to use.
Raises an interesting question on the Understanding stuff though – I feel like sometimes it’s use to explain/frame, but that’s the SC itself’s job.