WordPress.org

Make WordPress Core

Opened 4 years ago

Closed 19 months ago

Last modified 14 months ago

#39271 closed defect (bug) (worksforme)

Help shortcut conflicts with VoiceOver Help shortcut (Mac)

Reported by: iseulde Owned by:
Milestone: Priority: normal
Severity: normal Version:
Component: TinyMCE Keywords:
Focuses: accessibility Cc:

Description (last modified by iseulde)

Both are using Control+Option+H.

To enable VoiceOver, press Command+F5.

Change History (5)

#1 @iseulde
4 years ago

  • Description modified (diff)

Actually it looks like quite a lot of shortcuts are conflicting, if not all. The Control+Option "space" seems to be used by VoiceOver.

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

#4 @afercia
19 months ago

  • Focuses accessibility added
  • Milestone set to Future Release
  • Status changed from new to reopened

I'm reopening this issue for the same reason I've reopened #43773. Worth considering many users with accessibility needs will stick to the Classic Editor. These users need keyboard shortcuts to work with their screen readers. This ticket applies to all the keyboard shortcuts that use Control+Option+something, as many of these combination are already used by VOiceOer on macOS.

Specifically for the Help modal shortcut, there's now https://core.trac.wordpress.org/ticket/45791

Also, the same issue can be reproduced on Gutenberg, see https://github.com/WordPress/gutenberg/issues/11154

#5 @azaozz
19 months ago

  • Milestone Future Release deleted
  • Resolution set to worksforme
  • Status changed from reopened to closed

The shortcut was changed to Shift + Alt/Option + H. This doesn't seem to conflict with anything.

#6 @afercia
19 months ago

Thanks @azaozz :) I think the only thing left is the iframe title? On a mac, it still says

Rich Text Area. Press Control-Option-H for help.

WordPress 5.1 is in soft string freeze though. Maybe is it possible to use the string for Windows?

#7 @azaozz
19 months ago

Yeah, it should use the same string as on Windows. Will try to see why it's different on a Mac.

Note: See TracTickets for help on using tickets.