Sure, we could  make a distinction as Microsoft does, between the "access
key" and a "keyboard accelerator/shortcut-key".

But, as you know the majority of AT support in OOo and derivatives like
LibreOffice is structured around the accessibleRole assigned to an
object--and from that comes accessibleName  and "access key" attributes if

For objects that have VCL or UI based "access keys" attributes, those are
exposed to the UNO Accessibility API as the object is navigated, and the
respective native accessibility bridge handles it--as the user has

Menu items and GUI widgets (buttons, spinners, etc.)  that do not have an
"access key" assigned will sound either the objects name or it's tooltip.
Those that do, will also sound the name and the "access key". 

With the shift of most of the GUI to UI, most "access keys" no longer are
<Alt>+letter combinations. Rather they are just the letter -- and that might
need to be adjusted at some point.

But global "keyboard accelerator/shortcuts-keys",  normally structured with
<Ctrl>+letter, or <Ctrl>+<Shift>+letter are not otherwise exposed to AT as
they are not associated with the UI object.  

Anyhow, looking at a Firefox session, there they have simply adjusted the
objects accessibleName  and are appending the global shortcut-key to the
name!   Nothing special.  The "access key" associated with the accessible
object is exposed with AT.  It is exactly the same with Adobe Reader.

So, we could do the same, pretty trivial as it is only label changes, and
some coordination with the l10n/i18n teams.


View this message in context:
Sent from the Accessibility mailing list archive at

To unsubscribe e-mail to:
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted

Reply via email to