Re:I have resigned as the WordPress accessibility team lead
by pavel_lishin on Wednesday October 10, 2018 @09:01AM
(#18184407)
But that's kind of a bad approach for developing software. "Sorry, handicapped person, you don't get the new hotness. But it's ok, you can continue using this old software that we super-duper promise to continue supporting."
[ Parent
| on HN ]
Re:I have resigned as the WordPress accessibility team lead
by user3359 on Wednesday October 10, 2018 @12:33PM
(#18186454)
I've been recommending my clients avoid using it for minimum 6 months post "release" regardless of accessibility.
Gutenberg has been changing constantly. When it's "released" it should only be released as a final version to developers, meaning they're no longer changing it, before being released to the public.
I've known a few people who've developed Gutenberg compatible plugins, only to have it break 2 weeks later when an "update" arrived. "Update" meaning "it's been redone entirely different".
It's been noted elsewhere here - use the official "classic editor". Gutenberg offers ZERO benefits. It's simply a different way of accomplising the same tasks.
Re:I have resigned as the WordPress accessibility team lead
by polygot on Wednesday October 10, 2018 @10:23AM
(#18185095)
Microsoft Outlook for Enterprises does that; it has a “lite” mode which is for people with older browsers, older computers, or have accessibility needs. However, my reasoning is a bit flawed as just because Microsoft does it doesn’t mean it’s correct.
Re:I have resigned as the WordPress accessibility team lead
by rciorba on Wednesday October 10, 2018 @10:24AM
(#18185104)
Also, that would mean maintain both editors going forward. Two UI-s means double the chance for regressions.
Re:I have resigned as the WordPress accessibility team lead
by kroosaidher on Wednesday October 10, 2018 @01:45PM
(#18187233)
And guess which one is the priority for bug fixes? Hint: it's not the old, unexciting one.