Date   

Re: Introducing support for selective UIA event registration in NVDA Alpha snapshots

Bill Dengler
 

Hi,
Is it possible to disable this on a per-process level?
I've written an app module (a self-contained version of #10910) that needs to react to background windows from the app.

Thanks,
Bill

-----Original Message-----
From: nvda-devel@groups.io <nvda-devel@groups.io> On Behalf Of Joseph Lee
Sent: Monday, 6 July 2020 02:20
To: nvda-devel@groups.io
Subject: Re: [nvda-devel] Introducing support for selective UIA event registration in NVDA Alpha snapshots

Hello everyone,
Folks on NVDA add-ons list may have seen the below message, but just to reiterate:
For people using Windows 10 App Essentials: you'll notice that if you do enable the option described here, you won't be able to hear emoji panel changes as you scroll through emoji categories. I'm testing a potential temporary fix, which will be rolling out to development snapshot users soon.
As noted by Leonard, please do file issues on GitHub should you notice regressions.
Cheers,
Joseph


-----Original Message-----
From: nvda-devel@groups.io <nvda-devel@groups.io> On Behalf Of Leonard de Ruijter
Sent: Sunday, July 5, 2020 11:11 PM
To: nvda-devel@groups.io; program-l@...
Subject: [nvda-devel] Introducing support for selective UIA event registration in NVDA Alpha snapshots

Dear all,


As many of you may know, people using Microsoft Visual Studio or other applications mainly accessed by UIAutomation can experience some major lag while using them with NVDA. In an attempt to fix this, I've spent some hours in coming up with an approach that majorly improves performance in these applications. Thanks to great feedback from NV Access and them merging it, it can now be enabled in most recent NVDA Alpha snapshots by enabling the "Enable selective registration for UI Automation events and property changes" option in NVDA's advanced settings.


Taking Visual Studio as an example, with this option enabled, I notice major performance improvements in the following areas:

* Nuget package manager

* Loading/moving through the error list

* Options like go to base, go to implementation, go to definition. etc.

Performance improvements aren't limited to that though. To go a bit technical, rather than requesting for all UIA events and processing/discarding them in NVDA's process, we're now mostly only requesting events for objects of interest. This means that many events fired on other controls than the focused control aren't simply discarded by NVDA, but rather not even seen by NVDA at all, thereby taking out the processing time needed to discard them.

As there might be some regressions introduced by this feature, it is marked advanced/experimental. As I hope it eventually will become the default, I'd really appreciate it if you could report any bugs or regressions perceived with this feature enabled on NVDA's Github.


Kind regards,

Leonard


Re: Introducing support for selective UIA event registration in NVDA Alpha snapshots

 

Hello everyone,
Folks on NVDA add-ons list may have seen the below message, but just to reiterate:
For people using Windows 10 App Essentials: you'll notice that if you do enable the option described here, you won't be able to hear emoji panel changes as you scroll through emoji categories. I'm testing a potential temporary fix, which will be rolling out to development snapshot users soon.
As noted by Leonard, please do file issues on GitHub should you notice regressions.
Cheers,
Joseph

-----Original Message-----
From: nvda-devel@groups.io <nvda-devel@groups.io> On Behalf Of Leonard de Ruijter
Sent: Sunday, July 5, 2020 11:11 PM
To: nvda-devel@groups.io; program-l@...
Subject: [nvda-devel] Introducing support for selective UIA event registration in NVDA Alpha snapshots

Dear all,


As many of you may know, people using Microsoft Visual Studio or other applications mainly accessed by UIAutomation can experience some major lag while using them with NVDA. In an attempt to fix this, I've spent some hours in coming up with an approach that majorly improves performance in these applications. Thanks to great feedback from NV Access and them merging it, it can now be enabled in most recent NVDA Alpha snapshots by enabling the "Enable selective registration for UI Automation events and property changes" option in NVDA's advanced settings.


Taking Visual Studio as an example, with this option enabled, I notice major performance improvements in the following areas:

* Nuget package manager

* Loading/moving through the error list

* Options like go to base, go to implementation, go to definition. etc.

Performance improvements aren't limited to that though. To go a bit technical, rather than requesting for all UIA events and processing/discarding them in NVDA's process, we're now mostly only requesting events for objects of interest. This means that many events fired on other controls than the focused control aren't simply discarded by NVDA, but rather not even seen by NVDA at all, thereby taking out the processing time needed to discard them.

