Issue #414
Featured: My grief with “In Brief”
“Just to preemptively state it: I appreciate what the Accessibility Guidelines Working Group (AGWG) is trying to do with the “In Brief” sections in WCAG’s Understanding documents. My criticism is about the execution of the information.”
Read more of My grief with “In Brief”.
Sponsored: Clearing the Digital Ramp: Practical advice and perspectives on website accessibility
A regular dose of news, advice, and opinions from the team at Mangrove, where inclusive and accessible website design has been a focal point for nearly 20 years.
Subscribe for provocative opinions about web accessibility and design.
News, resources, tools and tutorials
- Under-engineered estimated reading time feature (blog post - adrianroselli.com)
- Be careful when using generative artificial intelligence to produce code (blog post - cerovac.com/a11y)
- Accessibility is for everyone: Real life examples of the curb cut effect (blog post - craftzing.com)
- What is accessibility in mobile apps? Legal requirements in app development series – Part I (blog post – thedroidsonroids.com)
- The moral implications of being a moderately successful computer scientist and a woman (blog post - sigops.org)
- a11y-syntax-highlighting has been updated (blog post – ericwbailey.website)
- Inclusive marketing: Strategies for success (article – scientificamerican.com)
- Accessibility show with Joe Dolson, Episode 1: Mobile menu toggles (podcast – wpbuilds.com)
- How to find the accessible name of a button with Google Chrome (blog post – erikkroes.nl)
- Stop recreating the wheel: Local government organizations sharing accessibility Information (blog post – equalentry.com)
- Introduction to XR accessibility (blog post – tetralogical.com)
- Using controllers for keyboard accessibility (video – youtube.com)
- Prioritize accessibility in procurement for better CX and EX (resource – forrester.com)
New to A11y
Scott Jehl has a tongue and cheek graphic posted on the topic of the history of web performance. The point Scott makes here is that web performance hasn’t changed all that much. Scott highlights 2013 as a dividing line, which I assume is around the time JavaScript-heavy interfaces start to take shape. You always have to respect your environment.
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.