Wrote an article about my experience designing reorderable lists and some considerations for making them as usable as possible.
https://t.co/W1NPK7gKYE
Haven't really been on here lately, but probably not coming back, at least not in Twitter's current form.
If you want to keep up with me, find me at my personal website or on the Elephant network (both linked in my bio).
Noticed a usability detail on a Japanese beer can: a small cavity in the lid under the pull tab that lets you more easily grip and open it.
My big fingers def found it helpful.
I’d be curious to hear if ppl who normally have trouble opening this type of can find it helpful.
@mmatuzo@openuicg@Una Oddly, I can’t see your tweet now either, though I did see it yesterday with no issues. I can see the one you quote tweeted, but not if I go to Una’s tweet. Maybe Twitter bugs?
The `aria-description` prop is going to have full browser support soon, so I did a little dive into it & its current level of support:
https://t.co/L85aW4X0EX
@jh3yy@alvaro_montoro An alt attr w/ an empty string as its value and a missing alt attr have different effects. The former hides the img from assistive tech. The latter will, depending on the browser/AT, result in either the file's name being announced or something like "unlabeled graphic".
@jensimmons The ability to directly transition/animate the width and height of elements to or from any value performantly (including “auto”) without needing to hack it with wrappers, transforms, etc.
Started an article series where I'll attempt to build a drag-and-drop interface that makes sense for screen reader users. Let's see if I can do it.
Here's part 1, where I look at communicating that an element is draggable:
https://t.co/qzkIUoHgh3
After reporting it the WebKit team jumped on it fast, patching it in Safari 15.4 in just over a month.
Orig. bug: https://t.co/xPUPuXulZz
I'm critical of WebKit/Safari at times, but it was good to see them prioritize an accessibility issue & push a fix quickly. Credit to them.
In April I noticed a Safari bug where dynamic lists (<ul>, role=list) weren't given list roles in the a11y tree, causing VoiceOver to read them as generic text nodes.
If used for a todo list or shopping cart, VO users would get a clunky (at best) or broken (at worst) experience.
The question I still have is why Safari thinks a 24px font size wasn’t large enough in some cases and needed be to increased.
The table’s width seemed to play a part as well, but not sure how. Wider tables looked to have their <caption>’s font size increased.
Spent an hour debugging table <caption> elements that were displaying at different font sizes on iOS.
The culprit: CSS’s “-webkit-text-size-adjust” property, which was enlarging the font size for some and not others.
Setting the value from “auto” to “none” solved the issue.
AudioEye’s attorneys sent me a Cease & Desist letter (and a follow-up).
I have posted it along with my response:
https://t.co/2mUMyej6Xp
TL;DR: I deleted three tweets, considering I am a self-employed independent consultant, not a multi-million dollar start-up.