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

Windows 8.1 and NVDA #3627

Closed
nvaccessAuto opened this issue Nov 7, 2013 · 1 comment
Closed

Windows 8.1 and NVDA #3627

nvaccessAuto opened this issue Nov 7, 2013 · 1 comment

Comments

@nvaccessAuto
Copy link

Reported by Daniel Langeron on 2013-11-07 14:32
This is not an incident report but some questions about the evolutions of Windows 8 and their impacts on NVDA.

Some time ago NVDA users could expect to use the Nokia - Lumia smartphones based on Windows 8. Unfortunately, the conclusions of the TT # 2608 (Refer to Note 1) were clear, namely : ” … it will not be possible to run any third party screen readers on Windows 8 RT or Phone.”
Newer versions of smartphones, phablets and tablets operating under Windows continue to be ARM-based. It is expected that they will use Windows Phone 8.1 (Windows Phone Blue) and as such the use of NVDA to navigate these devices will always be impossible.
In the new generation of Microsoft Surface 2 tablets only tablet Surface Pro 2 based on an x86 platform allows the use of NVDA.
Today, in the world of mobile devices, if we except Tablet PC ("two in one" devices), it appears that NVDA can be used very rarely.
Yet there is a new Intel chip family (Refer to Note 2) which would make possible the production of x86 based smartphones, phablets and tablets running “plain” Windows 8.1 instead of ARM-powered devices running Windows 8.1 RT or Phone.
This is the solution adopted by Dell in its recent tablet (competing with Surface Pro 2): The Dell Venue 11 Pro tablet which, like any device based on x86 (PC or Tablet PC), allows to use NVDA.
NVDA users would benefit Microsoft and Nokia adopt these new chips! But one can wonder if a major element of the new strategy of Microsoft is not to move closer to the ARM architecture and the Metro / Modern UI ?

While the maturation of Windows Phone Blue (8.1) continues, many articles are published. A persistent rumor emerges from these articles, it relates to the gradual disappearance of the Desktop (Refer to Note 3, 4, 5)
The question now is what will happen to the Desktop of the devices using an x86-platform ? If the Desktop in this case was also called to be more “discreet” and eventually disappear what would be the consequences for NVDA ?
But perhaps is this fear unfounded ?
Thanks, Daniel.
Notes
1 : [: [http://www.zdnet.com/microsofts-mobile-strategy-where-android-ios-and-windows-8-1-fit-in-7000017352/](http://community.nvda-project.org/ticket/2608]
2)
3 : [: [http://www.zdnet.com/microsoft-starts-de-emphasizing-the-desktop-with-surface-2-7000022372/](http://www.zdnet.com/what-comes-next-after-windows-8-1-7000022034/]
4)
5 : [http://windowsitpro.com/windows-8/windows-desktop-death]

@nvaccessAuto
Copy link
Author

Comment 1 by jteh on 2013-11-08 08:28
The development list is a better place for this discussion. This tracker is entirely for issue reports. Nevertheless, since this will no doubt be asked again, here's a fairly short answer.

The reality is that there is too much speculation and not enough definite information to provide any useful answers. That said, even if phones do start running on Intel chips, I suspect they may not run a full desktop experience. Microsoft, following in Apple's footsteps, seem committed to locking down newer platforms as much as possible, which is part of the new Windows Store ecosystem. Also, the desktop environment (and thus most desktop apps) weren't designed for low power environments. If the desktop environment does disappear, NVDA in its current form will not function. Furthermore, unless Microsoft removes some restrictions from the Windows Store app environment, no third party assistive technology can run in that environment. The situation will be the same as it is for Windows RT. Obviously, I really hope I'm wrong. We'll have to wait and see.
Changes:
Added labels: invalid
State: closed

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

1 participant