[wp-trac] [WordPress Trac] #29358: Remove the 'accesskey` attributes from Quicktags buttons

[WordPress Trac]

#29358: Remove the 'accesskey` attributes from Quicktags buttons
--------------------------+-----------------------------
 Reporter:  azaozz        |       Owner:
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Future Release
Component:  Editor        |     Version:
 Severity:  normal        |  Resolution:
 Keywords:  early         |     Focuses:  accessibility
--------------------------+-----------------------------

Comment (by afercia):

 Replying to [ticket:29358 azaozz]:
 > When there are several instances of Quicktags on the page, using the
 "accesskey" shortcut will focus the corresponding button in the last
 instance, even if it's not visible.

 Spent a whole day investigating on this :) and then came across this
 ticket.
 Things are even trickier: Chrome will always try to activate the last
 instance but other browsers behave differently. Here's
 [http://www.456bereastreet.com/archive/201005/if_you_use_the_accesskey_attribute_specify_unique_values/
 what happens in different browsers when two or more elements share the
 same accesskey value]. That post is a bit old (2010) but still relevant
 and what applies to "Safari" it's valid for Chrome too.

 Btw what's described there it's just the basic behavior. I've run some
 tests and when elements are hidden or cloned things get weirder and
 weirder especially in Firefox.

 I'd definitely agree with @joedolson: remove them all, consider to
 implement instead keyboard shortcuts that match the ones used in TinyMCE
 (but is it worth?).

 Accesskeys may be useful (and it's still a matter of debate between
 experts) just when limited to a very small (no more than 4-5), easy to
 remember, set of main actions that are consistent across an application
 and when numeric values are used to reduce conflicts, for example:
 0: Help
 1: Skip to content
 2: Navigation
 3: Search
 but any different use should be avoided anywhere.
 Not to mention that using letters leads to language issues: for example,
 "b" and "i" suggest "bold" and "italic" but just for English speakers.

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