Issue #411
Featured: WCAG’s A and AA distinction is mostly academic
Eric Eggert explains one way to think about what makes a WCAG Success Criterion (SC) A, AA, or AAA. Eric’s way of looking at this challenge may be simpler than you think.
Read more of WCAG’s A and AA distinction is mostly academic.
Sponsored: To make your site more accessible, start with your content
Word choice, content formatting, the inclusion of video captions —all of these and more influence your site’s accessibility.
Discover Mangrove’s steps and tips on for creating accessible website content.
News, resources, tools and tutorials
- The most important thing to look at when choosing an accessibility auditor (blog post - afixt.com)
- Reckoning: Part 2 — Object lesson (blog post - infrequently.org)
- 80 / 20 accessibility (blog post - marcus.io)
- Stripes(): the border function you never knew you needed (blog post – joshtumath.uk)
- How to create accessible charts in React: A guide to inclusive data visualisation (blog post - dev.to/tinyoctopus)
- Creating accessible digital colour palettes using the 60-30-10 design rule (blog post – visionaustralia.org)
- What the heck is ARIA? A beginner’s guide to ARIA for accessibility (event – a11ytalks.com)
- The article element (blog post – heydonworks.com)
- How can accessibility improve your conversion rate optimization efforts? (blog post – cerovac.com/a11y)
- Basic keyboard shortcut support for focused links (blog post – ericwbailey.website)
- Batteries included accessibility: A Pragmatic guide to get started today (webinar – youtube.com)
- Using alternative formats in your Canvas course (blog post – blog.pope.tech)
- When it comes to EAA compliance, to delay is to pay (blog post – deque.com)
- Foundations: Labelling text fields with input and label (blog post – tetralogical.com)
- Disability data alarmingly absent from AI algorithmic tools, report suggests (blog post – forbes.com/sites/gusalexiou)
- Spoiler alert: It needs to be accessible (blog post – scottohara.me)
Sponsored Classifieds
Buttons are a small but key element of a website and Dave Davies, Frontend Developer, explains why creating accessible buttons is crucial for all users.
New to A11y
I confess. Not too long ago I started testing an interface as part of an audit, and kept running into some weirdness with keyboard functionality. I thought something broke. Turns out that I needed to think about what to do before filing that keyboard bug. I’ve been doing this work for more than a decade, and this still gets me on occasion. This time, it was because I had just gotten a new computer, and hadn’t enabled full keyboard access in MacOS yet.
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.