Issue #326
Featured: Component library accessibility audit
“Auditing components is necessary—all code should be tested for accessibility standards—but presenting a component alone on an empty page in the context of a component library has limitations.”
Read more of Component library accessibility audit.
News, resources, tools and tutorials
- Simple web accessibility checks - featuring Orca (video - youtube.com)
- How indie studios are pioneering accessible game design (article - wired.com)
- Carry on testing 2023 (blog post - tpgi.com)
- Turn your InDesign resume into an accessible PDF (blog post – bootcamp.uxdesign.cc)
- Legal update: December 2022 (blog post – convergeaccessibility.com)
- Federal web accessibility focus has private sector on notice (article - news.bloomberglaw.com)
- Will ChatGPT threaten the future of the digital accessibility field? (blog post – inklusiv.ca)
- JAWS, NVDA, and VoiceOver Braille viewers (blog post - adrianroselli.com)
- Sony’s Project Leonardo is a controller kit to help people with disabilities play PS5 (article – engadget.com)
- A new accessibility strategy for the GOV.UK Design System (blog post - accessibility.blog.gov.uk)
- Marketing in accessibility (blog post - equalentry.com)
New to A11y
Alexander Lehner shares common ARIA mistakes and how to avoid them. I wish more engineers and designers picked up this skill. It’s an important one.
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.