Issue #281
Featured: Support for marking radio buttons required, invalid
Adrian Roselli writes about making radio buttons required, described as “The white whale to many a developer who is trying their darnedest to ensure they are conveyed accessibly while not also making it sound like every individual radio button must be toggled.”
Read more of Support for marking radio buttons required, invalid.
News, resources, tools and tutorials
- Making a custom clear text field button (blog post – scottohara.me
- Inclusion first: How to make your product accessible and inclusive (blog post - uxdesign.cc)
- Turning the tables on accessibility (blog post - theguardian.com)
- Column headers and browser support (blog post - adrianroselli.com)
- Comic Sans is a good typeface, actually (blog post - ericwbailey.design)
- How to use the accessibility tree for a11y testing (blog post - giovanicamara.com)
- Accessibility tree snapshots in Pleasantest (tool - cloudfour.com)
- Time for government to stop using Medium (blog post - govfresh.com)
New to A11y?
Mark Steadman outlines the tangled web of ARIA, and the problems with ARIA-first development. Mark points out many challenges with too much ARIA, among them: “It is not as maintainable as using semantic HTML.” So true.
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.