[kleopatra] [Bug 331062] New: Kleopatra doesn't report accessibility information through the QT accessibility infra structure
Heiko Folkerts
heiko at hfolkerts.de
Wed Feb 12 19:03:57 GMT 2014
https://bugs.kde.org/show_bug.cgi?id=331062
Bug ID: 331062
Summary: Kleopatra doesn't report accessibility information
through the QT accessibility infra structure
Classification: Unclassified
Product: kleopatra
Version: 2.2.0
Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
Severity: major
Priority: NOR
Component: general
Assignee: kdepim-bugs at kde.org
Reporter: heiko at hfolkerts.de
CC: mutz at kde.org
When using a screen reader like NVDA www.nvda-project.org one cannot nteract
with kleopatra. The controls are not recognized and have no label. So a screen
reader user doesn't know what the button etc. is about that has the focus.
The problem can be solved by providing the following properties for all GUI
elements:
- accessible_name - the caption of the control
- accessible_description - a kind of tooltip explaining the control further
- accessible_role - this is only needed if the controls don't inherit from the
QT base control classes.
In addition the folder accessibility from the plugins folder of the QT
libraries (containing a few DLLs) have to be installed in the application
folder so QT finds the accessibility plugin libs when a screen reader is in
use.
Fixing this bug would enable blind people to use gnupg especially gpg4win.
Reproducible: Always
Steps to Reproduce:
1.run the screen reader and open up Kleopatra. Tabbing arround will not give
helpful speech output from the screen reader.
2.
3.
Expected Results:
Helpful descriptions about the controls so one can operate the application
without seeing the screen.
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the Kdepim-bugs
mailing list