[wp-trac] [WordPress Trac] #38061: Rename the text window name on the editor

[WordPress Trac]

#38061: Rename the text window name on the editor
-------------------------------------+------------------------------
 Reporter:  lukecavanagh             |       Owner:  afercia
     Type:  enhancement              |      Status:  assigned
 Priority:  normal                   |   Milestone:  Awaiting Review
Component:  Editor                   |     Version:
 Severity:  normal                   |  Resolution:
 Keywords:  has-patch needs-refresh  |     Focuses:  accessibility
-------------------------------------+------------------------------
Changes (by afercia):

 * keywords:  has-patch => has-patch needs-refresh
 * owner:   => afercia
 * focuses:   => accessibility
 * status:  new => assigned


Comment:

 Following the argumentations on #20993 seems to me the change from `HTML`
 to `Text` was an improvement anyways, as `HTML` was a bit misleading.
 However, although `Text` is better than `HTML`, it still doesn't
 accurately represents what users see in the normal textarea, which is a
 mix of text and code. I'd agree this could be potentially confusing for
 new users.

 @giuriani on #42627 made a good point `Text` may be confusing for
 beginners and also not so meaningful when read out of context. Ideally,
 any UI control should make sense even when read out of context. For
 example, screen reader users can jump to different parts of a page using
 dedicated shortcuts, and landing on a control that says just "Visual" or
 just "Text" doesn't help so much new users. Of course, with time users
 would learn those controls relate to the Editor, but making them a bit
 more explicit would help.

 I'd also suggest to consider what's going to happen with Gutenberg. When
 switching to "text mode", what users see there doesn't really look like
 text :) there's a lot of code there:

 [[Image(https://cldup.com/fR-NuUOZKQ.png)]]

 I understand the available space is a concern, but I'd propose to expand a
 bit these labels to give better context, adding the word "editor" as
 [attachment:38061.diff] does. Seems to me the word "Code" better
 represents what the textarea content actually is. To add some context
 something like the following strings could work:
 - Visual editor
 - Code editor

 Gutenberg already has a lot of space for longer strings:

 [[Image(https://cldup.com/NUhzYnwVMG.png)]]

 Worth noting many other things should be changed, as done on #20993. For
 example:
 - documentation
 - inline comments
 - the contextual help tab content
 - translators comments and context, e.g. `Name for the Text editor tab
 (formerly HTML)`

--
Ticket URL: <https://core.trac.wordpress.org/ticket/38061#comment:21>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform