Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

I have resigned as the WordPress accessibility team lead

rianrietveld.com

Post reply on HN
Print view View original

1–10 of 21 posts

Re: I have resigned as the WordPress accessibility team lead

#4

Post by detaro »

cronz wrote: post #3

Isn't Gutenberg optional? Can't you have a checkbox that says "I'm disabled, I can't use Gutenberg, give me the old editor"

as far as I know it is not intended to be optional once finished, although I suspect someone wanting the old one back will make a plugin replacing it.

Re: I have resigned as the WordPress accessibility team lead

#5

Post by pavel_lishin »

cronz wrote: post #3

Isn't Gutenberg optional? Can't you have a checkbox that says "I'm disabled, I can't use Gutenberg, give me the old editor"

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."

Re: I have resigned as the WordPress accessibility team lead

#6

Post by polygot »

pavel_lishin wrote: post #5
cronz wrote: post #3

Isn't Gutenberg optional? Can't you have a checkbox that says "I'm disabled, I can't use Gutenberg, give me the old editor"

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."

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

#7

Post by rciorba »

pavel_lishin wrote: post #5
cronz wrote: post #3

Isn't Gutenberg optional? Can't you have a checkbox that says "I'm disabled, I can't use Gutenberg, give me the old editor"

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."

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

#8

Post by SippinLean »

detaro wrote: post #4
cronz wrote: post #3

Isn't Gutenberg optional? Can't you have a checkbox that says "I'm disabled, I can't use Gutenberg, give me the old editor"

as far as I know it is not intended to be optional once finished, although I suspect someone wanting the old one back will make a plugin replacing it.

There is already an official plugin replacing it: https://wordpress.org/plugins/classic-editor/

Re: I have resigned as the WordPress accessibility team lead

#9

Post by ricardobeat »

This is a bit puzzling for me:

1. A React app is still DOM-based. Normal accessibility practices still apply, as they do for any other SPAs

2. It takes maybe a week to learn enough of JSX and React to get started on accessibility tasks

This sounds like refusing to work on a new codebase without actually being invested into it. Also got a combative feeling from reading a few PRs, where simple style issues are discussed at length vs just fixed with one variable change. Am I reading it wrong?

All the best luck for Matthew.

Re: I have resigned as the WordPress accessibility team lead

#10

Post by user3359 »

pavel_lishin wrote: post #5
cronz wrote: post #3

Isn't Gutenberg optional? Can't you have a checkbox that says "I'm disabled, I can't use Gutenberg, give me the old editor"

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."

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.

Post reply on HN