Featured: The curious case of “iff” and overriding screenreader pronunciations
“I’d like to propose a few steps one could take before using markup hacks to override screenreader pronunciations. If you’re dealing with your own case where you think a pronunciation override might be best, consider whether one of these options could work for you instead.”
News, resources, tools and tutorials
- Web and app ADA lawsuits: Six trends so far in 2023 (blog post - blog.usablenet.com)
- Vision Pro Development Kits offer captivating clues at the headset’s accessibility story (blog post - forbes.com/sites/stevenaquino)
- How to provide accessibility in your native Android app with Jetpack Compose, part 1 (blog post - thedroidsonroids.com)
- Legibility: How and why typography affects ease of reading (resource – legible-typography.com)
- Legal update: July 2023 (blog post – convergeaccessibility.com
- WebAIM’s WCAG 2 checklist (updated for 2.2) (resource – webaim.org)
- Accessibility represents maturity (blog post – tempertemper.net
- Accessibility of the button: Should we fix it or the root cause problem? (blog post – deque.com)
- CSS and accessibility: Inclusion through user choice (blog post – smashingmagazine.com
- Odd Contrast (tool – oddcontrast.com)
- Just normal web things. (blog post – heather-buchel.com
New to A11y
Whitney Lewis covers eight common heading questions, many of which have come many times in my own work. I’m a big fan of articles like this because it brings content and accessibility to the forefront. Accessibility isn’t just about the technical bits. Content matters too.
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 firstname.lastname@example.org.
Sponsorships and donations
You can sponsor Accessibility Weekly! If you or your company is interested, send a note to email@example.com.
If you enjoy the newsletter, consider making a donation.