[wp-trac] [WordPress Trac] #38049: Rename Headings in TinyMCE

WordPress Trac noreply at wordpress.org
Wed Oct 26 15:22:09 UTC 2016


#38049: Rename Headings in TinyMCE
-------------------------+--------------------------------
 Reporter:  mrwweb       |       Owner:
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:  Future Release
Component:  Editor       |     Version:
 Severity:  normal       |  Resolution:
 Keywords:  has-patch    |     Focuses:  ui, accessibility
-------------------------+--------------------------------

Comment (by mrwweb):

 Replying to [comment:3 hugobaeta]:
 > Another solution might be to use explicit levels indicators:
 >
 > - '''Heading Level 1'''  ''(this would generate an h2)''
 > - '''Heading Level 2'''  ''(this would generate an h3)''
 > - '''Heading Level 3'''  ''(this would generate an h4)''

 That is super confusing and I can't think of any other place in WordPress
 where the interface is essentially lying about what it's doing. I have
 personally spent hours drilling into people not to use Heading 1 and I
 personally know a lot of other who have done the same. This would cause
 problems and people wouldn't even know it.

 '''Regarding page builders''', in previous tickets it's been mentioned
 that it's quite easy to add H1 back into `formatselect` via the
 [https://codex.wordpress.org/TinyMCE#Customize_TinyMCE_with_Filters
 tiny_mce_before_init] filter settings. I know some page builders (Make
 theme) insert the title as H1 with screen reader text if users choose to
 hide it, which seems like a smart decision. Even with page builders, my
 guess is still that a large majority of themes either output Heading 1 for
 the Page Title or ''should'' be doing that and are doing something weird
 instead.

 '''Finally, I want to remind people the point of changing this:'''

 > To encourage correct heading usage, the new labels must communicate to
 all editors that '''the heading levels are hierarchical''' and not
 selected based on perceived importance or (obviously) visual appearance.

 Any interface that relies only on how headings look will do more harm than
 good. I have spent hours watching people screw up the use of headings and
 that is the primary mistake they make. (I've written up a list of
 [https://mrwweb.com/common-heading-mistakes/ common heading mistakes I see
 users make].)

 So with all that said, I think we should either do:

 > Heading 2
 > – Heading 3
 > –– Heading 4

 OR

 > Page Title
 > – Heading 2
 > –– Heading 3
 > ––– Heading 4

 This may not be as pretty as renaming them but it is technically
 descriptive and shows hierarchy. Given that, I have a hard time imagining
 a solution that meets the goal better than that.

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


More information about the wp-trac mailing list