Issue #511
Featured: Use cases for aria-expanded
“This article is intended to help you more easily determine whether aria-expanded has been used correctly or not. It’s not about how to implement every pattern discussed here in a production environment! However, in each section, I’ve included additional links so you can dive deeper into the topic.”
Read more of Use cases for aria-expanded.
Sponsored: Put your “unable to determine” contrast results to rest
Run a contrast scan and a big chunk of the results come back as needs-manual-review, because the scanner can’t reason about gradients, background images, opacity, or layered elements. AAArdvark’s AI-powered contrast checker analyzes what’s actually rendered on screen and confirms roughly 80% of those flagged issues as a clear pass or fail. Filter down to the handful that genuinely need a human eye, and skip the hours of manual spot-checking on the rest.
See how the AAArdvark contrast checker works
News, resources, tools and tutorials
- Bringing the automated scanning series together (Part 4) (blog post - convergeaccessibility.com)
- June 2026 A11y Book Club recap | Digital Accessibility Ethics (video - youtube.com)
- Google docs makes accessible links easier: A small feature with big accessibility benefits (blog post - equalentry.com)
- Does your screen reader content need an editor? (blog post - intopia.digital)
- Designing for distressed users: Why mental health apps shouldn’t follow every UI fashion (blog post - smashingmagazine.com)
- Design systems are no longer optional (blog post - mandy.dev)
- The perfect cripple: A user guide to being palatable (blog post - salient.org.nz)
- 98% isn’t very much (blog post - whynothugo.nl)
- A11y 101 (blog post - tarnoff.info)
- Testing methods: Error suggestion (blog post - dennisdeacon.com)
- Link + popover navigation (blog post - adrianroselli.com)
Sponsored classifieds
From “inaccessible” to inclusive: A practical PDF remediation demo via webinar recording: Learn all about PDF tagging and how to remediate PDFs for accessibility in Acrobat Pro.
The ADA Title II deadlines moved, but your liability didn’t. Improve WCAG testing and management. Start your 14-day free trial of Accessible Web’s RAMP today!
Benchmark your accessibility program in under 4 minutes with this Maturity Model. Get a personalized roadmap to get to the next level.
New to A11y
Erik Kroes talks about how (not to) name things in accessibility. A short post with an important lesson on semantics. HTML already knows the “type,” of control, you need name it in a way that explains what it does.
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.