Issue #11
Featured: Flexbox and the keyboard navigation disconnect
CSS Flexbox can create a disconnect between the DOM order and visual presentation of content, causing keyboard navigation to break. For this reason, the CSS Flexible Box Layout module warns against resequencing content logic, but asking authors not to use flexbox in this way seems illogical in itself.
Read more from Léonie Watson on the challenge of Flexbox and accessibility.
News and links
The Accessibility Project redesigns: The open source accessibility resource has a new look.
Petition Demands Release of Internet ADA Regulations: From the news story, “Internet ADA regulations were scheduled to be released this spring, but the U.S. Department of Justice has postponed that until 2018. Now, an online petition is circulating to ask the White House not to wait any longer.”
Looking ahead: Microsoft Edge for developers in 2016: Microsoft sets priorities for its Microsoft Edge browser, including accessibility.
Resources, tools and tutorials
- Why accessibility is good for business (according to my mechanic) (blog post)
- On smells and colors (blog post)
- A new podcast on digital accessibility (blog post)
- Three common accessibility pitfalls for developers: text alternatives (blog post)
- Race, gender, and other categories in alt Text for headshots (listserv discussion)
- Captions and YouTube (blog post)
New to A11y
Karin Hitselberger write about why accessibility is not a “nice thing to do.”
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.