Issue #177
Featured: First public working draft: WCAG 2.2
The Accessibility Guidelines Working Group has published a first public working draft of Web Content Accessibility Guidelines (WCAG) 2.2.
Read First public working draft: WCAG 2.2.
News, resources, tools and tutorials
- Accessible content – Part 5: Accessible graphics (blog post – accessabilly.com)
- MIT to caption online videos after discrimination lawsuit (blog post – pbs.org)
- Why 543 KB keep me up at night (blog post – matuzo.at)
- Cross-cultural design (blog post – alistapart.com)
- Why the GOV.UK Design System team changed the input type for numbers (blog post – technology.blog.gov.uk)
- Cleaning our way to accessibility (blog post – accessibility.blog.gov.uk)
- HTML: The inaccessible parts (blog post – daverupert.com)
- Decoding label and name for accessibility (article – webaim.org)
- Accessibility dont’s, learn from basic mistakes in web design (blog post – pineco.de)
- Online altruists are making Reddit more accessible (article – wired.com)
- Stop using ‘drop-down’ (blog post – adrianroselli.com)
- More accessible defaults, please! (blog post – hiddedevries.nl)
New to A11y
Sarah Higley takes a deep dive into why focus management still matters. This post goes into some of the lesser known reasons behind why things work the way they do, and what browsers need to account for. It’s fscinating, and a good introduction to how complicated accessibility can be for someone new to it.
Suggestions and corrections
Have a suggestion for something to be included in Accessibility Weekly? Did I make a mistake that doesn't belong on the Internet? You can either reply to this email or send a note to hello@a11yweekly.com.
Sponsorships and donations
You can sponsor Accessibility Weekly! For details, check out the sponsor page. If you or your company is interested, send a note to hello@a11yweekly.com.
If you enjoy the newsletter, consider making a donation.