Big loss for WordPress.
“I have resigned as the WordPress accessibility team lead. Here is why.” by @RianRietveld
rianrietveld.com/2018/10/09/i-h…
“I have resigned as the WordPress accessibility team lead. Here is why.” by @RianRietveld
rianrietveld.com/2018/10/09/i-h…
“There was no REACT developer with accessibility experience in the community […]”
Which means every a11y fix is a bug fix, an afterthought.
Which means every a11y fix is a bug fix, an afterthought.
“[…] tested, improved and then approved by Andrea, changed in a later stage, breaking the a11y improvements […]”
I do not envy @afercia.
I do not envy @afercia.
Essentially every time he provided a fix, the lack of React a11y skills meant his work was overwritten and he would have to start over.
“New functionality was not keyboard tested before implementation […]”
This is such a fundamental mistake. A bellwether of the future state.
This is such a fundamental mistake. A bellwether of the future state.
“The results indicated so many accessibility issues that most testers refused to look at Gutenberg again.”
Sisyphean.
Sisyphean.
“[…] feedback this week that we should have written the GitHub issues differently.”
The rallying cry of failure. *Our* fault.
*sigh*
The rallying cry of failure. *Our* fault.
*sigh*
There is a lesson here for your organization, laid bare by the 2-year-late and inaccessible result of Gutenberg.
Learn from it.
Learn from it.
Red flag indeed.
I agree with her assertion about leadership priority.
I agree with her assertion about leadership priority.
The first part of @joedolson’s post touches on the gatekeeping, the second on the latest (of many) release date: joedolson.com/2018/10/wordpr…
Also true.
This overall thread echos some of my concerns from June 2017 when Gutenberg was revealed: adrianroselli.com/2017/06/first-…
It also reaffirms my decision in June, after WordCamp Europe, to recommend against Gutenberg in an open letter: adrianroselli.com/2018/06/on-gut…
If on mobile, comments are collapsed so you will need to expand and then manually scroll to the comment.
As of 2 hours ago, the GitHub issue has been closed to non-collaborators: github.com/WordPress/gute…
Note comments leading up to it.
Note comments leading up to it.
“I'm still not convinced there are sufficient Accessibility issues that prevent a release”
Why an audit is needed.
Why an audit is needed.
New issue just opened to identify what is “sufficiently accessible” for merging Gutenberg into core: github.com/WordPress/gute…
More reasons to thank @afercia for his efforts to calmly explain that *these have all been tried before*: github.com/WordPress/gute…
Reminder that Rian made a page back in March with test criteria for those who want try Gutenberg and leave feedback:
make.wordpress.org/accessibility/…
make.wordpress.org/accessibility/…
Automattic is scrapping any a11y audit of Gutenberg because ”the audit will not affect release timing”.
WON‘T FIX
github.com/WordPress/gute…
WON‘T FIX
github.com/WordPress/gute…
I leave it to you to draw your own conclusions.
“A Very Informal Look at Gutenberg Accessibility” thatdevgirl.com/blog/a-very-in…
Pokes the editor with an automated tool and then keyboard only.
Pokes the editor with an automated tool and then keyboard only.
1. If so, the employer can be sued.
Or…
2. No upgrade to 5, so security risks;
3. Classic editor plug-in, as more and more plug-ins stop supporting it.
Goto 1
“Regarding Accessibility in Gutenberg” make.wordpress.org/core/2018/10/1…
Gathered together likely in response to outcry.
Gathered together likely in response to outcry.
Regardless of what has been done so far, if it still has barriers in even one critical part, the entire platform can be useless.
For example, huge reliance on keyboard shortcuts but seemingly no consideration for speech users or WCAG 2.1.4: Character Key Shortcuts: w3.org/WAI/WCAG21/Und…
(In retrospect, I do not immediately see any single-key shortcuts, so 2.1.4 may not apply.)
While not specifically about Gutenberg, Matt Mullenweg’s response to missing captions of his talks on WordPress•tv is telling: iamahmedkhalifa.com/blog/being-sho…
There are still no captions on his 2017 WCEU talk announcing Gutenberg (which I noted in my own 2017 post): wordpress.tv/2017/07/01/int…
“Some Gutenberg Accessibility Clarifications” from @joedolson: joedolson.com/2018/10/some-g…
The current chaos has obfuscated some key points.
The current chaos has obfuscated some key points.
“It is entirely possible that Gutenberg will come within a hair of passing WCAG […] 2.0 at level AA at release, but still be inaccessible.”
“The best solution would be to delay the release.”
“Call for Testers: Community Gutenberg Accessibility Tests” make.wordpress.org/core/2018/10/1…
Note that a keyboard is assistive technology.
Note that a keyboard is assistive technology.
As is Windows High Contrast Mode, ZoomText, custom mice, switch controls, dictation software, etc.
After ~2 years, and weeks away from release, the project lead is finally trying to start testing with users with disabilities. Without paying.
Per Joe, he is the *accessibility* lead for the release. I knew it and still cocked it up.
Positive sign: automattic.com/work-with-us/p…
At least two years too late for Gutenberg, but Automattic is at least signaling an interest in accessibility.
At least two years too late for Gutenberg, but Automattic is at least signaling an interest in accessibility.
Even more positive sign — WPCampus has an RFP for a Gutenberg accessibility audit:
“The accessibility team will publish a detailed post about the accessibility level of Gutenberg.” make.wordpress.org/accessibility/…
At least two weeks out.
At least two weeks out.
[T]here is no mechanism for increasing the font size […] in the existing editor. However, […] there may as well not be one in Gutenberg.” make.wordpress.org/accessibility/…
WP a11y team proposed a warning in 5.0 to warn administrators of a11y issues. Closed as ‘nah?’
core.trac.wordpress.org/ticket/44671
core.trac.wordpress.org/ticket/44671
“WordPress philosophy states deadlines are not arbitrary. […] Core standards are not arbitrary either, and accessibility is a not a one-more feature.”
werdswords.com/accessibility-…
werdswords.com/accessibility-…
I have done usability reviews like this: a narrative as you go…
jjj.blog/2018/10/wordpr…
Not accessibility issues per se, but yeah they are.
jjj.blog/2018/10/wordpr…
Not accessibility issues per se, but yeah they are.
Damage done, people gone, ill will created.
Saying you will address it *after* release misses the point.
pento.net/2018/10/26/ite…
Saying you will address it *after* release misses the point.
pento.net/2018/10/26/ite…
Where @photomatt asserts some UI widgets “are in every modern web app”, but does not understand they are usually inaccessible.
wptavern.com/wordpress-acce…
wptavern.com/wordpress-acce…
Where @photomatt again falsely asserts “for many [AT] users Gutenberg improves what you can do”. Offers no example.
wptavern.com/wordpress-acce…
wptavern.com/wordpress-acce…
In this entire thread Matt has liked this one where I retracted an assertion:
Smells like cherry-picking.
Smells like cherry-picking.
I left a comment asking what specific AT he was referencing. Not visible, probably in moderation: wptavern.com/wordpress-acce…
Keynote talk from @mor10 at WordCamp Vancouver:
Touches on Gutenberg accessibility.
Note: auto-generated captions.
Touches on Gutenberg accessibility.
Note: auto-generated captions.
Anecdotally, I have heard of and spoken with other WP contributors who are frustrated by Gutenberg and just walking away.
Appropriately, NC State University is recommending disabling Gutenberg on 5.0 upgrades until after an a11y audit: design.oit.ncsu.edu/2018/10/24/gut…
Founder of Yoast:
“if we keep striving for its planned November 19th release date, we are setting ourselves up for failure.”
joost.blog/wordpress-5-0-…
“if we keep striving for its planned November 19th release date, we are setting ourselves up for failure.”
joost.blog/wordpress-5-0-…
“I do not have the privilege of simply ignoring Gutenberg’s accessibility problems, because [they] directly effect my livelihood.”
customerservant.com/some-quick-tho…
customerservant.com/some-quick-tho…
Classic Editor support (as plug-in) ends 31 Dec 2021. Also, consideration for bundling with 5.0 (upgrades only).
make.wordpress.org/core/2018/11/0…
make.wordpress.org/core/2018/11/0…
“WordPress 5.0 is Not Ready” mrwweb.com/wordpress-5-0-…
“[T]here hasn’t even been a public explanation for why these new features are ready.”
“[T]here hasn’t even been a public explanation for why these new features are ready.”
WordPress 5.0 release date slips to 27 November (from 19th): make.wordpress.org/core/2018/11/0…
This is within the 8 day buffer originally mentioned.
This is within the 8 day buffer originally mentioned.
<cough>haha yeah right they are too committed to an artificial deadline</cough>
I see more and more saying this about WordPress. Whether Gutenberg, captions, etc.
From Matt’s own hands, @automattic is planning a Gutenberg accessibility audit after all. It had been called off 29 days ago.
Still a petty response.
Still a petty response.
.@10up ran usability test on Guteberg flow, rated highly:
10up.com/blog/2018/test…
Note participants said a step easy, but did not complete task.
10up.com/blog/2018/test…
Note participants said a step easy, but did not complete task.
Users will often mis-report how difficult a task was in usability studies. Not uncommon. Note how they handled changing an image.
I think too few have considered the need for backward compat with a tool committed to launching before it is done.
Automated accessibility testing can only catch ~30% of issues, but in Gutenberg’s current state this is good:
11 days to go before Gutenberg launches (the fallback date)! Some bugs linked in this thread:
Great article: wptavern.com/how-wordpress-…
But I am so jaded I can only think of how disabled devs I know will have their livelihoods affected with Gutenberg.
But I am so jaded I can only think of how disabled devs I know will have their livelihoods affected with Gutenberg.
WordPress really is an impressive platform. I am hard on Gutenberg because of how it blunts that potential.
WordPress 5.0 release date slips again (from 19th then 27th): make.wordpress.org/core/2018/11/2…
No new date. Pending completion of RC, then will decide.
No new date. Pending completion of RC, then will decide.
Yesterday was the latter release date, which we knew would be missed. January 22 is a possible fallback date. Next core meeting in 7 hours.
Meanwhile, WPCampus is crowd-funding ($30k) for the Gutenberg audit it solicited:
Targeting 17 Jan audit completion.
Targeting 17 Jan audit completion.
Adrian Roselli LLC has just made a donation to the crowdfunding effort for an a11y audit of Gutenberg (that Automattic should be funding): wpcampus.org/2018/11/fundra…
Remember, Automattic can afford it. WPCampus has to crowdfund it.
Didn’t Matt suggest it was back on though when he was being petty to Marcy?
Didn’t Matt suggest it was back on though when he was being petty to Marcy?
No notes (yet) from yesterday’s core meeting. However, Matt is scheduling 15 min chat sessions now through Sunday: make.wordpress.org/core/2018/11/2…
Odd justification. Automattic will pay for 40 Gutenberg devs, but expects a11y experts to volunteer. Ship it anyway! gutenbergtimes.com/gutenberg-acce…
A write-up on the WPCampus accessibility crowd-funding effort with a quote from 👍 this guy 👍: wptavern.com/wpcampus-seeks…
This is my first hearing that @automattic’s a11y audit is back on: ma.tt/2018/11/a-gute…
Maybe fund @wpcampusorg’s effort instead?
Maybe fund @wpcampusorg’s effort instead?
Pay attention to the fact that no date is mentioned. No timeline. Assertions to assuage, but failure to act is the trend I see.
I asked for more detail at the original GitHub announcement (& retraction) of the @Automattic Gutenberg a11y audit: github.com/WordPress/gute…
Got an answer: ma.tt/2018/11/a-gute…
“I think it’s fine having two as well, I’ll talk to Rachel about how the funding is going.”
“I think it’s fine having two as well, I’ll talk to Rachel about how the funding is going.”
Thursday 5 December is now the launch date for WordPress 5.0 and Gutenberg: make.wordpress.org/core/2018/12/0…
Gotta meet that WPUS date, issues be damned!
Gotta meet that WPUS date, issues be damned!
Yoast on whether or not to upgrade to WordPress 5.0 tomorrow:
“So our advice boils down to: if you can wait, wait.”
yoast.com/should-you-upd…
“So our advice boils down to: if you can wait, wait.”
yoast.com/should-you-upd…
Today might be a good day to finally have that conversation with your clients. adrianroselli.com/2018/06/on-gut…
This confuses me. Is Automattic still doing its own audit as Matt suggested on his site two days ago?
Either way, if Automattic is going to fully fund it, then adding my pledge ($103) plus what I spent on captioning his videos ($142), I want my $245.
“WordPress and the new Gutenberg editor” studio24.net/blog/wordpress…
“At present we advise to not use Gutenberg.”
“At present we advise to not use Gutenberg.”
“The Night Before Gutenberg”
advancedcustomfields.com/blog/the-night…
“[ACF] are unfortunately not ready for the WordPress 5.0 release.”
advancedcustomfields.com/blog/the-night…
“[ACF] are unfortunately not ready for the WordPress 5.0 release.”
Of course 5.0 came out while I was on a call: wordpress.org/news/2018/12/b…
Note that it leads with Gutenberg.
Note that it leads with Gutenberg.
Just a few years ago, colleges would not even look at Drupal due to its a11y issues. Now its messaging is on-point. dri.es/drupal-commitm…
Big wrap-up from @abrightclearweb:
“The User Experience and Accessibility of Gutenberg (The WordPress 5.0 Block Editor)”
abrightclearweb.com/user-experienc…
“The User Experience and Accessibility of Gutenberg (The WordPress 5.0 Block Editor)”
abrightclearweb.com/user-experienc…
So @hankchizljaw has summed up this thread and wrote much the same retrospective post I was going to write. Only better.
smashingmagazine.com/2018/12/gutenb…
smashingmagazine.com/2018/12/gutenb…
