Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

improving current access to QT applications #852

Closed
nvaccessAuto opened this issue Aug 23, 2010 · 3 comments
Closed

improving current access to QT applications #852

nvaccessAuto opened this issue Aug 23, 2010 · 3 comments
Labels
task

Comments

@nvaccessAuto
Copy link

Reported by arfy on 2010-08-23 14:19
Currently, NVDA can provide access to applications written using the Nokia (formally troltech) QT GUI toolkit. However, there are still problems that show up in it's use. Note this is based on a fairly cursary look at QT creator that comes with the QT sdk, 2010.04, GPL edition. However, even so, some fairly major blocks to full access were found.

  1. when tabbing through dialogs, bits of html were presented as part of the control description. for example:

press tab. "Boarder. feedback button". press tab. Boarder, select an example... menu button submenu".

On further investigation with object nav, it appears that the "boarders" are actually unlabeled group boxes.

And, an example of html showing up.
To get this, open qt creator, and hit escape to clear the welcome/getting started screen. then shift-tab once. You'll here,
Status bar. Show Sidebar span style = color "grey" fontsize=small, alt-0."

  1. The help system and any web content showing is based on webKit, so, it might be time to create yet another, virtual buffer backend, perhaps...
  2. Text fields don't seem to be navigable with cursor keys.
    edit's are identified as edit, submenu, and combo boxes, while identified right, and the contents initially read, don't speak as you cursor up and down to change values.

I'm sure there's other things, but those wer the first three that came to mind for now.
@nvaccessAuto
Copy link
Author

Comment 1 by jteh (in reply to comment description) on 2010-08-23 22:34
Generally, it's better to file separate issues as separate tickets. Even though these are all related to QT, they are very different issues. Nevertheless, replies below:

Replying to arfy:

press tab. "Boarder. feedback button". press tab. Boarder, select an example... menu button submenu".

On further investigation with object nav, it appears that the "boarders" are actually unlabeled group boxes.

I have no idea why QT exposes these are borders. If you discover that all "borders" in QT are actually group boxes, we could just hack the role to "grouping" for QT.

  1. The help system and any web content showing is based on webKit, so, it might be time to create yet another, virtual buffer backend, perhaps...

No can do. Webkit's accessibility support requires some improvement before we can do this. See my first comment on #734 for details.

  1. Text fields don't seem to be navigable with cursor keys.

edit's are identified as edit, submenu, and combo boxes, while identified right, and the contents initially read, don't speak as you cursor up and down to change values.

Unfortunately, there's nothing we can do about this either. QT needs to implement support for IAccessible2 (specifically, IAccessibleText) in order to enable access to editable text fields.

The combo box issue is different and is due to them not firing the correct events when the combo box changes. There's probably nothing we can do about that on our side either, although I need to investigate that one further.

@nvaccessAuto
Copy link
Author

Comment 2 by heikofolkerts on 2013-07-30 18:33
While we can't do anything on the NVDA site to most of the described things, we could open a ticket in the QT tracker and make our users vote for this bug. I opened a bug in the QT tracker for something different some years ago but it didn't get any respect so far since very litle people voted for it.

@jcsteh
Copy link
Contributor

jcsteh commented Jun 28, 2017

Qt 5 has been out for some time now and it includes major accessibility improvements, including access to editable text fields via IAccessible2 and significant bug fixes. Also, NVDA now treats borders as layout. There are certainly still problems with Qt accessibility, but these should be filed as separate issues (and ideally against Qt itself).

@jcsteh jcsteh closed this as completed Jun 28, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
task
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jcsteh @nvaccessAuto