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

Windows Logon: Incorrect password alert not always read #4937

Closed
nvaccessAuto opened this issue Feb 20, 2015 · 10 comments
Closed

Windows Logon: Incorrect password alert not always read #4937

nvaccessAuto opened this issue Feb 20, 2015 · 10 comments
Labels
bug close/worksforme p4 https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priority

Comments

@nvaccessAuto
Copy link

Reported by Diego on 2015-02-20 20:32
Hello developers!
to enter the password incorrectly on the logon screen, NVDA does not read the password is incorrect, having to press tab or the command to read the dialogue.
@nvaccessAuto
Copy link
Author

Comment 1 by jteh on 2015-02-20 21:49
Confirmed. Nothing seems to actually get focus (at least as far as accessibility is concerned) when you press enter after entering an incorrect password, which is a bug in Windows. We'll need to work around it, though. I think there's some sort of alert event that Narrator is using to at least read the message (though it too can't find the focus).
Changes:
Changed title from "NVDA does not automatically reads the security screen" to "Windows Logon: Incorrect password alert not always read"
Milestone changed from None to next

@nvaccessAuto
Copy link
Author

Comment 2 by JamaicanUser on 2015-04-27 14:02
Anybody knows how JAWS deals with this issue?

@nvaccessAuto nvaccessAuto added this to the next milestone Nov 10, 2015
@jcsteh jcsteh modified the milestones: 2016.2, next Feb 15, 2016
@jcsteh jcsteh modified the milestones: 2016.2, 2016.3 May 6, 2016
@josephsl
Copy link
Collaborator

Hi,

Partly addressed in PR #6073 (at least for password entry (not PIN) in Windows 10). Workaround is to press TAB.
Thanks.

@jcsteh jcsteh removed this from the 2016.3 milestone Aug 5, 2016
@jcsteh jcsteh added the p4 https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priority label Aug 7, 2016
@fisher729
Copy link

@jcsteh, do you think this issue can be closed? I have certainly seen this fixed by issues such as #6010. I haven't seen this happen in a very long time.

@josephsl
Copy link
Collaborator

josephsl commented Aug 2, 2017 via email •
edited by feerrenrut

@jcsteh
Copy link
Contributor

jcsteh commented Aug 2, 2017

This works in Windows 10. I'm not sure about the status for Windows 8/8.1. I don't think they use the live region event, but they possibly use the system alert event, which was also implemented in #7282. Any Win 8/8.1 users able to test this?

@Adriani90
Copy link
Collaborator

I do not have this issue on Windows 8.1. I will close this as works for me. @diego if you still have this issue, please comment on this one and we can reopen it. Thanks.

@chojiro
Copy link
Contributor

chojiro commented Mar 17, 2020

This still happens in Windows 10 version 1909 for me, as well as previous Windows 10/NVDA releases.

Currently on Windows 10 1909 and NVDA 2019.3.1.

@feerrenrut
Copy link
Contributor

@chojiro This issue is old, closed, and doesn't have very specific information. Could you please open a new issue to describe your particular case?

@chojiro
Copy link
Contributor

chojiro commented Mar 17, 2020

#10881 is open.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug close/worksforme p4 https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priority
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
8 participants
@chojiro @feerrenrut @jcsteh @josephsl @fisher729 @nvaccessAuto @ehollig @Adriani90