[wp-meta] [Making WordPress.org] #7593: Remove the non-block editor

[Making WordPress.org]

#7593: Remove the non-block editor
----------------------------+---------------------
 Reporter:  dd32            |       Owner:  (none)
     Type:  task (blessed)  |      Status:  new
 Priority:  low             |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:                  |
----------------------------+---------------------

Comment (by dd32):

 Replying to [comment:8 alexstine]:

 @alexstine I'm aware of the listed issues, and I nearly linked it.

 However, The Gutenberg interface shown on the forums is a ''tiny'' set of
 the most basic Gutenberg featured. The issues facing many parts of the
 Gutenberg interface is absolutely irrelevant to the forums use-case.

 > For the issues:
 > 1. There is no longer a simple field to write a reply in, users must
 choose a block first.

 The editor does have a paragraph block as the starting point, a block
 selection is not supposed to be required.
 However, The tab indexes are indeed poorly arranged, resulting in landing
 on the toolbar and Block sections first.

 That should be resolved, I'd have to explore whether this is a
 implementation detail, Blocks Everywhere, or Gutenberg issue.

 This affects more than just those with accessibility needs.

 > 2. The editor adds landmark pollution to the main landmark.

 I'd really need more details on how to see this, and how it actually
 affects the interface. It's not at all obvious to most of us who don't use
 accessibility tools of what the expected outcome is, or how to resolve it.

 > 3. There is no options menu like in the main editor so therefore no way
 for users to discover the shortcuts required

 Enabling the Help / Shortcut menu's is possible. This seems like a very
 reasonable request, and one that is not otherwise tracked upstream, as
 it's an implementation detail.

 > 4. The list view option is read as a submenu, not sure how that
 happened. Maybe a plugin regression I guess.
 > 5. Shift+Tab does not move you to the block formatting toolbar, not sure
 why.

 These seem like bugs that likely need to be tested and filed upstream.

 > What I fail to see is why we're so hard pressed to make the experience
 harder for users to get and receive support.

 Given the option to disable the editor is already hidden in the user
 profile, this is really not about making it harder to receive support, but
 rather to streamline the experience and expectations in code.

 Right now, those using the non-block-editor do not get their workflows
 tested, as it's such a small percentage of posts, instead it's just
 expected that every post is a block post.

 > Really, the best outcome for this would have been an option to edit in
 plain text or the Gutenberg editor that you could select on the new
 topic/reply forms

 IIRC the problem is that it's not natively offered by the upstream
 interface being used, and so adding it in is prohibitively complex.

 > just because in your opinion people are not using ALT text doesn't mean
 we should remove the option.

 It's not opinion, it's what the data says. There's no need to
 design/account for something that is not utilised.

 > EDIT: ALT text, joedolson said it could not be added with Gutenberg so
 how are people adding it in the forums?

 I suspect it might be from copy-paste then, as that's correct, I've
 checked and there's no UI exposed for it currently.

 > It's clear my opinion doesn't matter so I'm going to see myself out.
 It's also getting harder and harder to not take this personally, I'm not
 just the annoying Accessibility Team, I actually live this daily.

 Your opinion does matter, but opinion needs to be backed up with data and
 examples. I can't read your mind, I can't duplicate your experiences, I
 can't resolve anything If I don't have anything to provide a basic
 direction.

 I've never once considered "The accessibility team is just annoying", but
 I do routinely wish that representatives of teams (Not specifically
 Accessibility! Other teams too) would provide adequate context to their
 requests and concerns. I can't do anything with "Team X feels this doesn't
 work".

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/7593#comment:9>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org