Featured: Should I use a button or a link?
“The answer is straightforward, and I think it’s only contentious when there is lack of consideration of why links and buttons both look different and behave in completely different ways.”
Read more of Should I use a button or a link?.
News, resources, tools and tutorials
- Six months with Android: A journey from a blind perspective (blog post – firstname.lastname@example.org)
- Giving your future self a little credit with progressive enhancement (blog post – pixotech.com)
- Here, here, and here (blog post - tempertemper.net)
- Visit for a surprise (blog post - ericwbailey.website)
- Neutrality isn’t an option when it comes to accessibility (blog post - karlgroves.com)
- ‘Accessibility at the Edge’ W3C CG Is an overlay smoke screen (blog post - adrianroselli.com)
- Comparing JAWS, NVDA, and VoiceOver (blog post - css-tricks.com)
- The accessibility and usability journey of Drupal’s primary navigation (blog post - smashingmagazine.com)
New to A11y?
The folks from Babylon Health have a guide on how to test with a screen reader that looks helpful. Many organizations and sites have similar resources, but I like to see what different design system teams like Babylon DNA put into their documentation.
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 email@example.com.
Sponsorships and donations
You can sponsor Accessibility Weekly! If you or your company is interested, send a note to firstname.lastname@example.org.
If you enjoy the newsletter, consider making a donation.