Issue #472
Featured: Why accessibility breaks between design and development
“By the time the product reaches QA, features that looked accessible on Figma suddenly fail real-world tests. Focus order behaves unpredictably. Screen readers miss entire sections. Captions overlap UI elements. Developers are left scrambling to fix what was once ‘already designed for accessibility.’”
Read more of Why accessibility breaks between design and development
Sponsored: Watch accessibility issues get fixed live
Join us Wednesday, November 5 at 1pm PST for a livestream where our founder Natalie will tackle accessibility issues in real-time. See the problem-solving, code fixes, and troubleshooting as we work through a site’s accessibility issues. Watch how Natalie works through the remediation process and handles the curveballs that come up when fixes aren’t straightforward. The session will be recorded if you can’t make it live.
Watch the livestream on YouTube.
News, resources, tools and tutorials
- ARIA and real world dangers (blog post - dennisdeacon.com)
- When to Use modal vs dialog components (interesting app - applevis.com/forum)
- What’s an interactive element? (blog post - matuzo.at)
- How a 3-minute a11y snapshot helps me turn curiosity into connection (blog post - pedalpoint.com)
- Video without vision (video – tab-able.co.uk)
- Swedish government starts to audit eCommence websites (blog post – chrisyoong.com)
- How to write an accessibility statement in 2025, with examples (blog post – equalizedigital.com)
- Legal update: October 2025 (blog post – tempertemper.net)
- A11y 101: 2.4.5 multiple ways (blog post - tarnoff.info)
- ChatGPT sez build with semantics first (blog post - html5accessibility.com)
- Don’t forget these tags to make HTML work like you expect (blog post - blog.jim-nielsen.com)
- Sometimes the best accessibility fix is a usability fix (blog post - buttondown.com/access-ability)
- Is it time to regulate React? (blog post - dbushell.com)
- Word and PowerPoint alt text roundup (blog post - webaim.org)
New to A11y
Chris Ferdinandi reminds engineers to just use a button. Using a div instead causes a host of problems. Semantic HTML always wins.
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.