WordPress.org

Make WordPress Core

Opened 2 years ago

Last modified 11 months ago

#34681 new enhancement

Consider removing the "Disable the visual editor when writing" option

Reported by: mark-k Owned by:
Milestone: Future Release Priority: normal
Severity: normal Version:
Component: Editor Keywords: needs-patch
Focuses: accessibility Cc:

Description

Is anyone even uses it? considering the lack of love the text editor gets I truly hope that the answer is no.

Change History (19)

#1 @SergeyBiryukov
2 years ago

#34682 was marked as a duplicate.

#2 @SergeyBiryukov
2 years ago

  • Component changed from Users to Editor
  • Summary changed from Time for the visual editor option in the user profile to die to Consider removing the "Disable the visual editor when writing" option

#3 follow-up: @joedolson
2 years ago

  • Focuses accessibility added

Speaking personally, I use this option all the time.

Speaking as a member of the accessibility team, there are a lot of problems in the visual editor for various types of disabilities, so for some people with disabilities the simplicity of the text editor makes the writing process much simpler. While it's true that users can disable this for themselves, having it completely disabled at the user level helps make certain that they won't have to repeat that action later.

The accessibility team will probably need to discuss this; it may be reasonable to remove, since it's not the only way to deal with that issue, but it'll need discussion and possibly some feedback from users with disabilities.

This ticket was mentioned in Slack in #accessibility by joedolson. View the logs.


2 years ago

#5 in reply to: ↑ 3 @mark-k
2 years ago

Replying to joedolson:

Speaking personally, I use this option all the time.

Speaking as a member of the accessibility team, there are a lot of problems in the visual editor for various types of disabilities, so for some people with disabilities the simplicity of the text editor makes the writing process much simpler. While it's true that users can disable this for themselves, having it completely disabled at the user level helps make certain that they won't have to repeat that action later.

Maybe I miss something. Removing this UI do not change anything in the editor, you are still able yo switch from the visual editor to the text one. The only UX impact is that you will still have the visual tab in the editor, but there is nothing that forces you to use it and the default is always the last one you used.

#6 @joedolson
2 years ago

For clarity, I didn't say that I think this is definitely a problem; I said that I think it needs to be looked at by the accessibility team and raised with users with disabilities. We have to make absolutely certain that the controls to switch between the visual and text editors don't have any accessibility issues.

#7 @mark-k
2 years ago

I realy hope they are no accessibility issues in switching the tabs in general, as in my age my eyesight is not getting better ;)

#8 @pento
2 years ago

  • Keywords needs-patch added
  • Milestone changed from Awaiting Review to Future Release

Assuming there are no blocking issues with accessibility, I agree that this option can go away. It's probably a bit late for 4.4, though. :-)

This ticket was mentioned in Slack in #accessibility by rianrietveld. View the logs.


2 years ago

#10 @iseulde
2 years ago

  • Milestone changed from Future Release to 4.5

@joedolson any updates? Anyone against it?

Last edited 2 years ago by iseulde (previous) (diff)

#11 @iseulde
2 years ago

  • Keywords good-first-bug added

#12 @joedolson
2 years ago

  • Keywords good-first-bug removed

Will follow up with the a11y team in our meeting Monday.

This ticket was mentioned in Slack in #accessibility by iseulde. View the logs.


2 years ago

#14 @joedolson
2 years ago

The biggest problem right now is that the tab sequence in the post editor is confusing, which makes it harder to switch between the visual and HTML editors. The fact that the options are between the editor and the title field, but are skipped when tabbing from title to post editor makes them difficult for a user to intuitively locate from the keyboard.

In cooperation with some movement on reorganizing the editor and post process per @michaelarestad's post https://make.wordpress.org/design/2016/01/11/improving-post-new/, this would be more desirable.

There's no opposition to removing this from the user settings, other than that it's confusing to find this control in the post editor from a screenreader + keyboard.

This ticket was mentioned in Slack in #core by chriscct7. View the logs.


2 years ago

#16 follow-up: @chriscct7
2 years ago

Should this be punted until the keyboard accessibility for switching between editors can be improved?

#17 in reply to: ↑ 16 @afercia
2 years ago

Replying to chriscct7:

Should this be punted until the keyboard accessibility for switching between editors can be improved?

Yes. :)

#18 @chriscct7
2 years ago

  • Milestone changed from 4.5 to Future Release

This ticket was mentioned in Slack in #accessibility by afercia. View the logs.


11 months ago

Note: See TracTickets for help on using tickets.