Which means every a11y fix is a bug fix, an afterthought.
I do not envy @afercia.
This is such a fundamental mistake. A bellwether of the future state.
The rallying cry of failure. *Our* fault.
Learn from it.
I agree with her assertion about leadership priority.
Note comments leading up to it.
Why an audit is needed.
Pokes the editor with an automated tool and then keyboard only.
1. If so, the employer can be sued.
2. No upgrade to 5, so security risks;
3. Classic editor plug-in, as more and more plug-ins stop supporting it.
Gathered together likely in response to outcry.
Note that a keyboard is assistive technology.
At least two years too late for Gutenberg, but Automattic is at least signaling an interest in accessibility.
At least two weeks out.
Not accessibility issues per se, but yeah they are.
Saying you will address it *after* release misses the point.
Smells like cherry-picking.
Touches on Gutenberg accessibility.
Note: auto-generated captions.
“if we keep striving for its planned November 19th release date, we are setting ourselves up for failure.”
“[T]here hasn’t even been a public explanation for why these new features are ready.”
This is within the 8 day buffer originally mentioned.
Still a petty response.
But I am so jaded I can only think of how disabled devs I know will have their livelihoods affected with Gutenberg.
No new date. Pending completion of RC, then will decide.
Targeting 17 Jan audit completion.
Didn’t Matt suggest it was back on though when he was being petty to Marcy?
“I think it’s fine having two as well, I’ll talk to Rachel about how the funding is going.”
Gotta meet that WPUS date, issues be damned!
“So our advice boils down to: if you can wait, wait.”
“At present we advise to not use Gutenberg.”
“[ACF] are unfortunately not ready for the WordPress 5.0 release.”
Note that it leads with Gutenberg.