My father-in-law is a webmaster. We were browsing McMaster and I asked him what it would cost to build it today. I will never forget his answer…
“We can’t, we don’t know how to do it”
It's WCAG canon that 320 px is equivalent to 1280 at 400% (the low vision support threshold), but in the modern web, I can tell you from experience, that isn't always the case!
Design responsive-ly, and test inclusive-ly!
Responsive layouts aren’t just for mobile! They also help users who zoom content or use keyboards on small devices. Make sure your design works at 320px wide. #WebAIM25#a11yTips
Responsive layouts aren’t just for mobile! They also help users who zoom content or use keyboards on small devices. Make sure your design works at 320px wide. #WebAIM25#a11yTips
Public service announcement: You should be aware of a pretty elaborate phishing scam using AI voice that claims to be Google Support (caller ID matches, but is not verified)
DO NOT CLICK YES ON THIS DIALOG— You will be phished
They claim to be checking that you are alive and that they should disregard a death certificate filed that claims a family member is recovering your account. It's a pretty elaborate ploy to get you to allow password recovery. The dead giveaway is the "Device" field here.
Whoever designed this at Google should really do even basic regex and/or LLM-based fraud detection on this text field. It's trivial to check the Device name for this.
Although Nintendo games are often accessible by design, the compnay's hardware and system options need a lot more work.
With the Switch 2 coming, it's time for them to finally start taking accessible hardware seriously. https://t.co/vnGtUNVC6b
@karlgroves@IAAPOrg Funny because the IAAP - of all orgs - should know that an accessibility professional isn't just gonna let something drop or be ignored without a fight.
Period reminder that "wrapping the <label> around the <input> is fine, and is sufficient for conformance on its own, however adding explicit association with` for` and `id` is still necessary in practice."
Details: https://t.co/FIzvHyXXyR
#a11y#HTML
Just realised a similar bug affects lazy loading: https://t.co/Ykv0xtQcJ3
All in all:
- `loading` must come before `srcset` + `src`
- `sizes` must come before `srcset`
- `srcset` must come before `src` [^1]
These bugs affect imgs created with JavaScript (in our case via React).
PSA for anyone using `srcset`: Safari has a bug where it downloads the largest source regardless of `sizes` if `sizes` appears after `srcset`.
This explains why we were seeing one page download 11 MB of images in Safari compared to 1 MB in Chrome. 🤯
https://t.co/qR8pDtGCgu