Hi Christophe, I understand your concern regarding the accessibility in design. On my page, I've talked about your concern and how I think it and be addressed if the future of LibreOffice is a theme similar to the "Ribbon UI". In the near future I will update the design on my page with some of the accessibility issues you have mentioned.
Nice you meet you, Evan Janusziewicz -----Original Message----- From: Christophe Strobbe [mailto:[email protected]] Sent: Thursday, September 08, 2011 6:26 AM To: [email protected] Subject: Re: [libreoffice-accessibility] Hi All! Mock-up. Hi Evan, At 01:55 6-9-2011, Evan Janusziewicz wrote: >I'm just making sure this gets to the whole design team. I've created a >mock-up of what LibreOffice could be like in the future. It's on my >wiki profile at twstdude0to1. I assume you are referring to the second mockup at <http://wiki.documentfoundation.org/User:twstdude0to1>. A few very things to bear in mind for a new design: * Theme support, especially high contrast themes (often with larger fonts), is essential for users with certain vision impairments. It has been a while since I tested high-contrast support in OpenOffice.org or LibreOffice, but I thought it worked fine, so this should not be lost in the new design. * Keyboard access: for example, a ribbon-based interface needs to be just as easy to access by keyboard as a menu-based interface. (I still don't know how to use the keyboard to select a formatting style in the MS Word 2010 ribbon, for example.) * Focus visibility for sighted keyboard users: this is currently not an issue in menus and dialogs, but it also needs to work well in task panels and dockable panes. For example, open the Navigator (press F5), dock it, then press F6 to cycle through the menu, the toolbar(s) etcetera, until you arrive at the Navigator, then use the arrow keys to navigate the buttons at the top of the Navigator. (Someone should test this with a high-contrast theme on Windows, Mac OS, Gnome and KDE to see whether contrast is sufficient for low vision users.) * Accessibility to assistive technologies, for example, exposing name, state, properties of menu items and other UI components through the accessibility API. Best regards, Christophe -- Christophe Strobbe K.U.Leuven - Dept. of Electrical Engineering - SCD Research Group on Document Architectures Kasteelpark Arenberg 10 bus 2442 B-3001 Leuven-Heverlee BELGIUM tel: +32 16 32 85 51 http://www.docarch.be/ Twitter: @RabelaisA11y --- Open source for accessibility: results from the AEGIS project www.aegis-project.eu --- Please don't invite me to Facebook, Quechup or other "social networks". You may have agreed to their "privacy policy", but I haven't. -- Unsubscribe instructions: E-mail to [email protected] 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 -- Unsubscribe instructions: E-mail to [email protected] 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
