Issue #21
Featured: The inaccessible web: how we got into this mess
Mischa Andrews explains just how the Web became and becomes so inaccessible. Plus, she offers some thoughts on the path toward a more inclusive Web.
Read more in The inaccessible web: how we got into this mess.
News and links
Web Standard spec writers draft Accessibility Object Model: From the project, “This effort aims to create a JavaScript API to allow developers to explore and modify the accessibility tree for an HTML page.”
Resources, tools and tutorials
- Accessible language pickers (blog post)
- What does accessibility supported mean? (blog post)
- Accessibility for all (podcast)
- Computer Vision API: What does it see? (blog post)
- Wa11y (resource)
- Making accessible links: 15 golden rules for developers (blog post)
- Button design best practices (blog post)
- How to create a culture of accessibility (blog post)
- Three things you should know before using VoiceOver for testing (blog post)
- Everything Apple Accessibility with Paul Adam (podcast)
- Pantsuit: The Hillary Clinton UI pattern library (tool)
- Introducing AccessLint CI - automated web accessibility testing (tool)
- Creating an accessible culture (blog post)
- Building in 10k: Markup for accessibility, clarity, and affordance (blog post)
- Screen reader compatibility for non-text content (resource)
New to A11y
Google has put together a free, six-week course on web accessibility, focused on developing with empathy, and it’s free on Udacity. (Last week’s issue had the wrong link, so this resource is repeated.)
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.