I’ve tweeted a lot about how much I love #gutenberg and the super positive impact it’s made for the marketing folks I work with everyday.But despite my love for it, I can’t responsibly support it being merged into core until it’s accessibility is improved.— Carrie Forde (@CarrieForde) October 20, 2018
Easiest way to make your content accessible to everyone? On any device? Plain old semantic HTML. #a11y— Deborah Edwards-Onoro (@redcrew) October 20, 2018
Web #accessibility is not "only" about meeting coding and color guidelines. It's also about reducing cognitive load and designing for cognitive differences. Excellent @alistapart piece, highly relevant to the current #WordPress + #Gutenberg situation https://t.co/lgll1tMIEm— Morten Rand-Hendriksen (@mor10) October 17, 2018
I wish developers took 2 minutes to navigate their pages using only a keyboard. So many accessibility issues would get identified this way. #a11y And it's not like the keyboard is a deeply esoteric accessibility testing tool. I suspect most developers still use it daily.— Nicolas Steenhout (@vavroom) October 17, 2018
We added metrics to see who's not using default font size on iOS, and the numbers were surprising! If you don't support Dynamic Type, you'll worsen the experience for at least a quarter of your users. Detailed stats + tips to support inside. https://t.co/OgvJw9HAgx— Peter Steinberger (@steipete) October 17, 2018