@Tom, *, No, you're asking the right question. But you do need to look under the bonnet from time to time.
Within the LibreOffice code there are two broad classes of keyboard accelerators. One is associated with the .uno action associated with each object in the user interface. The other are specific key functions defined globally. Most of the current implementation can be reviewed here: Other than the GenericCommands.xcu, different modules assign "access keys" as needed http://opengrok.libreoffice.org/xref/core/officecfg/registry/data/org/openoffice/Office/UI/ These are the "global" "keyboard accelerator/short-cut keys" and each LibreOffice module responds in some fashion to them. The KEY_MOD1 and KEY_MOD2 differ depending on OS. http://opengrok.libreoffice.org/xref/core/vcl/source/window/keycod.cxx The native accessibility bridges handle only the first, the "access keys". But does so pretty effectively at this point. Enhancement would be to do as Mozilla and Adobe (and I assume Google) have done, and simply label each menu item (or button) with its "keyboard accelerator/short-cut key" as appropriate for the function. The rub would come with needing to accommodate keys for each OS and possibly UI issues with the l10n/i18n support. -- View this message in context: http://nabble.documentfoundation.org/libreoffice-accessibility-Display-bindings-tp4131697p4132420.html Sent from the Accessibility mailing list archive at Nabble.com. -- To unsubscribe e-mail to: accessibility+unsubscr...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/accessibility/ All messages sent to this list will be publicly archived and cannot be deleted