Date   

Re: Issue with tab key under 2020.3

Scott Salzman
 

If that doesn't work, the Zoom keyboard shortcuts page says that pressing Control + Alt + Shift will move focus to Zoom's meeting controls.

 

Scott

 

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gene via groups.io
Sent: Tuesday, October 13, 2020 7:52 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Issue with tab key under 2020.3

 

Try pressing alt once and see if that solves the problem.  I don't recall just what alt does but it is something like to show or hide the interface.

It’s a toggle.

 

Gene

-----Original Message-----

From: Marcia Yale

Sent: Tuesday, October 13, 2020 6:06 PM

To: nvda@nvda.groups.io

Subject: [nvda] Issue with tab key under 2020.3

 

I can no longer tab around in Zoom. I have disabled the Zoom add-on thinking this was an incompatibility issue, but it didn't solve the problem. I'm using Windows 7.

 

Marcia Yale

It is not our differences that divide us. It is our inability to recognize, accept, and celebrate those differences.

Audre Lorde

 

 

 

 

 

 

 

 

 

 

 

 


Re: Updating NVDA

Quentin Christensen
 

NVDA checks for updates roughly once a day - so if you are active on the list or follow NV Access on social media, you may well see the posts about a new version coming out before your copy goes off to look for it.  That manually running the check for updates feature found the new version indicates that NVDA can check for updates and find the new version, so it likely would have prompted you maybe later in the day or the next day if you hadn't tried earlier.  We could set it to check more often I'm sure, but given we release usually four updates a year, it's arguably not worth it just to try to get in before you see it on the list here :)


On Wed, Oct 14, 2020 at 8:22 AM Kerryn Gunness via groups.io <k_gunness=yahoo.ca@groups.io> wrote:
i go the same as brian and also i check for updates and do the update there
 
----- Original Message -----
Sent: Tuesday, October 13, 2020 2:11 PM
Subject: Re: [nvda] Updating NVDA

I have not come across this, specifically, but my decades of dealing with all sorts of software have shown me that, over time, a lot of software that's been updated, and particularly repeatedly, via "install over" updates often gets wonky.

If/when they do, I simply uninstall them entirely using Control Panel, then install the updated version separately afterward.  This solves these issues in almost all cases.

NVDA makes this particularly easy, since your user data is stored in your own AppData folder, so any configuration changes you've made, add-ons you've installed, etc., are all still there when you do a fresh install.

--

Brian - Windows 10 Pro, 64-Bit, Version 2004, Build 19041  

It’s hard waking up and realizing it’s not always black and white.

     ~ Kelley Boorn

 



--
Quentin Christensen
Training and Support Manager


Re: waterfox error

Quentin Christensen
 

A number of the errors in there appear to relate to Calibre rather than Firefox.  Calibre.exe appears to be in a directory called "Calibre2" - which version are you using?  Calibre, the eBook reader / converter, is currently at version 5.2.0.

Also, are you using any NVDA add-ons?

On Wed, Oct 14, 2020 at 7:05 AM Shaun Everiss <sm.everiss@...> wrote:
Hi.

Installed nvda 2020.3, and now got this error after brousing round a
little online, this seems to happen with blogspot sites, but as I said
things continue to happen as before with latest waterfox.

ERROR - speech.manager.SpeechManager._handleIndex (08:47:46.568) -
MainThread (8668):
Error running speech callback
Traceback (most recent call last):
   File "speech\manager.pyc", line 669, in _handleIndex
   File "speech\commands.pyc", line 326, in run
   File "sayAllHandler.pyc", line 164, in _onLineReached
   File "sayAllHandler.pyc", line 213, in lineReached
   File "documentBase.pyc", line 24, in makeTextInfo
   File "virtualBuffers\__init__.pyc", line 207, in __init__
   File "textInfos\offsets.pyc", line 477, in __init__
   File "virtualBuffers\__init__.pyc", line 225, in _getStoryLength
