[Libreoffice-qa] Improving UI Accessibility

Robinson Tryon bishop.robinson at gmail.com
Thu Nov 21 11:25:14 PST 2013

Hi QA,

Per our discussion at the QA Meeting on Monday[1], I talked to the ESC
about our concerns with keyboard a11y issues in new/converted UIs.

ESC was helpful in suggesting several steps to remedy these shorfalls including
* Turning bugs into EasyHacks that can be more easily addressed
* Providing documentation on a11y testing/dev tools

Stuart/Florian R. - Thank you for bringing these problems up at the QA
Meeting. A11y is really important for us as a project, and it's great
to have people ensuring that we're not regressing as we improve
LibreOffice's UI. I'd like you two to take the lead on addressing
these bugs and providing feedback in a format that's actionable by the

Regarding testing, perhaps there are specific things that we could do
with MozTrap to identify a11y-relevant changes early-on. Sophie -
thoughts? :-)

Stuart -- you mentioned several key issues that affect multiple teams
in the project:

* "capricious assignments made in widget UI...impact the Documentation effort"
* "Special key usage—KEY_F6, KEY_F10 with modifiers and the movements
they control should be consistent across all UI layouts."
* "Graphical placement of Widget buttons and dialogs must also have
logical sequencing..."

As these issues affect multiple teams including Design, Documentation,
QA, Development, etc.., perhaps we need to improve communication with
the a11y team to be able to better-address these issues. I'm not sure
how other projects address these concerns (maybe we could ask projects
like Gnome?), but I'd like to have a11y be considered early-on in the
development process so that once a Design is approved and implemented
and arrives in QA for testing, any general a11y concerns have already
been noted.


[1] https://wiki.documentfoundation.org/QA/Meetings/2013/December_02#PENDING_ITEM:_Start_Center_and_Sidebar_Concerns

More information about the Libreoffice-qa mailing list