Date: prev next · Thread: first prev next last

Re: [libreoffice-accessibility] Display bindings


Hi

I still believe there is a bug or maybe we should call it an enhancement request. It is true that accelerators are exposed properly through IAccessible::get_accKeyboardShortcut, as they should. But reading Microsoft notes [1] on the matter suggests that one should expose the keyboard shortcut, aka Ctrl + O, together with the menu item name. This is also how, for example, Firefox, Chrome, Internet Explorer, Acrobat Reader does it. Am I missing some reason as to why we would not want to do the same.

However Stuarts instructions in the previous mail is enough to quickly get around in LibreOffice. Note also that there are extensive information on keyboard shortcuts in the LibreOffice help. Se for example:
https://help.libreoffice.org/Common/General_Shortcut_Keys_in
or:
https://help.libreoffice.org/Writer/Shortcut_Keys_for_Writer


[1] http://msdn.microsoft.com/en-us/library/windows/desktop/dd318482%28v=vs.85%29.aspx

Regards,
Niklas Johansson


--
To unsubscribe e-mail to: accessibility+unsubscribe@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

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.