OSError: [WinError 1775] A null context handle was passed from the
client to the host during a remote procedure call
WARNING - fileUtils.getFileVersionInfo (08:54:07.529) - Dummy-1 (10332):
Invalid or unavailable version info attribute for 'C:\\Program
Files\\Calibre2\\calibre.exe': ProductName
WARNING - fileUtils.getFileVersionInfo (08:54:07.529) - Dummy-1 (10332):
Invalid or unavailable version info attribute for 'C:\\Program
Files\\Calibre2\\calibre.exe': ProductVersion
ERROR - watchdog._watcher (09:01:26.115) - watchdog (10764):
Core frozen in stack!
INFO - watchdog._watcher (09:01:26.119) - watchdog (10764):
Listing stacks for Python threads:
Python stack for thread 13000
(watchdog.CancellableCallThread.execute(<_FuncPtr object at 0x00BA6828>)):
   File "threading.pyc", line 890, in _bootstrap
   File "threading.pyc", line 926, in _bootstrap_inner
   File "watchdog.pyc", line 317, in run
   File "threading.pyc", line 552, in wait
   File "threading.pyc", line 296, in wait

Python stack for thread 10764 (watchdog):
   File "threading.pyc", line 890, in _bootstrap
   File "threading.pyc", line 926, in _bootstrap_inner
   File "threading.pyc", line 870, in run
   File "watchdog.pyc", line 127, in _watcher
   File "watchdog.pyc", line 62, in getFormattedStacksForAllThreads

Python stack for thread 6332 (winInputHook):
   File "threading.pyc", line 890, in _bootstrap
   File "threading.pyc", line 926, in _bootstrap_inner
   File "threading.pyc", line 870, in run
   File "winInputHook.pyc", line 79, in hookThreadFunc

Python stack for thread 9848 (_UIAHandler.UIAHandler.MTAThread):
   File "threading.pyc", line 890, in _bootstrap
   File "threading.pyc", line 926, in _bootstrap_inner
   File "threading.pyc", line 870, in run
   File "_UIAHandler.pyc", line 310, in MTAThreadFunc
   File "queue.pyc", line 170, in get
   File "threading.pyc", line 296, in wait

Python stack for thread 10040 (braille._BgThread):
   File "threading.pyc", line 890, in _bootstrap
   File "threading.pyc", line 926, in _bootstrap_inner
   File "threading.pyc", line 870, in run
   File "braille.pyc", line 2187, in func

Python stack for thread 9660 (synthDrivers._espeak.BgThread):
   File "threading.pyc", line 890, in _bootstrap
   File "threading.pyc", line 926, in _bootstrap_inner
   File "synthDrivers\_espeak.pyc", line 190, in run
   File "queue.pyc", line 170, in get
   File "threading.pyc", line 296, in wait

Python stack for thread 8668 (MainThread):
   File "nvda.pyw", line 215, in <module>
   File "core.pyc", line 550, in main
   File "wx\core.pyc", line 2134, in MainLoop
   File "gui\__init__.pyc", line 1050, in Notify
   File "core.pyc", line 520, in run
   File "queueHandler.pyc", line 88, in pumpAll
   File "queueHandler.pyc", line 55, in flushQueue
   File "scriptHandler.pyc", line 166, in _queueScriptCallback
   File "keyboardHandler.pyc", line 516, in executeScript
   File "inputCore.pyc", line 201, in executeScript
   File "scriptHandler.pyc", line 208, in executeScript
   File "browseMode.pyc", line 451, in <lambda>
   File "browseMode.pyc", line 407, in _quickNavScript
   File "documentBase.pyc", line 27, in _get_selection
   File "documentBase.pyc", line 24, in makeTextInfo
   File "virtualBuffers\__init__.pyc", line 207, in __init__
   File "textInfos\offsets.pyc", line 472, in __init__
   File "virtualBuffers\__init__.pyc", line 212, in _getSelectionOffsets

ERROR - scriptHandler.executeScript (09:01:34.119) - MainThread (8668):
error executing script: <bound method
BrowseModeTreeInterceptor.addQuickNav.<locals>.<lambda> of
<virtualBuffers.gecko_ia2.Gecko_ia2 object at 0x013FE950>> with gesture 'h'
Traceback (most recent call last):
   File "scriptHandler.pyc", line 208, in executeScript
   File "browseMode.pyc", line 451, in <lambda>
   File "browseMode.pyc", line 407, in _quickNavScript
   File "documentBase.pyc", line 27, in _get_selection
   File "documentBase.pyc", line 24, in makeTextInfo
   File "virtualBuffers\__init__.pyc", line 207, in __init__
   File "textInfos\offsets.pyc", line 472, in __init__
   File "virtualBuffers\__init__.pyc", line 212, in _getSelectionOffsets
OSError: [WinError 1726] The remote procedure call failed

I know I posted a dump out there, but  here is a new one.









--
Quentin Christensen
Training and Support Manager


Re: Issue with tab key under 2020.3

Gene
 

Try pressing alt once and see if that solves the problem. I don't recall just what alt does but it is something like to show or hide the interface. It’s a toggle.

Gene

-----Original Message-----
From: Marcia Yale
Sent: Tuesday, October 13, 2020 6:06 PM
To: nvda@nvda.groups.io
Subject: [nvda] Issue with tab key under 2020.3

I can no longer tab around in Zoom. I have disabled the Zoom add-on thinking
this was an incompatibility issue, but it didn't solve the problem. I'm
using Windows 7.

Marcia Yale
It is not our differences that divide us. It is our inability to recognize,
accept, and celebrate those differences.
Audre Lorde


Issue with tab key under 2020.3

Marcia Yale
 

I can no longer tab around in Zoom. I have disabled the Zoom add-on thinking
this was an incompatibility issue, but it didn't solve the problem. I'm
using Windows 7.

Marcia Yale
It is not our differences that divide us. It is our inability to recognize,
accept, and celebrate those differences.
Audre Lorde


News – NV Access - NVDA 2020.3 Released #nvaccessnewsfeed

Quentin Christensen
 

NV Access is pleased to announce that version 2020.3 of NVDA, the free screen reader for Microsoft Windows, is now available for download. We encourage all users to upgrade to this version.

NVDA 2020.3 includes several large improvements to stability and performance, particularly in Microsoft Office applications. There are new settings to toggle touchscreen support and graphics reporting. The existence of marked (highlighted) content can be reported in browsers, and there are new German braille tables.


For the full release information and to download, please visit: https://www.nvaccess.org/post/nvda-2020-3/


Kind regards


Quentin.


--
Quentin Christensen
Training and Support Manager


Re: Updating NVDA

Kerryn Gunness <k_gunness@...>
 


i go the same as brian and also i check for updates and do the update there
 

----- Original Message -----
Sent: Tuesday, October 13, 2020 2:11 PM
Subject: Re: [nvda] Updating NVDA

I have not come across this, specifically, but my decades of dealing with all sorts of software have shown me that, over time, a lot of software that's been updated, and particularly repeatedly, via "install over" updates often gets wonky.

If/when they do, I simply uninstall them entirely using Control Panel, then install the updated version separately afterward.  This solves these issues in almost all cases.

NVDA makes this particularly easy, since your user data is stored in your own AppData folder, so any configuration changes you've made, add-ons you've installed, etc., are all still there when you do a fresh install.

--

Brian - Windows 10 Pro, 64-Bit, Version 2004, Build 19041  

It’s hard waking up and realizing it’s not always black and white.

     ~ Kelley Boorn

 


Re: waterfox error

 

Shaun,

              Please read the following, from the Admin Notice entitled, List Updates: Please Read  (Sent April 11, 2020):

  • Speaking of logs, we should avoid sending long logs to this list.
    • Logs may contain personal information to your system, your set-up, or possibly keystrokes you press, etc.
    • It is not expected that users on this list will know how to read logs, or that they will dissect those logs for you to determine the issue. Please reach out to NVAccess directly. No doubt there is already a process in place for this, however we shouldn't ask users to post logs to this list.

I am asking you, and all other members, not to post logs, or even parts of logs, to this group.  It's not a developers group, there are few here who can possibly decipher logs.  If an issue is believed to be a problem with NVDA, then, as directed, "please reach out to NVAccess directly," by filing an issue [AKA bug] report.
--

Brian - Windows 10 Pro, 64-Bit, Version 2004, Build 19041  

It’s hard waking up and realizing it’s not always black and white.

     ~ Kelley Boorn

 


Re: vocaliser voice updates

 

Hmph, Well I just downloaded and installed the launcher, and got told about updates to vices but left these alone now.

Its up to date.