As there might be some regressions introduced by this feature, it is marked advanced/experimental. As I hope it eventually will become the default, I'd really appreciate it if you could report any bugs or regressions perceived with this feature enabled on NVDA's Github.


Kind regards,

Leonard


Introducing support for selective UIA event registration in NVDA Alpha snapshots

 

Dear all,


As many of you may know, people using Microsoft Visual Studio or other applications mainly accessed by UIAutomation can experience some major lag while using them with NVDA. In an attempt to fix this, I've spent some hours in coming up with an approach that majorly improves performance in these applications. Thanks to great feedback from NV Access and them merging it, it can now be enabled in most recent NVDA Alpha snapshots by enabling the "Enable selective registration for UI Automation events and property changes" option in NVDA's advanced settings.


Taking Visual Studio as an example, with this option enabled, I notice major performance improvements in the following areas:

* Nuget package manager

* Loading/moving through the error list

* Options like go to base, go to implementation, go to definition. etc.

Performance improvements aren't limited to that though. To go a bit technical, rather than requesting for all UIA events and processing/discarding them in NVDA's process, we're now mostly only requesting events for objects of interest. This means that many events fired on other controls than the focused control aren't simply discarded by NVDA, but rather not even seen by NVDA at all, thereby taking out the processing time needed to discard them.

As there might be some regressions introduced by this feature, it is marked advanced/experimental. As I hope it eventually will become the default, I'd really appreciate it if you could report any bugs or regressions perceived with this feature enabled on NVDA's Github.


Kind regards,

Leonard


Re: Error running scons source

Nathaniel Schmidt
 

Glad my reply was helpful.  I was literally taking a stab in the dark.

Nathaniel

========================================
Nathaniel Schmidt
Undergraduate student
Bachelor of Computer Science (S306)
School of information Technology
Faculty of Science, Engineering and Built Environment
Deakin University, cloud campus
https://sync.deakin.edu.au/profiles/student/njschmidt

E: njschmidt@...
M: 0439591709
GitHub: https://github.com/njsch/
Skype: nathaniel_schmidt1994

7

On 4 Jul 2020, at 4:22 pm, Noelia Ruiz <nrm1977@...> wrote:

Hello, many thanks. You gave me the key to solve the problem and find
the appropiate components in the dialog.
I have my NVDA source tree ready now. :)
Unfortunately the app module which I wanted to submit as a PR doesn't
work when it's placed in source\appModules, just when it's included in
scratchpad.
I have commented this at
https://github.com/nvaccess/nvda/issues/11302

Best

2020-07-04 0:42 GMT+02:00, Nathaniel Schmidt <schmidty2244@...>:
Hi,

Not sure if this is necessarily the cause of your problem but I think you
also need the x86_64 components as well.

Nathaniel

========================================
Nathaniel Schmidt
Undergraduate student
Bachelor of Computer Science (S306)
School of information Technology
Faculty of Science, Engineering and Built Environment
Deakin University, cloud campus
https://sync.deakin.edu.au/profiles/student/njschmidt

E: njschmidt@...
M: 0439591709
GitHub: https://github.com/njsch/
Skype: nathaniel_schmidt1994

7

On 4 Jul 2020, at 6:06 am, Noelia Ruiz <nrm1977@...> wrote:

Hello:

I get the following error when running scons source to prepare NVDA's
source code:
scons: *** [build\arm64\IAccessible2proxy.dll] Error 1104
scons: building terminated because of errors.
I see that, in individual components for Visual Studio 2019, there are
several checkboxes with similar names related to:
* MSVC v142 - VS 2019 C++ ARM64 build tools
          * C++ ATL for v142 build tools (ARM64)
I have checked the first checkbox related to these components.
May this issue be related to this? What are the exact checkboxes that
should be selected?

I have created an app module to fix issue #11302, where I described a
bug with Thorium reader and I was trying to create a PR, so I tried to
test in NVDA source code before submitting it, after testing with the
app module placed in the scratchpad folder.
This app module maybe too small to be maintained as a separate add-on,
so I was trying to send a PR.
Thanks











Re: Error running scons source

Noelia Ruiz
 

Hello, many thanks. You gave me the key to solve the problem and find
the appropiate components in the dialog.
I have my NVDA source tree ready now. :)
Unfortunately the app module which I wanted to submit as a PR doesn't
work when it's placed in source\appModules, just when it's included in
scratchpad.
I have commented this at
https://github.com/nvaccess/nvda/issues/11302

Best

2020-07-04 0:42 GMT+02:00, Nathaniel Schmidt <schmidty2244@...>:

Hi,

Not sure if this is necessarily the cause of your problem but I think you
also need the x86_64 components as well.

Nathaniel

========================================
Nathaniel Schmidt
Undergraduate student
Bachelor of Computer Science (S306)
School of information Technology
Faculty of Science, Engineering and Built Environment
Deakin University, cloud campus
https://sync.deakin.edu.au/profiles/student/njschmidt

E: njschmidt@...
M: 0439591709
GitHub: https://github.com/njsch/
Skype: nathaniel_schmidt1994

Sent from my iPhone 7

On 4 Jul 2020, at 6:06 am, Noelia Ruiz <nrm1977@...> wrote:

Hello:

I get the following error when running scons source to prepare NVDA's
source code:
scons: *** [build\arm64\IAccessible2proxy.dll] Error 1104
scons: building terminated because of errors.
I see that, in individual components for Visual Studio 2019, there are
several checkboxes with similar names related to:
* MSVC v142 - VS 2019 C++ ARM64 build tools
* C++ ATL for v142 build tools (ARM64)
I have checked the first checkbox related to these components.
May this issue be related to this? What are the exact checkboxes that
should be selected?

I have created an app module to fix issue #11302, where I described a
bug with Thorium reader and I was trying to create a PR, so I tried to
test in NVDA source code before submitting it, after testing with the
app module placed in the scratchpad folder.
This app module maybe too small to be maintained as a separate add-on,
so I was trying to send a PR.
Thanks





Re: Error running scons source

Nathaniel Schmidt
 

Hi,

Not sure if this is necessarily the cause of your problem but I think you also need the x86_64 components as well.

Nathaniel

========================================
Nathaniel Schmidt
Undergraduate student
Bachelor of Computer Science (S306)
School of information Technology
Faculty of Science, Engineering and Built Environment
Deakin University, cloud campus
https://sync.deakin.edu.au/profiles/student/njschmidt

E: njschmidt@...
M: 0439591709
GitHub: https://github.com/njsch/
Skype: nathaniel_schmidt1994

7

On 4 Jul 2020, at 6:06 am, Noelia Ruiz <nrm1977@...> wrote:

Hello:

I get the following error when running scons source to prepare NVDA's
source code:
scons: *** [build\arm64\IAccessible2proxy.dll] Error 1104
scons: building terminated because of errors.
I see that, in individual components for Visual Studio 2019, there are
several checkboxes with similar names related to:
* MSVC v142 - VS 2019 C++ ARM64 build tools
           * C++ ATL for v142 build tools (ARM64)
I have checked the first checkbox related to these components.
May this issue be related to this? What are the exact checkboxes that
should be selected?

I have created an app module to fix issue #11302, where I described a
bug with Thorium reader and I was trying to create a PR, so I tried to
test in NVDA source code before submitting it, after testing with the
app module placed in the scratchpad folder.
This app module maybe too small to be maintained as a separate add-on,
so I was trying to send a PR.
Thanks




Error running scons source

Noelia Ruiz
 

Hello:

I get the following error when running scons source to prepare NVDA's
source code:
scons: *** [build\arm64\IAccessible2proxy.dll] Error 1104
scons: building terminated because of errors.
I see that, in individual components for Visual Studio 2019, there are
several checkboxes with similar names related to:
* MSVC v142 - VS 2019 C++ ARM64 build tools
* C++ ATL for v142 build tools (ARM64)
I have checked the first checkbox related to these components.
May this issue be related to this? What are the exact checkboxes that
should be selected?

I have created an app module to fix issue #11302, where I described a
bug with Thorium reader and I was trying to create a PR, so I tried to
test in NVDA source code before submitting it, after testing with the
app module placed in the scratchpad folder.
This app module maybe too small to be maintained as a separate add-on,
so I was trying to send a PR.
Thanks


Native support for tab controls?

Karl-Otto Rosenqvist
 

Hi!
I just received info from a developer of an application I'm trying to make more accessible with NVDA. There are two messages one can send to get info about what tab that's selected and info about the tab.

https://docs.microsoft.com/en-us/windows/win32/controls/tcm-getcursel
https://docs.microsoft.com/en-us/windows/win32/controls/tcm-getitem

Are there already support in NVDA to grab this information somehow or do I have to implement these messages?


Kind regards

Karl-Otto

--
Karl-Otto Rosenqvist
MAWINGU
Orgnr: 750804-3937
0701- 75 98 56
karl-otto@...
https://mawingu.se


Re: Using Windows Sandbox with NVDA?

Akash Kakkar
 

As now the sandboxie is open source now, let's what comes on the table

On 6/28/20, Akash Kakkar <akash.misc07@...> wrote:
Thanks Joseph.
Ya Sandboxie is awesome. I was using it untill some time back since 2012

On 6/28/20, DaVid <dhf360@...> wrote:
I don't like windows sandbox, I prefer to use sandboxie. But NVDA is
unreliable with this software.
Also Windows sandbox is included with windows pro only.
Any solution for this?

Sorry to comment this here. I sent a message a long time ago about
this topic, but no one replied.
The compatibility with screen readers is enabled. So, I don't know if
this can be solved with a configuration or is NVDA issue.
Sandboxie can be used correctly with JAWS.

Regards,
DaVid.




Re: Using Windows Sandbox with NVDA?

Akash Kakkar
 

Thanks Joseph.
Ya Sandboxie is awesome. I was using it untill some time back since 2012

On 6/28/20, DaVid <dhf360@...> wrote:
I don't like windows sandbox, I prefer to use sandboxie. But NVDA is
unreliable with this software.
Also Windows sandbox is included with windows pro only.
Any solution for this?

Sorry to comment this here. I sent a message a long time ago about
this topic, but no one replied.
The compatibility with screen readers is enabled. So, I don't know if
this can be solved with a configuration or is NVDA issue.
Sandboxie can be used correctly with JAWS.

Regards,
DaVid.




Re: Using Windows Sandbox with NVDA?

DaVid
 

I don't like windows sandbox, I prefer to use sandboxie. But NVDA is
unreliable with this software.
Also Windows sandbox is included with windows pro only.
Any solution for this?

Sorry to comment this here. I sent a message a long time ago about
this topic, but no one replied.
The compatibility with screen readers is enabled. So, I don't know if
this can be solved with a configuration or is NVDA issue.
Sandboxie can be used correctly with JAWS.

Regards,
DaVid.


Re: Using Windows Sandbox with NVDA?

 

Hi,
You can toggle full screen mode by pressing Control+Alt+Break (turn off full screen mode to toggle out of Sandbox window). To really exit Widnows Sandbox, you need to exit out of full screen and close Sandbox from the host (avoid shutting down the sandboxed guest from the guest itself as it causes errors).
Cheers,
Joseph

-----Original Message-----
From: nvda-devel@groups.io <nvda-devel@groups.io> On Behalf Of Akash Kakkar
Sent: Sunday, June 28, 2020 2:17 AM
To: nvda-devel@groups.io
Subject: Re: [nvda-devel] Using Windows Sandbox with NVDA?

Hi Joseph,
So, how do I come out off sandbox environment? because
alt+control+break doesn't work relyably. is there any other command
which may be I'm not aware about?
Hi Brian
Actually I haven't tried it with narrator since I don't use it at all

On 6/28/20, Joseph Lee <@joslee> wrote:
Hi,
Once Windows Sandbox opens, you need to copy NVDA installer to Sandbox
guest's desktop and run it. Unless you let Windows Sandbox use full
screen (Control+Alt+Break), you won't be able to use majority of NVDA commands.
Cheers,
Joseph

-----Original Message-----
From: nvda-devel@groups.io <nvda-devel@groups.io> On Behalf Of Brian's
Mail list account via groups.io
Sent: Sunday, June 28, 2020 12:11 AM
To: nvda-devel@groups.io
Subject: Re: [nvda-devel] Using Windows Sandbox with NVDA?

Does Narrator support it by any chance? If yes then maybe it can be
used, but if not, well.
Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
Newsgroup monitored: alt.comp.blind-users
----- Original Message -----
From: "Akash Kakkar" <akash.misc07@...>
To: "nvda-addons" <nvda-addons@nvda-addons.groups.io>; "nvda-devel"
<nvda-devel@groups.io>
Sent: Sunday, June 28, 2020 7:21 AM
Subject: [nvda-devel] Using Windows Sandbox with NVDA?


Hey all,
I want to know that how can we use Windows Sandbox with NVDA?
Is there any addon available for this?
If native support is available, then how?
Any help will be appreciated.









Re: Using Windows Sandbox with NVDA?

Akash Kakkar
 

Hi Joseph,
So, how do I come out off sandbox environment? because
alt+control+break doesn't work relyably. is there any other command
which may be I'm not aware about?
Hi Brian
Actually I haven't tried it with narrator since I don't use it at all

On 6/28/20, Joseph Lee <@joslee> wrote:
Hi,
Once Windows Sandbox opens, you need to copy NVDA installer to Sandbox
guest's desktop and run it. Unless you let Windows Sandbox use full screen
(Control+Alt+Break), you won't be able to use majority of NVDA commands.
Cheers,
Joseph

-----Original Message-----
From: nvda-devel@groups.io <nvda-devel@groups.io> On Behalf Of Brian's Mail
list account via groups.io
Sent: Sunday, June 28, 2020 12:11 AM
To: nvda-devel@groups.io
Subject: Re: [nvda-devel] Using Windows Sandbox with NVDA?

Does Narrator support it by any chance? If yes then maybe it can be used,
but if not, well.
Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
Newsgroup monitored: alt.comp.blind-users
----- Original Message -----
From: "Akash Kakkar" <akash.misc07@...>
To: "nvda-addons" <nvda-addons@nvda-addons.groups.io>; "nvda-devel"
<nvda-devel@groups.io>
Sent: Sunday, June 28, 2020 7:21 AM
Subject: [nvda-devel] Using Windows Sandbox with NVDA?


Hey all,
I want to know that how can we use Windows Sandbox with NVDA?
Is there any addon available for this?
If native support is available, then how?
Any help will be appreciated.









Re: Using Windows Sandbox with NVDA?

 

Hi,
Once Windows Sandbox opens, you need to copy NVDA installer to Sandbox guest's desktop and run it. Unless you let Windows Sandbox use full screen (Control+Alt+Break), you won't be able to use majority of NVDA commands.
Cheers,
Joseph

-----Original Message-----
From: nvda-devel@groups.io <nvda-devel@groups.io> On Behalf Of Brian's Mail list account via groups.io
Sent: Sunday, June 28, 2020 12:11 AM
To: nvda-devel@groups.io
Subject: Re: [nvda-devel] Using Windows Sandbox with NVDA?

Does Narrator support it by any chance? If yes then maybe it can be used, but if not, well.
Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
Newsgroup monitored: alt.comp.blind-users
----- Original Message -----
From: "Akash Kakkar" <akash.misc07@...>
To: "nvda-addons" <nvda-addons@nvda-addons.groups.io>; "nvda-devel"
<nvda-devel@groups.io>
Sent: Sunday, June 28, 2020 7:21 AM
Subject: [nvda-devel] Using Windows Sandbox with NVDA?


Hey all,
I want to know that how can we use Windows Sandbox with NVDA?
Is there any addon available for this?
If native support is available, then how?
Any help will be appreciated.



Re: Using Windows Sandbox with NVDA?

Brian's Mail list account
 

Does Narrator support it by any chance? If yes then maybe it can be used, but if not, well.
Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
Newsgroup monitored: alt.comp.blind-users

----- Original Message -----
From: "Akash Kakkar" <akash.misc07@...>
To: "nvda-addons" <nvda-addons@nvda-addons.groups.io>; "nvda-devel" <nvda-devel@groups.io>
Sent: Sunday, June 28, 2020 7:21 AM
Subject: [nvda-devel] Using Windows Sandbox with NVDA?


Hey all,
I want to know that how can we use Windows Sandbox with NVDA?
Is there any addon available for this?
If native support is available, then how?
Any help will be appreciated.


Using Windows Sandbox with NVDA?

Akash Kakkar
 

Hey all,
I want to know that how can we use Windows Sandbox with NVDA?
Is there any addon available for this?
If native support is available, then how?
Any help will be appreciated.


Re: sounds on wsl commendline

Luke Davis
 

The best advice I can give you, is that google is your friend.

If you want to do something, think of how someone else might have asked how to do a similar thing, and google it.

You will find a lot from stackexchange, stackoverflow, and similar forum Q&A sites.

Everyone I know "learned by doing", so I don't really know many "beginner" resources.

One site that you really must know about if you want to work in the bash shell, whether you're a beginner or a long time pro, is this one below. Playing with these examples will teach you a great deal.

http://mywiki.wooledge.org/BashFAQ
And related:
http://mywiki.wooledge.org/BashGuide

This will be my last comment on this thread, as this seems rather off topic.

Luke

On Fri, 26 Jun 2020, UMIT ERDEM Yigitoglu wrote:

thank you for all of you it works. do you have any suggestiond/advice for a biggener comendline user? is there a good resource to learn it more or anything
I should be aware of?
Thank you again.


Re: sounds on wsl commendline

UMIT ERDEM Yigitoglu
 

thank you for all of you it works. do you have any suggestiond/advice for a biggener comendline user? is there a good resource to learn it more or anything I should be aware of?
Thank you again. 
best regards


collection of very useful resources for developing NVDA

J.G
 

Hello,

I found a huge collection of libraries, frameworks etc in/for python, which may help developers to develop NVDA core and/or addons.
https://github.com/vinta/awesome-python
some resources have been already used byNVDA though.

hope, it could be helpful.

best regards,
Jožef


Enhanced Touch gestures notice: global touch support toggle and touch gesture passthrough features to be removed in a future release

 

Hello NVDA developers and add-ons community,

 

I’m delighted to announce that two major features from Enhanced Touch Gestures add-on are being considered for inclusion in a future NVDA release (or rather, one is already here, the other is being looked at). As such, the following features will be removed from the add-on in a future release:

 

  • Enable/disable touch support completely: the ability to enable or disable touch support (also being aware of profiles) is now part of latest NVDA alpha snapshot.
  • Command to enable/disable touch support and touch passthrough: until now it was possible to enable or disable touch support through a command that comes with the add-on, and to suspend touch support for up to ten seconds (touch passthrough). There is an NVDA pull request (PR 11297) to bring this to NVDA itself (not written by me), and if approved, touch passthrough (automatic and manual) will be removed from the add-on, as it is no longer needed.

 

Because many people are using NVDA stable releases (or trying out betas), these changes will not happen overnight – it will happen in a future version of Enhanced Touch Gestures. However, in order to make this process as smooth as possible, I’m laying the foundation in version 20.07 of the add-on (July). Specifically:

 

  • Last tested version will be set to 2020.3 (at least in the add-on manifest). This is to remind me that I need to conduct more tests in coming days.
  • If touch support is disabled globally, an appropriate debug log message will be printed.
  • The add-on does come with an extension point action handler for configuration profile switches. If an NVDA version with the ability to toggle touch support is in use, the action handler will ignore config profile switches altogether, as that is now handled by NVDA.
  • Automatic touch passthrough (where touch support can be suspended for up to ten seconds) will be deprecated. The only passthrough mode will be manual i.e. touch support can be toggled from everywhere, not suspended for a time. Automatic touch passthrough will be removed in a fall release. The user interface responsible for setting up automatic touch passthrough will be removed, however i.e. no more “Enhanced Touch Gestures” settings panel (the only thing left in there will be enable/disable touch support checkbox, meant for older NVDA releases).
  • As part of toggling touch support from everywhere, a keyboard command is proposed (see the mentioned PR). If this comes to NVDA, Enhanced Touch Gestures will add the same keyboard command to toggle manual touch passthrough mode for ease of transition.

 

The result of this work is that Enhanced Touch Gestures add-on will be left with the following features:

 

  • Global object mode gestures (read title, read status bar, for instance)
  • Additional NVDA command gestures (four finger double tap to toggle input help, for instance)
  • Web and synth settings touch modes
  • Touch keyboard enhancements

 

P.S. Coordinate announcement beep feature will be removed, too (that feature is beyond the scope of this post).

Thanks.

Cheers,

Joseph