Issue #104
Featured: Accessibility is not a feature
Ethan Marcotte reflects on some of the language he uses to talk about accessibility – or, more specifically, to talk about the people he designs for.
Read Accessibility is not a feature.
News, resources, tools and tutorials
- Variable fonts and dyslexia (blog post – adrianroselli.com)
- Is placeholder text a sufficient accessible label for form fields (blog post – davidmacd.com)
- Challenges in measuring automatic transcription accuracy (blog post – medium.com/descript)
- Improving Basecamp’s accessibility - Interview with Michael Berger on how to make an existing web app more inclusive (blog post – marcus.io)
- The power of progressive enhancement (blog post – medium.com/no-divide)
- Accessible breadcrumb navigation pattern (code – scottaohara.github.io)
- Don’t use “click here” (blog post – medium.com/@heyoka)
- Axe-core gets WCAG 2.1 rules (blog post – deque.com)
- Conversational semantics (blog post – alistapart.com)
- Heading structures are tables of contents (blog post – hiddedevries.nl)
New to A11y
Henny Swan talks about the velvet rope of design. That’s the barrier a lot of people face when a user experience isn’t an accessible one. And as she points out, it’s about much more than design systems and standards.
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.