Featured: Debunking the myth: Accessibility and React
Mark Steadman says that the story you may have heard regarding React and accessibility isn’t all true. Lots of the challenges can be overcome within the framework itself.
News, resources, tools and tutorials
- Front-end performance checklist 2020 (resource – smashingmagazine.com)
- Text links: Best practices for screen readers (blog post – deque.com)
- Why You Should Choose HTML5 article Over section (blog post – smashingmagazine.com)
- Passing of Joseph O’Connor (blog post – webaxe.org)
- Documentation is key for “inclusion” (blog post – email@example.com)
- What is the difference between WCAG A and WCAG AA conformance? (blog post – levelaccess.com)
- Accessibility guidelines 3.0 (blog post – myaccessible.website)
- Checking 3rd party vendors’ product accessibility (blog post – knowbility.org)
- My priority of methods for labeling a control (blog post – adrianroselli.com)
- Under discussion: Web accessibility (podcast – welcometothejungle.com)
- Putting devs before users: how frameworks destroyed web performance (blog post – uxdesign.cc)
- Smaller HTML payloads with service workers (blog post – philipwalton.com)
New to A11y
HTML serves as the foundation of good, accessible experiences. So it’s nice to know what not to do, or you might end up in, HTMLHell. This evolving collection of bad practices from Manuel Matuzovic also includes what to do instead.
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 firstname.lastname@example.org.
Sponsorships and donations
You can sponsor Accessibility Weekly!. If you or your company is interested, send a note to email@example.com.
If you enjoy the newsletter, consider making a donation.