July 19, 2021 • Issue #249

View this issue online or browse the full issue archive.

Featured: Automated accessibility testing, a few scenarios

Rian Rietveld explains that while automated accessibility testing can’t solve every accessibility challenge, a lot that can be done automatically to help you create better experiences.

Read more of Automated accessibility testing, a few scenarios.

Sponsored: CommonLook gives back to higher ed with free software and training

To give back to higher education institutions during these difficult times, CommonLook is providing a free subscription to two of its best-selling PDF accessibility software solutions: CommonLook PDF and CommonLook Office to higher ed institutions in the United States and Canada.

For details, visit CommonLook gives back to higher ed with free software and training.

News, resources, tools and tutorials

• Making all forms on GOV.UK accessible, easy to use and quick to process (blog post – gds.blog.gov.uk)
• Sa11y 2.0 (resource – ryersondmp.github.io/sa11y)
• Everyday accessibility (blog post - a11yproject.com)
• How Jetpack Compose is helping put accessibility first (blog post - deque.com)
• Three insights I gained while researching Vue.js accessibility (blog post - smashingmagazine.com)
• Accessibility of the section element (blog post - scottohara.me)
• CSS for Web Vitals (blog post - web.dev)

New to A11y

I read this piece by Seth Godin the other day about how good writing is cheaper than special effects, and it got me thinking. You could draw a parallel from that to accessibility. How? Inclusive design is cheaper than remediation. Many organizations pour money into accessibility testing late in the product lifecycle when that money may have a better return if invested in accessibility earlier during the design phase. As Seth says, “… it might be worth more to take the time and invest the effort to design something great instead.”