Thing is it never told me there was an update at all eloquence is also updated but I never knew.



On 13/10/2020 10:51 pm, mattias wrote:

The latest vocalizer sapi are

1.9.0

I downloaded it and no notification about updates

Skickades från E-post för Windows 10

 

Från: Shaun Everiss
Skickat: den 13 oktober 2020 08:15
Till: nvda@nvda.groups.io
Ämne: [nvda] vocaliser voice updates

 

Hi.

 

I have the sapi vocaliser installed.

 

I just downloaded the latest launcher from atguys.

 

There are several voices that state they need updates but there is no

update button.

 

So I uninstalled all voices and reinstalled them again but still get

notifications that some voices have updates.

 

Also tried to change activation status for one system and got an cert

error so maybe I need to wait for code factory to renew their ssl.

 

 

 

 

 

 

 


waterfox error

 

Hi.

I may have fixed my own issue.

At least I can't get it working or failing like this right now.

I toggled say all and the issue stopped at least I think its stopped.

I don't need say all to load, so maybe thats my issue.


waterfox error

 

Forgot the dump

ERROR - speech.manager.SpeechManager._handleIndex (08:47:46.568) - MainThread (8668):
Error running speech callback
Traceback (most recent call last):
  File "speech\manager.pyc", line 669, in _handleIndex
  File "speech\commands.pyc", line 326, in run
  File "sayAllHandler.pyc", line 164, in _onLineReached
  File "sayAllHandler.pyc", line 213, in lineReached
  File "documentBase.pyc", line 24, in makeTextInfo
  File "virtualBuffers\__init__.pyc", line 207, in __init__
  File "textInfos\offsets.pyc", line 477, in __init__
  File "virtualBuffers\__init__.pyc", line 225, in _getStoryLength
OSError: [WinError 1775] A null context handle was passed from the client to the host during a remote procedure call
WARNING - fileUtils.getFileVersionInfo (08:54:07.529) - Dummy-1 (10332):
Invalid or unavailable version info attribute for 'C:\\Program Files\\Calibre2\\calibre.exe': ProductName
WARNING - fileUtils.getFileVersionInfo (08:54:07.529) - Dummy-1 (10332):
Invalid or unavailable version info attribute for 'C:\\Program Files\\Calibre2\\calibre.exe': ProductVersion
ERROR - watchdog._watcher (09:01:26.115) - watchdog (10764):
Core frozen in stack!
INFO - watchdog._watcher (09:01:26.119) - watchdog (10764):
Listing stacks for Python threads:
Python stack for thread 13000 (watchdog.CancellableCallThread.execute(<_FuncPtr object at 0x00BA6828>)):
  File "threading.pyc", line 890, in _bootstrap
  File "threading.pyc", line 926, in _bootstrap_inner
  File "watchdog.pyc", line 317, in run
  File "threading.pyc", line 552, in wait
  File "threading.pyc", line 296, in wait

Python stack for thread 10764 (watchdog):
  File "threading.pyc", line 890, in _bootstrap
  File "threading.pyc", line 926, in _bootstrap_inner
  File "threading.pyc", line 870, in run
  File "watchdog.pyc", line 127, in _watcher
  File "watchdog.pyc", line 62, in getFormattedStacksForAllThreads

Python stack for thread 6332 (winInputHook):
  File "threading.pyc", line 890, in _bootstrap
  File "threading.pyc", line 926, in _bootstrap_inner
  File "threading.pyc", line 870, in run
  File "winInputHook.pyc", line 79, in hookThreadFunc

Python stack for thread 9848 (_UIAHandler.UIAHandler.MTAThread):
  File "threading.pyc", line 890, in _bootstrap
  File "threading.pyc", line 926, in _bootstrap_inner
  File "threading.pyc", line 870, in run
  File "_UIAHandler.pyc", line 310, in MTAThreadFunc
  File "queue.pyc", line 170, in get
  File "threading.pyc", line 296, in wait

Python stack for thread 10040 (braille._BgThread):
  File "threading.pyc", line 890, in _bootstrap
  File "threading.pyc", line 926, in _bootstrap_inner
  File "threading.pyc", line 870, in run
  File "braille.pyc", line 2187, in func

Python stack for thread 9660 (synthDrivers._espeak.BgThread):
  File "threading.pyc", line 890, in _bootstrap
  File "threading.pyc", line 926, in _bootstrap_inner
  File "synthDrivers\_espeak.pyc", line 190, in run
  File "queue.pyc", line 170, in get
  File "threading.pyc", line 296, in wait

Python stack for thread 8668 (MainThread):
  File "nvda.pyw", line 215, in <module>
  File "core.pyc", line 550, in main
  File "wx\core.pyc", line 2134, in MainLoop
  File "gui\__init__.pyc", line 1050, in Notify
  File "core.pyc", line 520, in run
  File "queueHandler.pyc", line 88, in pumpAll
  File "queueHandler.pyc", line 55, in flushQueue
  File "scriptHandler.pyc", line 166, in _queueScriptCallback
  File "keyboardHandler.pyc", line 516, in executeScript
  File "inputCore.pyc", line 201, in executeScript
  File "scriptHandler.pyc", line 208, in executeScript
  File "browseMode.pyc", line 451, in <lambda>
  File "browseMode.pyc", line 407, in _quickNavScript
  File "documentBase.pyc", line 27, in _get_selection
  File "documentBase.pyc", line 24, in makeTextInfo
  File "virtualBuffers\__init__.pyc", line 207, in __init__
  File "textInfos\offsets.pyc", line 472, in __init__
  File "virtualBuffers\__init__.pyc", line 212, in _getSelectionOffsets

ERROR - scriptHandler.executeScript (09:01:34.119) - MainThread (8668):
error executing script: <bound method BrowseModeTreeInterceptor.addQuickNav.<locals>.<lambda> of <virtualBuffers.gecko_ia2.Gecko_ia2 object at 0x013FE950>> with gesture 'h'
Traceback (most recent call last):
  File "scriptHandler.pyc", line 208, in executeScript
  File "browseMode.pyc", line 451, in <lambda>
  File "browseMode.pyc", line 407, in _quickNavScript
  File "documentBase.pyc", line 27, in _get_selection
  File "documentBase.pyc", line 24, in makeTextInfo
  File "virtualBuffers\__init__.pyc", line 207, in __init__
  File "textInfos\offsets.pyc", line 472, in __init__
  File "virtualBuffers\__init__.pyc", line 212, in _getSelectionOffsets
OSError: [WinError 1726] The remote procedure call failed


waterfox error

 

Hi.

Installed nvda 2020.3, and now got this error after brousing round a little online, this seems to happen with blogspot sites, but as I said things continue to happen as before with latest waterfox.

ERROR - speech.manager.SpeechManager._handleIndex (08:47:46.568) - MainThread (8668):
Error running speech callback
Traceback (most recent call last):
  File "speech\manager.pyc", line 669, in _handleIndex
  File "speech\commands.pyc", line 326, in run
  File "sayAllHandler.pyc", line 164, in _onLineReached
  File "sayAllHandler.pyc", line 213, in lineReached
  File "documentBase.pyc", line 24, in makeTextInfo
  File "virtualBuffers\__init__.pyc", line 207, in __init__
  File "textInfos\offsets.pyc", line 477, in __init__
  File "virtualBuffers\__init__.pyc", line 225, in _getStoryLength
OSError: [WinError 1775] A null context handle was passed from the client to the host during a remote procedure call
WARNING - fileUtils.getFileVersionInfo (08:54:07.529) - Dummy-1 (10332):
Invalid or unavailable version info attribute for 'C:\\Program Files\\Calibre2\\calibre.exe': ProductName
WARNING - fileUtils.getFileVersionInfo (08:54:07.529) - Dummy-1 (10332):
Invalid or unavailable version info attribute for 'C:\\Program Files\\Calibre2\\calibre.exe': ProductVersion
ERROR - watchdog._watcher (09:01:26.115) - watchdog (10764):
Core frozen in stack!
INFO - watchdog._watcher (09:01:26.119) - watchdog (10764):
Listing stacks for Python threads:
Python stack for thread 13000 (watchdog.CancellableCallThread.execute(<_FuncPtr object at 0x00BA6828>)):
  File "threading.pyc", line 890, in _bootstrap
  File "threading.pyc", line 926, in _bootstrap_inner
  File "watchdog.pyc", line 317, in run
  File "threading.pyc", line 552, in wait
  File "threading.pyc", line 296, in wait

Python stack for thread 10764 (watchdog):
  File "threading.pyc", line 890, in _bootstrap
  File "threading.pyc", line 926, in _bootstrap_inner
  File "threading.pyc", line 870, in run
  File "watchdog.pyc", line 127, in _watcher
  File "watchdog.pyc", line 62, in getFormattedStacksForAllThreads

Python stack for thread 6332 (winInputHook):
  File "threading.pyc", line 890, in _bootstrap
  File "threading.pyc", line 926, in _bootstrap_inner
  File "threading.pyc", line 870, in run
  File "winInputHook.pyc", line 79, in hookThreadFunc

Python stack for thread 9848 (_UIAHandler.UIAHandler.MTAThread):
  File "threading.pyc", line 890, in _bootstrap
  File "threading.pyc", line 926, in _bootstrap_inner
  File "threading.pyc", line 870, in run
  File "_UIAHandler.pyc", line 310, in MTAThreadFunc
  File "queue.pyc", line 170, in get
  File "threading.pyc", line 296, in wait

Python stack for thread 10040 (braille._BgThread):
  File "threading.pyc", line 890, in _bootstrap
  File "threading.pyc", line 926, in _bootstrap_inner
  File "threading.pyc", line 870, in run
  File "braille.pyc", line 2187, in func

Python stack for thread 9660 (synthDrivers._espeak.BgThread):
  File "threading.pyc", line 890, in _bootstrap
  File "threading.pyc", line 926, in _bootstrap_inner
  File "synthDrivers\_espeak.pyc", line 190, in run
  File "queue.pyc", line 170, in get
  File "threading.pyc", line 296, in wait

Python stack for thread 8668 (MainThread):
  File "nvda.pyw", line 215, in <module>
  File "core.pyc", line 550, in main
  File "wx\core.pyc", line 2134, in MainLoop
  File "gui\__init__.pyc", line 1050, in Notify
  File "core.pyc", line 520, in run
  File "queueHandler.pyc", line 88, in pumpAll
  File "queueHandler.pyc", line 55, in flushQueue
  File "scriptHandler.pyc", line 166, in _queueScriptCallback
  File "keyboardHandler.pyc", line 516, in executeScript
  File "inputCore.pyc", line 201, in executeScript
  File "scriptHandler.pyc", line 208, in executeScript
  File "browseMode.pyc", line 451, in <lambda>
  File "browseMode.pyc", line 407, in _quickNavScript
  File "documentBase.pyc", line 27, in _get_selection
  File "documentBase.pyc", line 24, in makeTextInfo
  File "virtualBuffers\__init__.pyc", line 207, in __init__
  File "textInfos\offsets.pyc", line 472, in __init__
  File "virtualBuffers\__init__.pyc", line 212, in _getSelectionOffsets

ERROR - scriptHandler.executeScript (09:01:34.119) - MainThread (8668):
error executing script: <bound method BrowseModeTreeInterceptor.addQuickNav.<locals>.<lambda> of <virtualBuffers.gecko_ia2.Gecko_ia2 object at 0x013FE950>> with gesture 'h'
Traceback (most recent call last):
  File "scriptHandler.pyc", line 208, in executeScript
  File "browseMode.pyc", line 451, in <lambda>
  File "browseMode.pyc", line 407, in _quickNavScript
  File "documentBase.pyc", line 27, in _get_selection
  File "documentBase.pyc", line 24, in makeTextInfo
  File "virtualBuffers\__init__.pyc", line 207, in __init__
  File "textInfos\offsets.pyc", line 472, in __init__
  File "virtualBuffers\__init__.pyc", line 212, in _getSelectionOffsets
OSError: [WinError 1726] The remote procedure call failed

I know I posted a dump out there, but  here is a new one.


Re: News – NV Access - NVDA 2020.3 Released #nvaccessnewsfeed

molly the blind tech lover
 

I just updated my NVDA.

Works great 😀

I love the new feature where the touch interaction can be toggled on and off.

And NVDA definitely seems more responsive.

I am currently using Microsoft word and NVDA seems more responsive while typing, reading character by character, etc.

I love it 😀

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Rosemarie Chavarria
Sent: Tuesday, October 13, 2020 12:37 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] News – NV Access - NVDA 2020.3 Released #NVAccessNewsFeed

 

It's working great here too. I love the snappy response too.

 

 

On 10/13/2020 9:35 AM, Sharni-Lee Ward wrote:

Just updated! Everything is so so much more responsive now! It responds to my typing faster than it used to in older versions before the update to Python 3!

 

I've only noticed one thing so far, and it's not necessarily a bad thing either, just something new to adjust to. The pauses after periods are shorter. Sentences feel closer together than they did before when reading. Again, this is something I could become accustomed to with time, and isn't necessarily a problem. I do like the snappy response time very much. :)  

On 14/10/2020 1:13 am, nvda@nvda.groups.io Integration wrote:

NVDA 2020.3 Released

By NV Access

NV Access is pleased to announce that version 2020.3 of NVDA, the free screen reader for Microsoft Windows, is now available for download. We encourage all users to upgrade to this version.

NVDA 2020.3 includes several large improvements to stability and performance, particularly in Microsoft Office applications. There are new settings to toggle touchscreen support and graphics reporting. The existence of marked (highlighted) content can be reported in browsers, and there are new German braille tables.

Please note, after updating any software, it is a good idea to restart the computer. Restart by going to the Shutdown dialog, selecting “restart” and pressing ENTER. Updating software can change files which are in use. This can lead to instability and strange behaviour which is resolved by rebooting. This is the first thing to try if you do notice anything odd after updating.

While downloading NVDA, please consider becoming a monthly donor. Contributions like yours help NV Access continue our important work.

We also have a range of training material in the NV Access Shop to help you increase your skills with NVDA. Start with the popular Basic Training for NVDA in electronic text, audio and braille. Save with the NVDA Productivity Bundle. This includes Basic Training, all our Microsoft Office training, and telephone support.

Download NVDA 2020.3

To find out what’s new in this release, please visit What’s new in NVDA 2020.3

Close-up photograph of NVDA logo in notification area.


Re: News – NV Access - NVDA 2020.3 Released #nvaccessnewsfeed

Louise Pfau
 

Hi.  It's working great here.  I love the responsiveness too.  I just checked the "What's new", and I can make excellent use of some of the features.

Louise


Re: Updating NVDA

Leslie <soundsofmusic@...>
 

I just updated NVDA. Because I just found notices on the list.  That was a very easy update, or is it that I am getting used to updating with W10.  Can you believe that I used to be phobic about updating my computer with any older program?  It used to take so long to update with slower computers and programs.  Now it’s even easier to update Windows with these faster computers.  Yippi.

 

Sent from Mail for Windows 10

 

From: Louise Pfau
Sent: Tuesday, October 13, 2020 11:03 AM
To: nvda@nvda.groups.io
Subject: [nvda] Updating NVDA

 


Hi.  I have the "automatically check for updates" and "notify for pending updates on start-up" checkboxes checked, but I don't seem to be getting notifications about updates.  I do receive the notifications when I manually check for updates.  For example, I checked after the notice to the list about the 2020.3 release.  Has anyone else come across this?

Thanks,

Louise

 


Re: web sites detecting a screen reader

Dave Grossoehme
 

Good Day Joseph and Group:  Is it possible to continue this discussion?  It might be helpful to have this discussed on insiders email group- as well.  Is there anyway to have a form set up for how this could be used in the future, so, there isn't a problem with screen readers and web sites?

Dave


On 10/10/2020 6:51 PM, Joseph Lee wrote:

Hi,

Ultimately, it is up to operating systems (such as Windows) to reveal this information to web browsers. On Windows, screen readers can inform Windows that they are active through a Windows API function named SystemParametersInfo (part of user32.dll), which is meant to be used by apps to adjust their workings, and I bet web browsers can expose this information to web authoring engines. Because this is a website-specific thing, I think it would be best to ask web authors to adjust their interfaces on the fly or add a box to suppress this (that last bit will be cleared if you delete web cookies).

