In the short term, we hope to resolve all accessibility issues that are true barriers to the use of Gutenberg. In the long term, we hope to improve the integration of accessibility into all future WordPress design processes.
Thanks @jmitchell! We’ve been tracking this closely. Also relevant, WPCampus—an organization of WordPress in higher education users, developers, etc— has put out on RFP for an third-party accessibility audit of Gutenberg.
At this point we will be deactivating Gutenberg within Pressbooks until further notice. I’ll be publishing a blog post about this soon.
At some point, will Pressbooks switch to a Block based editor?
My current perception is that the status quo will just stay until some compelling feature appears in Gutenberg (simultaneous multi author editing?) that would be worth switching for. Is that mostly correct?
Hi @beckej – we’re still monitoring the ongoing work to fix and improve the many a11y issues identified with Gutenberg: https://github.com/WordPress/gutenberg/projects/25. We haven’t made any plans to change out the default editor for Pressbooks users. It’s not something we’re likely to do any time in the near future.