Dialog's control access keys are not discoverable

[Marek Lewandowski]

It was surprising to see that we actually have some mechanism for access keys. We need end user documentation on this matter, as it's not discoverable at all.

We need to provide some additional information for that. Ideally the solution would be to put it in the dialog itself.

A cructial thing here is that we want to make it perceivable to all users.

aria-describedby would be handy for giving this information to a screen reader, but not sure how to nicely present this information to sighted user.

• Approach similar to Linux/Windows accelerator keys (if you press access key modificator key, then associated character gets underlined) would be the best fit, but it requires major code changes so it would take considerable amount of time.
• Displaying constantly it next to label is not an option too, as:
  • it doesn't fit the design
  • we don't want bloat UI with information that will be useful only for smaller part of users
• Listing dialog access keys in resources like [Accessibility Support and Keyboard Shortcuts](​http://sdk.ckeditor.com/samples/accessibility.html) or in A11y help dialog (alt+0). Still terrible idea, because we'd end up with just too much information in a very inconvienient place.

Additionally we'd only list hotkeys for official plugins, and these wouldn't be updated automatically.

Curious to know other people opinions.

[Marek Lewandowski]

Setting version back to 4.0 but I believe it was never implemented.

[Jakub Ś]

We could have fade away or fixed small message "Press Alt+XYZ for hot keys" between top bar and tabs. Key shortcut could navigate to A11y dialog (the easiest) or some special dialog especially created for “hot keys”.

In that second case it doesn't make sense to create dialog just for a fixed set of keys. A dedicated plugin which allows adding keys for custom plugins could be created.