Unable to dismiss the lock screen in recent builds of Windows 10 #5220

Closed
nvaccessAuto opened this Issue Jul 14, 2015 · 2 comments

1 participant

@nvaccessAuto

Reported by mdcurran on 2015-07-14 00:29
It has always been possible to dismiss the lock screen on Win 10 by the invoke pattern of the UIA element for the lock screen container (parent containing the date/time and network status etc). However in recent builds this element had changed such that NVDA no longer recognised it as having a presentation type of content and therefore would skip it when exploring with touch. This container should be classed as content so that it can be explored and then invoked with double tap.

@nvaccessAuto

Comment 1 by Michael Curran <mick@... on 2015-07-14 00:32
In [5622497]:
```CommitTicketReference repository="" revision="5622497f989c1c16dd45c0b65dc37e060dd22e6a"
Merge branch 't5220' into next. Incubates #5220

Changes:
Added labels: incubating
@nvaccessAuto

Comment 2 by James Teh <jamie@... on 2015-07-31 03:16
In [4d21ecd]:
```CommitTicketReference repository="" revision="4d21ecddc6cea6afaca8367c12d0afe99bb54719"
The Windows 10 lock screen can now be dismissed using a touch screen.

Add a lockApp appModule for the Win 10 lock screen, so that it is possible to touch explore to the lock screen container itself thus then allowing dismissal of the screen with a double tap.
Fixes #5220.

Changes:
Removed labels: incubating
State: closed
@nvaccessAuto nvaccessAuto added this to the 2015.3 milestone Nov 10, 2015
@michaelDCurran michaelDCurran added a commit that referenced this issue Nov 23, 2015
@michaelDCurran michaelDCurran The Windows 10 lock screen can now be dismissed using a touch screen.
Add a lockApp appModule for the Win 10 lock screen, so that it is possible to touch explore to the lock screen container itself thus then allowing dismissal of the screen with a double tap.
Fixes #5220.
4d21ecd
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment