Updates: has responded to the Tavern article, as has Adrian.
WPTavern disagrees with Studio 24’s decision to drop WordPress over Gutenberg. I was going to write a long comment on that post, but then I figured I’d just address it on my site.
The Tavern’s disagreement hinges on the W3C prioritizing accessibility over its commitment to open source. And I’m wondering why that’s a bad thing.
Open source as a rule, (and FLOSS in particular, from Stallman on down), continues to consider accessibility one of those things that should be left up to the choice of the developer instead of something that should be implemented so that everyone can enjoy the freedoms granted by the GPL and other licenses. And anyone who has spent any time advocating for accessibility within the free spoftware space knows this. There’s a reason advocates are giving talks about the rights aspect of this instead of technical talks.
That talk’s from 2017, and I can’t think of another talk given by an accessibility advocate in that space since then. I can’t speak for anyone else but I get the impression we’ve finally just given up on trying to convince the Free Software movement that accessibility should be a requirement instead of a nice-to-have at best.
So it’s kind of nice to see the W3C flip tables over this.
Prioritizing accessibility over open source/free software isn’t the wrong thing to do, it’s the right thing to do, especially given the state of accessibility in the FLOSS space.
With regard to Gutenberg specifically, out of the eight projects I’m working on right now, two clients can use it without wanting to throw something, and only one of them really enjoys it. That client doesn’t have a disability and doesn’t use assistive technology. I still find Gutenberg to be an efficiency nightmare, and I’ve been using it for seven months now. And while I don’t think there’s a person alive who would say that the accessibility of the thing hasn’t improved, the part of that talk by Joe Dolsen left out is that the issues that have been closed and the accessibility successes are a start.
There’s also this, from his post on this subject:
When I read that statement, I feel like it implies that I gave a positive report on the accessibility state of Gutenberg in a way that isn’t really accurate.
Both those statements are absolutely true: two-thirds of the issues reported in the initial accessibility audit of Gutenberg have been solved, and the
overall accessibility is, indeed, vastly improved over the release, as would be expected given the first piece of information.
But it ignores the fact that those accessibility issues are not the only concerns raised on the project. They only encompass issues that existed in the
spring of 2019. Since then, many features have been added and changed, and those features both resolve issues and have created new ones. The accessibility
team is constantly playing catch up to try and provide enough support to improve Gutenberg. And even now, while it is more or less accessible, there are
critical features that are not yet implemented. There are entirely new interface patterns introduced on a regular basis that break prior accessibility
expectations.
And the statement that Gutenberg is vastly more accessible than at release is not particularly significant. At release, it was woefully inadequate; now
it’s bearable and largely usable, but in no way enjoyable. And in certain respects, it is lacking extremely basic features, such as support for adding
video captions within Gutenberg.
Note also Joe’s comments regarding WordPress and internationalization. They’re important, and I’m seconding them completely.
Improvement is excellent, but it’s not done. And speaking as someone who has to use Gutenberg on a pretty regular basis, it’s not ready to be deployed if you’re concerned about whether or not people with disabilities can add content to your system.
I hope that the W3C’s decision will convince WordPress’s leadership to prioritize accessibility at a higher level. But hope is not a strategy, and I don’t think organizations or individuals should be expected to stick with something that clearly isn’t meeting their needs or is even causing problems for the sake of their devotion to FLOSS.
I think Gutenberg is a great idea, despite the all-too-frequent flare-ups that still happen over accessibility issues. But I definitely don’t enjoy using it, and I don’t know any people with disabilities who enjoy using it either. And WCAG 2.0 is the minimum. You could completely conform to WCAG 2.0, and it doesn’t mean you’ve created something people with disabilities can use as effortlessly as everyone else.
Until Gutenberg gets to a point where it’s as easy to use as the classic editor, (if it ever does), organizations who either employ or want to employ people with disabilities are going to continue to drop WordPress over it. And telling them to fork WordPress or to maintain the classic editor plugin after WordPress stops doing that isn’t a solution to the problem. It’s about the most obtuse thing that could be said.
Seems like this Gutenberg thing is a royal pain in the behind. It’s almost like WP is starting to lean more towards a visual editor/designer that’s easier for those with little to no technical experience/knowledge to use. But that often leaves disabled users in the lurch.
Basically yeah.
Eric Eggert reposted this article on twitter.com.
biou reposted this article on twitter.com.
Llu ? mentioned this article on twitter.com.
mallory, alice & bob reposted this article on twitter.com.
Llu ? liked this article on twitter.com.
Steve Axthelm liked this article on twitter.com.
Eric Eggert liked this article on twitter.com.
Marco Zehe reposted this article on twitter.com.
Marco Zehe mentioned this article on twitter.com.
Marco Zehe mentioned this article on twitter.com.
patrick h. lauke reposted this article on twitter.com.
This is absolutely the right thing to do. Not least because offering accessible tools to staff is a legal requirement in many parts of the world.
?uud Steltenp?l ?????,??,??,??????? liked this article on twitter.com.
negi4a liked this article on twitter.com.
Fotis Papadogeorgopoulos liked this article on twitter.com.
Dennis Westphal reposted this article on twitter.com.
Project Which Pissed All Over Web Standards Is Astonished It Didn’t Get The Web Standards Gig
Dennis Westphal liked this article on twitter.com.
Valentin Go?u ????? liked this article on twitter.com.
?
Mathieu Savelli reposted this article on twitter.com.
goetsu reposted this article on twitter.com.
Mathieu Savelli liked this article on twitter.com.
Sandra Pilz reposted this article on twitter.com.
Chris Adams liked this article on twitter.com.
Anne Koepcke liked this article on twitter.com.
Eirenne // Shayla Maas reposted this article on twitter.com.
Eirenne // Shayla Maas liked this article on twitter.com.
btisdall liked this article on twitter.com.
Garry Turkington liked this article on twitter.com.
Nick mentioned this article on twitter.com.
Adrian Roselli liked this article on twitter.com.
Andrew Maier liked this article on twitter.com.
Robert Kingett mentioned this article on twitter.com.
Mark Greenfield liked this article on twitter.com.
Marijke Luttekes liked this article on twitter.com.
Rachel Cherry ? liked this article on twitter.com.
Alex Tait reposted this article on twitter.com.
CoolfieldsConsulting mentioned this article on twitter.com.
Alex Tait liked this article on twitter.com.
customerservant.com/w3c-is-priorit…
Wendy Reid liked this article on twitter.com.
It’s actually a good thing. Open-Source does not mean accessible, it just means that we can view the source.
????HTML?? reposted this article on twitter.com.
w3c.studio24.net/updates/on-not…
Alicia Jarvis (She/Her), CPACC, CSM ?? reposted this article on twitter.com.
????HTML?? liked this article on twitter.com.
Alicia Jarvis (She/Her), CPACC, CSM ?? liked this article on twitter.com.
Már Örlygsson ? liked this article on twitter.com.
Jo Spelbrink liked this article on twitter.com.
Access2Accessibility liked this article on twitter.com.
Diego Ramírez liked this article on twitter.com.
Damn straight. ?
Ashley Bischoff liked this article on twitter.com.
Robert Kingett mentioned this article on twitter.com.
Ricky Onsman reposted this article on twitter.com.
Chris Schmechel liked this article on twitter.com.
Ricky Onsman liked this article on twitter.com.
Dominik Wilkowski liked this article on twitter.com.
Tobie Langel reposted this article on twitter.com.
Accessibility is a human rights issue. Human rights trump open source purity.
Tobie Langel liked this article on twitter.com.
Myles Lewando liked this article on twitter.com.
Dan York liked this article on twitter.com.
Calum Leslie liked this article on twitter.com.
OZeWAI reposted this article on twitter.com.
Birkir Gunnarsson liked this article on twitter.com.
Aimee Maree reposted this article on twitter.com.
Da socially distant Vampy ? liked this article on twitter.com.
Myz Lilith liked this article on twitter.com.
Pumpkin Spice Mac n’ Cheese mentioned this article on twitter.com.
Steve Lee liked this article on twitter.com.
Aaron mentioned this article on dragonscave.space.
Coralie Mercier liked this article on twitter.com.
Gerald Oskoboiny liked this article on twitter.com.
Anthony Hortin ??? reposted this article on twitter.com.
Anthony Hortin ??? liked this article on twitter.com.
Ross McKay reposted this article on twitter.com.
Ross McKay liked this article on twitter.com.
Adrian Roselli mentioned this article on twitter.com.
Stephen Cronin reposted this article on twitter.com.
Stephen Cronin liked this article on twitter.com.
Ashley @ #GHC20, looking for 2021 internships! liked this article on twitter.com.
Deborah Edwards-Oñoro mentioned this article on twitter.com.
Jennifer Strickland liked this article on twitter.com.