In reply to Alex Sirota.

As for the actual content creation, this is definitely a challenge, no doubt. It appears that in the rush for a superior experience with new technologies (ie React), the WordPress community and Automattic will be forced to innovate and make the underpinning tech behind Gutenberg accessible. No easy feat, but I am sure it is doable. And admirable!
But remember, this is innovation. This isn’t just the latest x.x.x release, but a major release. Innovation does require pushing forward, pissing people off, but eventually advancing and making it even easier to create beautiful AND accessible content. My bet is on Gutenberg creating a more accessible web, not one that is less accessible. We just have to be a bit more patient, constructive and probably contribute in ways we have not before. First, it is absolutely possible to make React apps accessible right now, no innovation needed. Second, before you can even talk about innovating when it comes to accessibility, you need to get the basics right first, and that means learning HTML deeply, CSS deeply, learning accessibility fundamentals, learning how to write JavaScript with accessibility baked in, and when and how to use ARIA, good focus management, ETC. All of this is necessary because when you decide to use your favorite framework, you will be able to recognize where it falls short, or where the code snippet you copied falls short so you can then fix it. You have to walk before you run, and the starting place for all of this is knowing what you don't know. Everybody who works in the field of accessibility has to start with knowing what they don't know, so you can then go from level to level.