Joseph, I'm going to be honest with you.
toggle quoted messageShow quoted text
I've tried the current releases of NVDA 2018.2, Developer's Master and this new Try Build release. The Try-Build release seems to work best on my system running the latest build of Microsoft Windows 10 Version 1803 (OS Build 17134.165.)
Edge is much more responsive when using this TB release. Maybe it's some sort of fluke, but I really do like how this build works with Windows applications overall.
Could the key be is to run the other two builds in portable mode for the Try-Build I'm running that way?
On 7/13/2018 2:25 PM, Joseph Lee wrote:
I advise against making my try build the primary version of NVDA on your computer for three important reasons:
1. New NVDA developments may break the try build, and in many cases, my try build will be out of date with "reality" too quickly (once the new release process is fully implemented and things start to pour into alpha builds).
2. Windows 10 uses continuous delivery model. In other words, things can change at a blink of an eye. The try build I wrote yesterday assumes you've got Windows 10 Version 1709 (build 16299) or later, and for emoji panel in particular, it assumes Windows 10 Redstone 5. In recent weeks Microsoft made significant changes to emoji panel in Redstone 5 builds, which means certain things won't work as advertised in older and newer builds.
3. My try build is not an official NV Access try build. This means no updates, no official support from NV Access, things won't work as expected when installed, no touchscreen support (very important for certain Windows 10 features) and so on.
For all practical purposes, you should install Windows 10 App Essentials add-on until such time when I say all major features from that add-on become part of NVDA screen reader (right now, it isn't). That's because:
1. Windows 10 App Essentials uses continuous delivery model. Unlike most of my add-ons I created or maintain (except another one), there is no major or minor releases of this add-on (at least on paper). Latest stable versions do include new features from Insider Preview builds, bug fixes, needed features for NVDA users and what not.
2. This add-on serves as a public testing version of pull requests that'll be sent to Nv Access after a period of usage. In recent months, NV Access has incorporated features from this add-on into NVDA. In one particular case, Mick Curran took inspiration from my add-on for a feature, and throughout 2017, I wrote or helped writing features seen today, including search suggestion sounds (originally came from my add-on).
There are certain things the add-on cannot do due to hacks involved, but for many things, the add-on should suffice.
From: email@example.com <firstname.lastname@example.org> On Behalf Of Kenny
Sent: Friday, July 13, 2018 11:08 AM
Subject: Re: [nvda] Microsoft Edge is Starting to Grow on Me.
This Try-Build works great Joseph. I've only installed the Mozilla Apps Enhancements and Speech History extensions. NVDA works seamlessly with various Microsoft applications, especially Edge.
Always believed it's better to incorporate Windows app improvements into the main NVDA program, without having to install an extension.
Think I may stick with this NVDA build as my primary screen reader for
now on out.
On 7/13/2018 1:18 PM, Joseph Lee wrote:
In short, the try build I posted yesterday is really Windows 10 App Essentials add-on incorporated inside NVDA itself. For months some folks have been asking me about inclusion of features from this add-on into NVDA screen reader directly, and yesterday's try build is a taste of that. Except for roledescription in Edge, features included are part of my add-on (that reminds me: I forgot to include a crucial feature in the try build (announcing the virtual desktop you're switching to), which I'll address in Version 1808).
From: email@example.com <firstname.lastname@example.org> On Behalf Of Sarah k Alawami
Sent: Friday, July 13, 2018 9:56 AM
To: Nvda List <email@example.com>
Subject: Re: [nvda] Microsoft Edge is Starting to Grow on Me.
Yes. That is before the add on. I noticed that when I was on a job website yesterday. It’s very flid and works a lot better.
On Jul 13, 2018, at 9:52 AM, Kenny <firstname.lastname@example.org> wrote:
Well with Joseph's announcement about the NVDA Try Build, I decided to invest more time in using Microsoft's applications on my Windows 10 PC.
Started things off with the Microsoft Edge browser.
Not sure if it's the new Try-Build or a lot of changes have recently been made to Edge overall, but it works pretty damn well with NVDA.
NVDA reads All of the push notification bar messages automatically. It also informs me when the page has fully loaded (Loading complete.) Most of the NVDA quick navigation key shortcuts do work to quickly jump through web content.
Love... love... love... the Reading View ([Ctrl]+[Shift]+[r]) feature of Edge. This alone is starting to make me a Chrome to Edge convert.
I hate to say it, but managing Favorites in Edge is much much easier to do then with Chrome in my humble opinion. Microsoft uses a traditional Treeview structure in their manager. Very nice!
The only problem I'm having is when I find myself sometimes being placed in the toolbar icons pain of Edge. I quickly jump back to the web page content by pressing [F6]. I just get annoyed with this at times.
Curious why they don't implement a shortcut key to display that entire pain (Similar to [Ctrl]+[i] for Favorites, [Ctrl]+[h] for History, and [Ctrl]+[j] for Downloads?) I could simply hit the [Escape] key to hide/dismiss it again.
Reading Joseph's recent email regarding the Try-Build of NVDA being released and us really caring about the changes Microsoft is implementing all the time to make their line of Windows applications more accessible got me thinking.
Why can't I give their programs a chance? Yes, in the past I've
experienced a lot of problems with their applications. That doesn't
mean they've not made efforts to correct things (Due to feedback from
Insider testers and bug reports.)
Time for me to start using the free tools Microsoft has developed and stop searching for replacements. And I mean all of the tools (Even the bug report and feedback submission tools.) This is key to helping Microsoft fix things they may not yet be aware of.
By the way, if you want a nice resource listing Microsoft Edge keyboard shortcuts:
It really has morphed into a pretty good browser. I'm going to start using it more.