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

Avira free anti virus version 14.0.7.468: NVDA does not read the items in the tree view opened through Extras submenu > Detections List > Help button #4805

Closed
nvaccessAuto opened this issue Jan 14, 2015 · 2 comments

Comments

@nvaccessAuto
Copy link

Reported by bhavyashah on 2015-01-14 13:17
Steps to reproduce
1 Download, install and open Avira free anti virus version 14.0.7.468.
2 Go to Extras submenu > Detections list > Help button.
3 You land on a tree view, where:
Expected Result : NVDAD should read the names of the tree view items as it usually does, at least through alternate methods like object navigation and screen review.
Actual Result : NVDA does not announce the name of the tree view item, instead simply says ‘tree view item x of y level z’, where x, y and z are variables of the item/total items/level number. Object navigation and screen review were unable to reveal any information either.
Narrator remained totally silent, didn’t even announce the entering of a tree view, or that the user was actually navigating tree view items x of y level z. Narrator's silence may possibly be due to my inexperience in using it.
Test Environment : Windows 7 Ultimate 32 bit
Avira free anti virus version 14.0.7.468
NVDA version 2014.4 stable

@nvaccessAuto
Copy link
Author

Comment 1 by enes on 2015-01-14 14:20
hi,
this is resolvable by disabling avira's self protection mechanism
in the avira interface, with nvda, most list views and treeviews are not read and on some, the nvda error sound plays.
this problem does not exist with jaws
couldn't the nvda devs find a way to expose the gui without dactivating the self defense mechanisms

@LeonarddeR
Copy link
Collaborator

Closing as duplicate of #4804, which is most likely the same underlying issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants