An Early History of Web Accessibility #a11y
So has accessibility now gone mainstream because of Beyoncé's (inaccessible) website? Well, better late than never. #a11y
Hi aspiring #a11ycats! If you can’t afford to take my @skillshare class on accessibility, I am happy to provide you with a code so you can watch it for free.
In return I ask that you write an *honest* review and share the class with your peers!
Also: “Spend money on training, not (only) QA.” @firstname.lastname@example.org
"Spend money on access, not lawyers." @LFLegal
Hey. @Medium@twitter.com is not the place to put #a11y writing. It does not support image alt text. Please stop (using Medium).
“Accessible” Design Systems Don’t Guarantee Accessible Products:
Accessibility is an Adopter’s Job Too, and They’ve Got Work To Do
A reminder to all to check out the fantastic articles being posted on 24 Accessibility this month. So many wonderful and inspiring reads about digital inclusion and accessibility!
After examining bunches of web sites and their keyboard support, @email@example.com confirms it’s a mess out there. https://www.24a11y.com/2018/i-threw-away-my-mouse/
If you manage developers, don't keep sending accessibility issues to your specialists to fix. The best thing you can do is share those tasks across entire dev team. The greener the dev, the better. It is the only way they will learn and future work will be better for it. #a11y
Web Rumble! According to @dequesystems aXe, @foxnews home page has 312 #a11y issues, while @CNN has 118. Page weight ~2MB for both. However, Fox works well when JS is disabled. CNN renders header and footer only. Winner, while painful to say: @foxnews PE FTW! Work on a11y tho!
WCAG IS DEAD. LONG LIVE WCAG! 😜
WCAG 1.0 will be marked superseded by the end of the year. WCAG 2.1 is a nice and important modern update to WCAG 2.0.
If you always wanted to get into accessibility, this is a great time.
“I have resigned as the WordPress accessibility team lead. Here is why.”
Hm. As browsers currently drop elements with display contents from the accessibility tree, rendering your content inaccessible, I’d say: Not at all for now.
(Write to your browser vendor to fix that bug!)
♠ “When to use display:contents to improve semantics in your HTML.” Working with CSS Grid occasionally come at a cost and that is semantic markup.
'“Sysadmin” is just another way to say “professional patcher.” It’s like you’re a roofer, but indoors and with different tar.' - #fmjail
New blog post:
“Conferences, Speakers: Please Caption Your Videos”
👉 Your dose of curate weekly links: accessibility tools for colors, to design for colorblind, accessibility general tips, CSS and HSL, CSS grid area, notifications and UX, building design systems and more. https://stephaniewalter.design/blog/pixels-of-the-week-november-11-2018/
Hey there! Just a reminder that there is a Mastodon instance dedicated to accessibility! Join us!
Bad Practices on Phone Number Form Fields >> hum, I don't think you should rely on geolocation to guess phone number country prefix. Current user location might not be the same as prefix (holidays, working in another country) :/ https://uxmovement.com/forms/bad-practices-on-phone-number-form-fields/
Standards-based web developer, designer, accessibility specialist and consultant in Allentown, PA.
An open community for those interested in learning more about digital accessibility.