Opened 7 years ago

Last modified 7 years ago

#11470 confirmed Task

A11yhelp dialog needs attention — at Version 1

Reported by: Olek Nowodziński Owned by:
Priority: Normal Milestone:
Component: Accessibility Version:
Keywords: Cc:

Description (last modified by Olek Nowodziński)

There are several things concerning the dialog that should be investigated/fixed/re-factorized:

  1. Keyboard button labels are not consistent

    Editor Context Menu Press Shift+Ctrl+F10 or APPLICATION KEY to open context-menu. Then move to next menu option with TAB or DOWN ARROW. Move to previous option with SHIFT+TAB or UP ARROW. Press SPACE or ENTER to select the menu option. [...]

This is because some labels are hard-coded (upper case) and some are generated from langfiles (lower case). #11196 allowed translation of keys and we should take advantage of that feature. All hard-coded labels must be converted into dynamic ones.

  1. We must verify whether help strings still match editor features. Some of them may be outdated/irrelevant/misleading. If necessary, some new ones should be written.
  1. We must investigate a11y aspect of the dialog, e.g. compatibility with screen readers (JAWS). Perhaps <kbd> tags would be suitable here and there.

Related tickets we could also take into consideration:

  • #8490: Plugins should extend a11yhelp to make the dialog dynamic and (build/editor)-dependent. At the moment a11yhelp creates a delusion that some features are enabled while, in fact, the plugins to which they belong are not even loaded.
  • #9638: "Press ALT 0 for help" iframe voice label makes no sense when a11yhelp is not loaded (i.e. basic build).

Change History (1)

comment:1 Changed 7 years ago by Olek Nowodziński

Description: modified (diff)
Note: See TracTickets for help on using tickets.
© 2003 – 2019 CKSource – Frederico Knabben. All rights reserved. | Terms of use | Privacy policy