Re: Announcing NVDA 2016.2.1RS1 (20160613)


mk360
 

The problem is one can't choose if windows 10 home edition updates or not, only the time to restart and install updates. So probably the windows of some people (including my self) will be updated automatically.

Regards,
mk.

On Tue, Jun 14, 2016 at 7:12 PM, Joseph Lee <joseph.lee22590@...> wrote:

Hi,

The Anniversary Update (Redstone) is in the final development phase, so once it is officially released, your computer will upgrade it. But please hold off until NVDA 2016.3, as I, Jamie, Mick and others are working on some fixes at the moment.

Cheers,

Joseph

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Arianna Sepulveda
Sent: Tuesday, June 14, 2016 4:10 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Announcing NVDA 2016.2.1RS1 (20160613)

 

Joseph, I've been a little confused by windows 10 and this Redstone thing. I am using Windows 10 home edition, so I don't have any control over what and when updates are installed. Do I need to be worried about Redstone? I don't want to suddenly find myself upgraded to it, and to be running a version of NVDA that doesn't work well with it, and not be able to get this try build version of NVDA onto my computer.

 

 

Thanks,

Ari


On Jun 14, 2016, at 3:07 PM, Joseph Lee <joseph.lee22590@...> wrote:

Hi everyone,

 

Some of you may recall a message I sent a few days ago announcing a try build of NVDA that supports Redstone. The update to this build is now out:

https://t.co/WasodNKlh5

 

Overview:

·         Includes features and sacrifices from NVDA 2016.2.1 (due to issues, grammar error announcement is gone in 2016.2.1 until a better solution is found).

·         Based on latest NVDA master (live beta) snapshot. Don’t worry if you hear error tones.

·         This build is optimized for Windows 10 Anniversary Update Preview build 14342 or later. The recommended build is 14361.

 

Differences from regular NVDA 2016.2.1 release:

·         Does not support updates.

·         Based on development branch code.

·         Do not install this build unless if you’d like to try out several items outlined below.

·         Due to ever-changing nature of Windows 10, updated builds of this kind will be released if accessibility fixes are required after Microsoft releases Insider builds.

·         Important: This is a third-party build. If you’d like to use snapshots from NV Access, please use either master or next snapshots, or use the latest released version (2016.2.1).

 

Changelog:

·         Redesigned UAC dialog is now announced (if you install this try build). In recent Redstone builds, UAC dialog has received a complete redesign – no longer a desktop dialog, it is now powered by Universal Windows Platform. This means all screen readers are affected when it comes to announcing UAC prompts.

·         NVDA now announces contents of sign-in and other secure screens in Redstone and other Windows 10 builds (also includes Threshold (10240 and 10586) builds).

·         You can now activate password edit box if you’re using touchscreens (may not work properly; don’t worry, all the provisions are there).

·         NVDA will announce status messages if you type a wrong password.

·         Browse mode makes a partial return in Microsoft Edge (ironically, it does not work in Edge itself, but it does work in Feedback Hub app).

 

Important things to note on current Windows 10 Redstone builds:

·         Invalid entry announcement: gone in build 14361 (a XAML (eXtensible Application Markup Language) markup problem in universal apps framework is to blame).

·         If you are using build 14361 and if you happen to restart NVDA, Start search suggestions will not be announced. The workaround is to launch Narrator, do a search, and then NVDA will start announcing suggestions (likely an issue with unresponsive or slow UI Automation).

·         Certain dialogs are not recognized as dialogs nor contents are announced. I’m actively hunting for these dialogs (partly caused by UI Automation tagging issue where NV Access and Microsoft have differing opinions on what a dialog is).

 

Contributing code: if you’d like to see the beauty of this build and/or help fix Windows 10 issues, please let me know. As always, source code of this and other NVDA artifacts can be obtained from the following location:

http://github.com/nvaccess/nvda

My own lab of NVDA code (where I have several experimental branches not found in NV Access repository) can be found at:

http://github.com/josephsl/nvda

 

Sending feedback: If you have feedback regarding this build, please send them to me directly (joseph.lee22590@...), via Twitter at @joslee or Facebook at josephsl. Thank you.

Cheers,

Joseph


Join nvda@nvda.groups.io to automatically receive all group messages.