To expand upon the API discussion: a few weeks ago some NVDA users working on PowerShell said an alert about PSReadline was issued at startup. A conversation with PowerShell team at Microsoft revealed that this is due to screen reader flag detection, which ironically uses the same Windows API function mentioned above (the difference is which flags are passed into modify system parameters globally). Apparently this was in response to reports that PSReadline module (used for cursor movement, editing and such) wasn’t working well with older NVDA releases, and I advised Microsoft to test PSReadline with newer NVDA releases.

As for web accessibility and screen reader detection on the web, an ongoing discussion between web standards stakeholders (web authors, browser vendors, assistive technology vendors, standards bodies, academics, and such) deals with how should software interpret seemingly conflicting ARIA (Accessible Rich Internet Applications) specifications. For example, should screen readers enter application/focus mode automatically when encountering what is essentially a web dialog, or how should screen readers announce form field descriptions and such. Making matters complicated is the speed of web development as you will find yourself meeting new browser releases every six weeks, and that “web standards implementations” on PC’s have pretty much became a battle between Mozilla on one side and Google and friends across the court. At first glance, NVDA may appear to provide the same experience, but trust me: there are internal differences between what Firefox says versus what Chromium family tells you (which, by the way, extends to how NVDA supports accessibility API’s, which merits a separate discussion; I’ll take a stab at giving you a tour of such topics if requested).

Cheers,

Joseph

 

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Don H
Sent: Saturday, October 10, 2020 5:12 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] web sites detecting a screen reader

 

OK I am a strong believer in using Google to find answers before I ask one here.  Giving me the term SR flag did not help much in resolving this issue.  I tried all kinds of searches using SR flag and got nothing.  Maybe you can be a little more helpful in hiding the screen reader from web pages.

On 10/10/2020 6:59 PM, Joseph Lee wrote:

Hi,

That magic term is “sr flag”.

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Brian Vogel
Sent: Saturday, October 10, 2020 4:07 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] web sites detecting a screen reader

 

Don,

          I don't think you can stop the websites, but I could swear that it was recently discussed that you can put screen readers, and I think it was NVDA in particular, into "stealth mode" at startup so that whatever flag it is that the screen reader sets/waves to tell software looking for it that it's present is not set.  But I'll be darned if I can remember the magic search term to find that discussion.

--

Brian - Windows 10 Pro, 64-Bit, Version 2004, Build 19041  

It’s hard waking up and realizing it’s not always black and white.

     ~ Kelley Boorn

 


Re: Updating NVDA

 

I have not come across this, specifically, but my decades of dealing with all sorts of software have shown me that, over time, a lot of software that's been updated, and particularly repeatedly, via "install over" updates often gets wonky.

If/when they do, I simply uninstall them entirely using Control Panel, then install the updated version separately afterward.  This solves these issues in almost all cases.

NVDA makes this particularly easy, since your user data is stored in your own AppData folder, so any configuration changes you've made, add-ons you've installed, etc., are all still there when you do a fresh install.

--

Brian - Windows 10 Pro, 64-Bit, Version 2004, Build 19041  

It’s hard waking up and realizing it’s not always black and white.

     ~ Kelley Boorn

 


Updating NVDA

Louise Pfau
 


Hi.  I have the "automatically check for updates" and "notify for pending updates on start-up" checkboxes checked, but I don't seem to be getting notifications about updates.  I do receive the notifications when I manually check for updates.  For example, I checked after the notice to the list about the 2020.3 release.  Has anyone else come across this?

Thanks,

Louise


Re: Creating a portable copy of nvda.

Tony Ballou
 

Hi,

 

I haven’t created a portable copy of NVDA for quite some time.  However, I believe that this can be done using a USB flash.  Check section 3.2 of the users guide which is in the NVDA help menu for further details on it.

 

Tony

From: Emmanuel Junaid
Sent: Sunday, October 11, 2020 12:50 PM
To: nvda@nvda.groups.io
Subject: [nvda] Creating a portable copy of nvda.

 

Hey there! I want to ask if it's possible to make a portable copy of nvda in an USB disk and make it autorun?
If yes, what's the process?

 


Re: News – NV Access - NVDA 2020.3 Released #nvaccessnewsfeed

Oleksandr Gryshchenko
 

It works great!

Thank you for your efforts!

8561 - 8580 of 86570