Topics

The new microsoft edge chromium based browser troubles with nvda not going to browse mode


hurrikennyandopo ...
 

Hi guys


In the stable version of NVDA 2019.2 NVDA works nicely with the new Microsoft Edge chromium based browser.


I just downloaded the latest snap shot of the Alfa branch to keep on testing it with and it looks like the browse mode function is broken. It seems to be stuck in focus mode and will not change to browse mode with nvda key + space bar.


Has any one else noticed this with the latest alfa of NVDA it still seems to be working ok with google browser etc that I have on this computer but not the chromium based microsoft edge at present.


I am wondering if some thing has corrupted in the alfa snap shot so am asking others for feed back to see if it is.


Gene nz


--
Check out my website for NVDA tutorials and other blindness related materials at http://www.accessibilitycentral.net

To find out which library networks in New Zealand have a copy of the NVDA screen reader on them and there library locations please go to http://www.accessibilitycentral.net/nz%20libraries%20with%20nvda.html
To find a NVDA certified expert near you, please visit the following link https://certification.nvaccess.org/. The certification page contains the official list of NVDA certified individuals from around the world, who have sat and successfully passed the NVDA expert exam.


David Csercsics
 

The new Edge works fine here with the NVDA alpha, unless you downloaded a later version than the one I have. I'll have a look at that. But I used it this morning and it was behaving as expected.


hurrikennyandopo ...
 

Hi


I deleted out the portable version of the latest alfa snap shot as of this morning and installed a fresh copy.


Getting the same results when you go into the new microsoft edge dev version of the browser.

It does not do it with the stable version of nvda 2019.2



It goes to load and seems like it does not. You can not use your tab keys or arrow keys nor go from focus mode to browse mode in it now.

I have set nvda to debug if this helps.


INFO - __main__ (14:40:39.372):
Starting NVDA
INFO - core.main (14:40:39.591):
Config dir: C:\nvda alfa snapshots\userConfig
INFO - config.ConfigManager._loadConfig (14:40:39.591):
Loading config: .\userConfig\nvda.ini
INFO - config.ConfigManager._loadConfig (14:40:39.622):
Config loaded (after upgrade, and in the state it will be used by NVDA):
{'schemaVersion': '3', 'development': {}, 'upgrade': {}, 'general': {'language': 'Windows', 'saveConfigurationOnExit': 'True', 'askToExit': 'True', 'playStartAndExitSounds': 'True', 'loggingLevel': 'DEBUG', 'showWelcomeDialogAtStartup': 'False'}, 'update': {'autoCheck': 'True', 'startupNotification': 'True', 'allowUsageStats': 'False', 'askedAllowUsageStats': 'True'}, 'speech': {'synth': 'espeak', 'outputDevice': 'Microsoft Sound Mapper', 'oneCore': {'voice': 'HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Speech_OneCore\\Voices\\Tokens\\MSTTS_V110_enUS_DavidM', 'volume': '100'}, 'espeak': {'voice': 'en', 'variant': 'max', 'rate': '30', 'pitch': '40', 'inflection': '75', 'volume': '100'}}, 'braille': {'noBraille': {}}, 'keyboard': {'useCapsLockAsNVDAModifierKey': 'True'}, 'virtualBuffers': {'useScreenLayout': 'False', 'autoPassThroughOnCaretMove': 'True', 'passThroughAudioIndication': 'False'}, 'documentFormatting': {'includeLayoutTables': 'True'}, 'mouse': {'enableMouseTracking': 'False'}}
DEBUG - core.main (14:40:39.731):
setting language to Windows
INFO - core.main (14:40:39.747):
NVDA version alpha-18450,8c27752f
INFO - core.main (14:40:39.747):
Using Windows version 10.0.18362 workstation
INFO - core.main (14:40:39.747):
Using Python version 3.7.4 (tags/v3.7.4:e09359112e, Jul  8 2019, 19:29:22) [MSC v.1916 32 bit (Intel)]
INFO - core.main (14:40:39.747):
Using comtypes version 1.1.7
INFO - core.main (14:40:39.747):
Using configobj version 5.1.0 with validate version 1.0.1
DEBUG - core.main (14:40:39.764):
Initializing add-ons system
DEBUG - addonHandler._getAvailableAddonsFromPath (14:40:39.764):
Listing add-ons from C:\nvda alfa snapshots\userConfig\addons
WARNING - baseObject.Getter.__init__ (14:40:39.794):
Abstract class properties are not supported.
DEBUGWARNING - touchHandler.touchSupported (14:40:40.226):
Touch only supported on installed copies
DEBUG - core.main (14:40:40.375):
Initializing appModule Handler
DEBUG - core.main (14:40:40.375):
Initializing NVDAHelper
DEBUG - core.main (14:40:40.476):
Speech Dictionary processing
DEBUG - speechDictHandler.SpeechDict.load (14:40:40.476):
Loading speech dictionary '.\userConfig\speechDicts\default.dic'...
DEBUG - speechDictHandler.SpeechDict.load (14:40:40.476):
file '.\userConfig\speechDicts\default.dic' not found.
DEBUG - speechDictHandler.SpeechDict.load (14:40:40.476):
Loading speech dictionary 'builtin.dic'...
DEBUG - speechDictHandler.SpeechDict.load (14:40:40.476):
3 loaded records.
DEBUG - core.main (14:40:40.476):
Initializing speech
INFO - synthDrivers.espeak.SynthDriver.__init__ (14:40:40.599):
Using eSpeak NG version b'1.49.3 dev'
DEBUG - speechDictHandler.SpeechDict.load (14:40:40.764):
Loading speech dictionary '.\userConfig\speechDicts\voiceDicts.v1\espeak\espeak-English (Great Britain).dic'...
DEBUG - speechDictHandler.SpeechDict.load (14:40:40.764):
file '.\userConfig\speechDicts\voiceDicts.v1\espeak\espeak-English (Great Britain).dic' not found.
DEBUG - synthDriverHandler.SynthDriver.loadSettings (14:40:40.768):
Loaded settings for SynthDriver espeak
INFO - synthDriverHandler.setSynth (14:40:40.768):
Loaded synthDriver espeak
INFO - core.main (14:40:40.768):
Using wx version 4.0.3 msw (phoenix) wxWidgets 3.0.5 with six version 1.12.0
DEBUG - core.main (14:40:40.770):
Initializing braille input
INFO - brailleInput.initialize (14:40:40.770):
Braille input initialized
DEBUG - core.main (14:40:40.770):
Initializing braille
INFO - braille.initialize (14:40:40.774):
Using liblouis version 3.10.0
INFO - braille.initialize (14:40:40.780):
Using pySerial version 3.4
INFO - braille.BrailleHandler.setDisplayByName (14:40:40.794):
Loaded braille display driver noBraille, current display has 0 cells.
DEBUG - core.main (14:40:40.794):
Initializing vision
DEBUG - core.main (14:40:40.794):
Initializing displayModel
DEBUG - core.main (14:40:40.794):
Initializing GUI
DEBUG - windowUtils._rawWindowProc (14:40:40.844):
CustomWindow rawWindowProc called for unknown window 328094
DEBUG - windowUtils._rawWindowProc (14:40:40.844):
CustomWindow rawWindowProc called for unknown window 328094
DEBUG - windowUtils._rawWindowProc (14:40:40.844):
CustomWindow rawWindowProc called for unknown window 328094
DEBUG - windowUtils._rawWindowProc (14:40:40.844):
CustomWindow rawWindowProc called for unknown window 328094
DEBUG - core.main (14:40:40.864):
initializing Java Access Bridge support
DEBUG - core.main (14:40:41.230):
Initializing legacy winConsole support
DEBUG - core.main (14:40:41.230):
Initializing UIA support
INFO - _UIAHandler.UIAHandler.MTAThreadFunc (14:40:41.261):
UIAutomation: IUIAutomation6
DEBUG - core.main (14:40:41.446):
Initializing IAccessible support
DEBUG - core.main (14:40:41.461):
Initializing input core
DEBUGWARNING - inputCore.InputManager.loadLocaleGestureMap (14:40:41.461):
No locale gesture map for language en
DEBUGWARNING - inputCore.InputManager.loadUserGestureMap (14:40:41.461):
No user gesture map
DEBUG - core.main (14:40:41.461):
Initializing keyboard handler
DEBUG - core.main (14:40:41.461):
initializing mouse handler
DEBUG - core.main (14:40:41.546):
Initializing touchHandler
DEBUGWARNING - touchHandler.touchSupported (14:40:41.546):
Touch only supported on installed copies
DEBUG - core.main (14:40:41.546):
Initializing global plugin handler
DEBUG - core.main (14:40:41.546):
Initializing core pump
DEBUG - core.main (14:40:41.546):
Initializing watchdog
DEBUG - core.main (14:40:41.562):
initializing updateCheck
INFO - core.main (14:40:41.562):
NVDA initialized
DEBUG - core.main (14:40:41.562):
entering wx application main loop
IO - speech.speak (14:40:41.599):
Speaking [LangChangeCommand ('en_GB'), 'Taskbar']
DEBUGWARNING - characterProcessing._getSpeechSymbolsForLocale (14:40:41.599):
No CLDR data for locale en_GB
IO - inputCore.InputManager.executeGesture (14:40:45.593):
Input: kb(desktop):windows+d
IO - speech.speak (14:40:45.609):
Speaking [CharacterModeCommand(True), LangChangeCommand ('en_GB'), 'd', EndUtteranceCommand()]
IO - speech.speak (14:40:45.953):
Speaking [LangChangeCommand ('en_GB'), 'FolderView  list']
IO - speech.speak (14:40:45.973):
Speaking [LangChangeCommand ('en_GB'), 'Recycle Bin  not selected  1 of 65']
IO - inputCore.InputManager.executeGesture (14:40:48.478):
Input: kb(desktop):m
IO - speech.speak (14:40:48.554):
Speaking [CharacterModeCommand(True), LangChangeCommand ('en_GB'), 'm', EndUtteranceCommand()]
IO - speech.speak (14:40:48.594):
Speaking [LangChangeCommand ('en_GB'), 'Malwarebytes  3 of 65']
IO - inputCore.InputManager.executeGesture (14:40:49.804):
Input: kb(desktop):m
IO - speech.speak (14:40:49.851):
Speaking [CharacterModeCommand(True), LangChangeCommand ('en_GB'), 'm', EndUtteranceCommand()]
IO - speech.speak (14:40:49.878):
Speaking [LangChangeCommand ('en_GB'), 'Mozilla Thunderbird  14 of 65']
IO - inputCore.InputManager.executeGesture (14:40:51.414):
Input: kb(desktop):m
IO - speech.speak (14:40:51.494):
Speaking [CharacterModeCommand(True), LangChangeCommand ('en_GB'), 'm', EndUtteranceCommand()]
IO - speech.speak (14:40:51.534):
Speaking [LangChangeCommand ('en_GB'), 'Microsoft Edge Dev  46 of 65']
IO - inputCore.InputManager.executeGesture (14:40:53.654):
Input: kb(desktop):enter
IO - speech.speak (14:40:55.326):
Speaking [LangChangeCommand ('en_GB'), 'Untitled - Microsoft Edge Dev']
IO - speech.speak (14:40:57.024):
Speaking [LangChangeCommand ('en_GB'), 'Latest breaking news NZ | Stuff.co.nz | New Zealand - Microsoft Edge Dev']
DEBUGWARNING - NVDAObjects.IAccessible.IAccessible._get_IAccessibleRole (14:40:57.234):
accRole failed: (-2147024809, 'The parameter is incorrect.', (None, None, None, 0, None))
DEBUGWARNING - NVDAObjects.IAccessible.IAccessible._get_IAccessibleRole (14:41:01.589):
accRole failed: (-2147024809, 'The parameter is incorrect.', (None, None, None, 0, None))
DEBUGWARNING - NVDAObjects.IAccessible.IAccessible._get_IAccessibleRole (14:41:02.410):
accRole failed: (-2147024809, 'The parameter is incorrect.', (None, None, None, 0, None))
DEBUGWARNING - NVDAObjects.IAccessible.IAccessible._get_IAccessibleRole (14:41:03.417):
accRole failed: (-2147024809, 'The parameter is incorrect.', (None, None, None, 0, None))
DEBUGWARNING - NVDAObjects.IAccessible.IAccessible._get_IAccessibleRole (14:41:06.254):
accRole failed: (-2147024809, 'The parameter is incorrect.', (None, None, None, 0, None))
DEBUGWARNING - NVDAObjects.IAccessible.IAccessible._get_IAccessibleRole (14:41:06.370):
accRole failed: (-2147024809, 'The parameter is incorrect.', (None, None, None, 0, None))
DEBUGWARNING - NVDAObjects.IAccessible.IAccessible._get_IAccessibleRole (14:41:06.740):
accRole failed: (-2147024809, 'The parameter is incorrect.', (None, None, None, 0, None))
DEBUGWARNING - NVDAObjects.IAccessible.IAccessible._get_IAccessibleRole (14:41:06.770):
accRole failed: (-2147024809, 'The parameter is incorrect.', (None, None, None, 0, None))
DEBUGWARNING - NVDAObjects.IAccessible.IAccessible._get_IAccessibleRole (14:41:07.275):
accRole failed: (-2147024809, 'The parameter is incorrect.', (None, None, None, 0, None))
DEBUGWARNING - NVDAObjects.IAccessible.IAccessible._get_IAccessibleRole (14:41:13.132):
accRole failed: (-2147024809, 'The parameter is incorrect.', (None, None, None, 0, None))
DEBUGWARNING - NVDAObjects.IAccessible.IAccessible._get_IAccessibleRole (14:41:14.256):
accRole failed: (-2147024809, 'The parameter is incorrect.', (None, None, None, 0, None))
DEBUG - treeInterceptorHandler.update (14:41:19.715):
Adding new treeInterceptor to runningTable: <NVDAObjects.IAccessible.chromium.ChromeVBuf object at 0x068390D0>
DEBUGWARNING - virtualBuffers.VirtualBuffer.prepare (14:41:19.717):
appModule has no binding handle to injected code, can't prepare virtualBuffer yet.
DEBUGWARNING - virtualBuffers.VirtualBuffer.prepare (14:41:19.721):
appModule has no binding handle to injected code, can't prepare virtualBuffer yet.
IO - inputCore.InputManager.executeGesture (14:41:29.835):
Input: kb(desktop):tab
DEBUGWARNING - virtualBuffers.VirtualBuffer.prepare (14:41:33.928):
appModule has no binding handle to injected code, can't prepare virtualBuffer yet.
DEBUGWARNING - virtualBuffers.VirtualBuffer.prepare (14:41:33.931):
appModule has no binding handle to injected code, can't prepare virtualBuffer yet.
DEBUGWARNING - virtualBuffers.VirtualBuffer.prepare (14:41:33.941):
appModule has no binding handle to injected code, can't prepare virtualBuffer yet.
DEBUGWARNING - virtualBuffers.VirtualBuffer.prepare (14:41:33.951):
appModule has no binding handle to injected code, can't prepare virtualBuffer yet.
DEBUGWARNING - virtualBuffers.VirtualBuffer.prepare (14:41:33.961):
appModule has no binding handle to injected code, can't prepare virtualBuffer yet.
DEBUGWARNING - virtualBuffers.VirtualBuffer.prepare (14:41:33.971):
appModule has no binding handle to injected code, can't prepare virtualBuffer yet.
IO - speech.speak (14:41:33.982):
Speaking [LangChangeCommand ('en_GB'), 'list']
IO - inputCore.InputManager.executeGesture (14:41:35.787):
Input: kb(desktop):tab
DEBUGWARNING - virtualBuffers.VirtualBuffer.prepare (14:41:36.670):
appModule has no binding handle to injected code, can't prepare virtualBuffer yet.
DEBUGWARNING - virtualBuffers.VirtualBuffer.prepare (14:41:36.671):
appModule has no binding handle to injected code, can't prepare virtualBuffer yet.
IO - inputCore.InputManager.executeGesture (14:41:40.451):
Input: kb(desktop):tab
DEBUGWARNING - virtualBuffers.VirtualBuffer.prepare (14:41:40.571):
appModule has no binding handle to injected code, can't prepare virtualBuffer yet.
DEBUGWARNING - virtualBuffers.VirtualBuffer.prepare (14:41:40.576):
appModule has no binding handle to injected code, can't prepare virtualBuffer yet.
IO - inputCore.InputManager.executeGesture (14:41:44.282):
Input: kb(desktop):downArrow
IO - inputCore.InputManager.executeGesture (14:41:46.570):
Input: kb(desktop):l
IO - speech.speak (14:41:46.592):
Speaking [CharacterModeCommand(True), LangChangeCommand ('en_GB'), 'l', EndUtteranceCommand()]
IO - inputCore.InputManager.executeGesture (14:41:48.018):
Input: kb(desktop):tab
IO - speech.speakTypedCharacters (14:41:48.031):
typed word: l
DEBUGWARNING - virtualBuffers.VirtualBuffer.prepare (14:41:48.131):
appModule has no binding handle to injected code, can't prepare virtualBuffer yet.
DEBUGWARNING - virtualBuffers.VirtualBuffer.prepare (14:41:48.138):
appModule has no binding handle to injected code, can't prepare virtualBuffer yet.
IO - inputCore.InputManager.executeGesture (14:41:49.362):
Input: kb(desktop):alt+tab
IO - speech.speak (14:41:49.622):
Speaking [LangChangeCommand ('en_GB'), 'Latest breaking news NZ | Stuff.co.nz | New Zealand - Microsoft Edge  row 1  column 1']
IO - speech.speak (14:41:49.637):
Speaking [LangChangeCommand ('en_GB'), 'Latest breaking news NZ | Stuff.co.nz | New Zealand - Microsoft Edge  row 1  column 1']
IO - speech.speak (14:41:50.475):
Speaking [LangChangeCommand ('en_GB'), 'Latest breaking news NZ | Stuff.co.nz | New Zealand - Microsoft Edge Dev']
DEBUGWARNING - virtualBuffers.VirtualBuffer.prepare (14:41:50.712):
appModule has no binding handle to injected code, can't prepare virtualBuffer yet.
DEBUGWARNING - virtualBuffers.VirtualBuffer.prepare (14:41:50.718):
appModule has no binding handle to injected code, can't prepare virtualBuffer yet.
DEBUGWARNING - virtualBuffers.VirtualBuffer.prepare (14:41:50.723):
appModule has no binding handle to injected code, can't prepare virtualBuffer yet.
DEBUGWARNING - virtualBuffers.VirtualBuffer.prepare (14:41:50.729):
appModule has no binding handle to injected code, can't prepare virtualBuffer yet.
DEBUGWARNING - virtualBuffers.VirtualBuffer.prepare (14:41:50.735):
appModule has no binding handle to injected code, can't prepare virtualBuffer yet.
DEBUGWARNING - virtualBuffers.VirtualBuffer.prepare (14:41:50.740):
appModule has no binding handle to injected code, can't prepare virtualBuffer yet.
DEBUGWARNING - virtualBuffers.VirtualBuffer.prepare (14:41:50.746):
appModule has no binding handle to injected code, can't prepare virtualBuffer yet.
IO - speech.speak (14:41:50.749):
Speaking [LangChangeCommand ('en_GB'), 'Latest breaking news NZ | Stuff.co.nz | New Zealand  document']
IO - speech.speak (14:41:50.755):
Speaking [LangChangeCommand ('en_GB'), 'list']
IO - inputCore.InputManager.executeGesture (14:42:00.682):
Input: kb(desktop):downArrow
IO - inputCore.InputManager.executeGesture (14:42:01.938):
Input: kb(desktop):NVDA+space
IO - speech.speak (14:42:01.951):
Speaking [LangChangeCommand ('en_GB'), 'Focus mode']
IO - inputCore.InputManager.executeGesture (14:42:03.618):
Input: kb(desktop):NVDA+space
ERROR - scriptHandler.executeScript (14:42:03.641):
error executing script: <bound method GlobalCommands.script_toggleVirtualBufferPassThrough of <globalCommands.GlobalCommands object at 0x067E3170>> with gesture 'NVDA+space'
Traceback (most recent call last):
  File "scriptHandler.pyc", line 205, in executeScript
  File "globalCommands.pyc", line 1301, in script_toggleVirtualBufferPassThrough
  File "treeInterceptorHandler.pyc", line 139, in _set_passThrough
  File "review.pyc", line 124, in setCurrentMode
  File "review.pyc", line 48, in getDocumentPosition
  File "documentBase.pyc", line 24, in makeTextInfo
  File "virtualBuffers\__init__.pyc", line 210, in __init__
  File "textInfos\offsets.pyc", line 404, in __init__
  File "virtualBuffers\__init__.pyc", line 198, in _getOffsetsFromNVDAObject
  File "virtualBuffers\__init__.pyc", line 193, in _getOffsetsFromNVDAObjectInBuffer
  File "virtualBuffers\__init__.pyc", line 167, in _getOffsetsFromFieldIdentifier
OSError: [WinError 1775] A null context handle was passed from the client to the host during a remote procedure call
IO - inputCore.InputManager.executeGesture (14:42:04.786):
Input: kb(desktop):tab
DEBUGWARNING - virtualBuffers.VirtualBuffer.prepare (14:42:04.914):
appModule has no binding handle to injected code, can't prepare virtualBuffer yet.
DEBUGWARNING - virtualBuffers.VirtualBuffer.prepare (14:42:04.924):
appModule has no binding handle to injected code, can't prepare virtualBuffer yet.
IO - inputCore.InputManager.executeGesture (14:42:05.994):
Input: kb(desktop):NVDA+space
IO - inputCore.InputManager.executeGesture (14:42:14.802):
Input: kb(desktop):NVDA+f1
DEBUGWARNING - displayModel.DisplayModelTextInfo._get__storyFieldsAndRects (14:42:14.815):
AppModule does not have a binding handle
INFO - globalCommands.GlobalCommands.script_navigatorObject_devInfo (14:42:15.090):
Developer info for navigator object:
name: 'Business Directory'
role: ROLE_LINK
states: STATE_FOCUSABLE, STATE_LINKED, STATE_FOCUSED
isFocusable: True
hasFocus: True
Python object: <NVDAObjects.IAccessible.ia2Web.Ia2Web object at 0x06825490>
Python class mro: (<class 'NVDAObjects.IAccessible.ia2Web.Ia2Web'>, <class 'NVDAObjects.IAccessible.IAccessible'>, <class 'NVDAObjects.window.Window'>, <class 'NVDAObjects.NVDAObject'>, <class 'documentBase.TextContainerObject'>, <class 'baseObject.ScriptableObject'>, <class 'baseObject.AutoPropertyObject'>, <class 'object'>)
description: None
location: RectLTWH(left=503, top=348, width=119, height=16)
value: 'https://www.neighbourly.co.nz/local/'
appModule: <'appModuleHandler' (appName 'msedge', process ID 5268) at address 6521710>
appModule.productName: 'Microsoft Edge'
appModule.productVersion: '78.0.249.1'
TextInfo: <class 'NVDAObjects.IAccessible.IA2TextTextInfo'>
windowHandle: 918778
windowClassName: 'Chrome_RenderWidgetHostHWND'
windowControlID: 835116960
windowStyle: 1445986304
extendedWindowStyle: 32
windowThreadID: 2972
windowText: 'Chrome Legacy Window'
displayText: ''
IAccessibleObject: <POINTER(IAccessible2) ptr=0x5cae2ac at 674a670>
IAccessibleChildID: 0
IAccessible event parameters: windowHandle=918778, objectID=-4, childID=-73
IAccessible accName: 'Business Directory'
IAccessible accRole: ROLE_SYSTEM_LINK
IAccessible accState: STATE_SYSTEM_FOCUSED, STATE_SYSTEM_FOCUSABLE, STATE_SYSTEM_LINKED, STATE_SYSTEM_VALID (5242884)
IAccessible accDescription: None
IAccessible accValue: 'https://www.neighbourly.co.nz/local/'
IAccessible2 windowHandle: 918778
IAccessible2 uniqueID: -73
IAccessible2 role: ROLE_SYSTEM_LINK
IAccessible2 states: IA2_STATE_OPAQUE (1024)
IAccessible2 attributes: 'display:inline;tag:a;'



On 26/08/2019 1:16 PM, David Csercsics wrote:
The new Edge works fine here with the NVDA alpha, unless you downloaded a later version than the one I have. I'll have a look at that. But I used it this morning and it was behaving as expected.





--
Check out my website for NVDA tutorials and other blindness related materials at http://www.accessibilitycentral.net

To find out which library networks in New Zealand have a copy of the NVDA screen reader on them and there library locations please go to http://www.accessibilitycentral.net/nz%20libraries%20with%20nvda.html
To find a NVDA certified expert near you, please visit the following link https://certification.nvaccess.org/. The certification page contains the official list of NVDA certified individuals from around the world, who have sat and successfully passed the NVDA expert exam.


Mr. Ed <pinky14@...>
 

Hi,

I am an old Jaws user and I am not understanding what brows mode is on nvda. Can someone explain it to me. Thanks in advance.

Mr. Ed


 

NVDA Focus mode is the equivalent of JAWS Forms mode

NVDA Browse mode is the equivalent of what I thought JAWS itself called Browse mode.

If you're not in a control where data entry is possible like a text edit box, radio button, etc. and are able to quick navigate from control to control using the single letter shortcuts or are able to use a screen reader search to find things you are in NVDA Browse mode.

Someone put me out of my misery and tell me what JAWS calls its equivalent if it's not also browse mode (as I suspect it isn't and I can't pull up that mode from memory for love nor money right now). 


--

Brian - Windows 10 Pro, 64-Bit, Version 1903, Build 18362  

The color of truth is grey.

           ~ André Gide

 

 


Nimer Jaber
 

They call it virtual PC cursor.

Thanks.

On Mon, Aug 26, 2019 at 1:08 PM Brian Vogel <britechguy@...> wrote:
NVDA Focus mode is the equivalent of JAWS Forms mode

NVDA Browse mode is the equivalent of what I thought JAWS itself called Browse mode.

If you're not in a control where data entry is possible like a text edit box, radio button, etc. and are able to quick navigate from control to control using the single letter shortcuts or are able to use a screen reader search to find things you are in NVDA Browse mode.

Someone put me out of my misery and tell me what JAWS calls its equivalent if it's not also browse mode (as I suspect it isn't and I can't pull up that mode from memory for love nor money right now). 


--

Brian - Windows 10 Pro, 64-Bit, Version 1903, Build 18362  

The color of truth is grey.

           ~ André Gide

 

 



--
Best,

Nimer Jaber

The message above is intended for the recipient to whom it was
addressed. If you believe that you are not the intended recipient,
please notify me via reply email and destroy all copies of this
correspondence. Action taken as a result of this email or its contents
by anyone other than the intended recipient(s) may result in civil or
criminal charges. I have checked this email and all corresponding
attachments for security threats. However, security of your machine is
up to you. Thanks.

Registered Linux User 529141.
http://counter.li.org/

To find out about a free and versatile screen reader for windows XP
and above, please click here:
http://www.nvda-project.org

You can follow @nimerjaber on Twitter for the latest technology news.

To contact me, you can reply to this email or you may call me at (970) (393-4481) and I will do my best to respond to you promptly. Thank
you, and have a great day!


 

On Mon, Aug 26, 2019 at 04:11 PM, Nimer Jaber wrote:
They call it virtual PC cursor.
Really?   My distinct memory is that JAWS described two distinct modes just like NVDA does.   In fact I recall when "automatic switching to forms mode" was introduced when you landed in/on a control.   I would have sworn that there was a one-word name for the mode that is not JAWS Forms mode.

I am aware of the virtual cursor, but that's a separate issue.
 
--

Brian - Windows 10 Pro, 64-Bit, Version 1903, Build 18362  

The color of truth is grey.

           ~ André Gide

 

 


Nimer Jaber
 

So far as I know, they call it forms mode and virtual PC cursor/virtual navigation mode. I don't think I've heard of JAWS calling theirs "browse mode". 


On Mon, Aug 26, 2019 at 1:19 PM Brian Vogel <britechguy@...> wrote:
On Mon, Aug 26, 2019 at 04:11 PM, Nimer Jaber wrote:
They call it virtual PC cursor.
Really?   My distinct memory is that JAWS described two distinct modes just like NVDA does.   In fact I recall when "automatic switching to forms mode" was introduced when you landed in/on a control.   I would have sworn that there was a one-word name for the mode that is not JAWS Forms mode.

I am aware of the virtual cursor, but that's a separate issue.
 
--

Brian - Windows 10 Pro, 64-Bit, Version 1903, Build 18362  

The color of truth is grey.

           ~ André Gide

 

 



--
Best,

Nimer Jaber

The message above is intended for the recipient to whom it was
addressed. If you believe that you are not the intended recipient,
please notify me via reply email and destroy all copies of this
correspondence. Action taken as a result of this email or its contents
by anyone other than the intended recipient(s) may result in civil or
criminal charges. I have checked this email and all corresponding
attachments for security threats. However, security of your machine is
up to you. Thanks.

Registered Linux User 529141.
http://counter.li.org/

To find out about a free and versatile screen reader for windows XP
and above, please click here:
http://www.nvda-project.org

You can follow @nimerjaber on Twitter for the latest technology news.

To contact me, you can reply to this email or you may call me at (970) (393-4481) and I will do my best to respond to you promptly. Thank
you, and have a great day!


 

And FYI, depending on the vintage of the reference, I'm finding results in web searches that refer to the mode of JAWS that's not Forms mode as Browse mode and Virtual mode.

I don't know when the change may have happened, but by the time I got involved with JAWS it was Browse/Forms [with the NVDA equivalents, respectively, Browse/Focus].
--

Brian - Windows 10 Pro, 64-Bit, Version 1903, Build 18362  

The color of truth is grey.

           ~ André Gide

 

 


g melconian
 

It depends on  the version of jaws.  some earlier versions  of jjaws wer referring to it as browse mode and the newer versions I think have dropped that  reference.i will have to  fire off my old pc an take  a look.   As I am primarily on mobile platforms lately and on chrome OS and so that  is why I seldom have that much need for jaws and the windows pc. 

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Brian Vogel
Sent: Monday, August 26, 2019 1:31 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] The new microsoft edge chromium based browser troubles with nvda not going to browse mode

 

And FYI, depending on the vintage of the reference, I'm finding results in web searches that refer to the mode of JAWS that's not Forms mode as Browse mode and Virtual mode.

I don't know when the change may have happened, but by the time I got involved with JAWS it was Browse/Forms [with the NVDA equivalents, respectively, Browse/Focus].
--

Brian - Windows 10 Pro, 64-Bit, Version 1903, Build 18362  

The color of truth is grey.

           ~ André Gide

 

 


Mr. Ed <pinky14@...>
 

Hi Brian,

Thanks for your answer. I am trying to figure out all the modes between Jaws and nvda. So does nvda have a touch cursor like Jaws? Does nvda have a cursor like the Jaws cursor. If so what are the key strokes for nvda?

I looked in the shortcut list but I did not see them or know what they were.

Mr. Ed

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Brian Vogel
Sent: Monday, August 26, 2019 3:09 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] The new microsoft edge chromium based browser troubles with nvda not going to browse mode

 

NVDA Focus mode is the equivalent of JAWS Forms mode

NVDA Browse mode is the equivalent of what I thought JAWS itself called Browse mode.

If you're not in a control where data entry is possible like a text edit box, radio button, etc. and are able to quick navigate from control to control using the single letter shortcuts or are able to use a screen reader search to find things you are in NVDA Browse mode.

Someone put me out of my misery and tell me what JAWS calls its equivalent if it's not also browse mode (as I suspect it isn't and I can't pull up that mode from memory for love nor money right now). 


--

Brian - Windows 10 Pro, 64-Bit, Version 1903, Build 18362  

The color of truth is grey.

           ~ André Gide

 

 


Luke Davis
 

Mr. Ed

I hate to lay an RTFM on you, but very literally, have you read the manual?
Insert+n, h, and arrow until you hear "User manual", think it may be the first option.
Many things you don't currently understand will be explained well there, and we can help you better once you have that base of knowledge.
Not that you have to understand everything in the manual, of course, but knowing a general outline of what it contains will serve you well I think.

Luke

On Mon, 26 Aug 2019, Mr. Ed wrote:

Thanks for your answer. I am trying to figure out all the modes between Jaws and nvda. So does nvda have a touch cursor like Jaws? Does nvda have a cursor
like the Jaws cursor. If so what are the key strokes for nvda?
I looked in the shortcut list but I did not see them or know what they were.


 

Mr. Ed,

         Screen readers, broadly speaking, all work similarly whether they use the same terminology or not.  I started off knowing JAWS and find NVDA an "easy transfer" or an easy secondary to learn and use.

         NVDA has the equivalent of the JAWS touch cursor, which I believe is object navigation if I'm not mistaken.  Someone will correct me if I'm not.

         I don't know what, precisely, you're asking with regard to NVDA having a cursor like the JAWS cursor (by which I believe you mean the virtual cursor, and all screen readers have an equivalent as it's the primary thing that most users are generally interacting with, particularly when web browsing).

         As I said to someone else earlier, and it's as true of JAWS as NVDA, I don't know of a single screen reader that does not have a "show the keyboard shortcuts" command built in to it, as all of us need to reference some of the ones we don't use frequently or when we're just learning.  In the case of NVDA, hitting the keyboard shortcut NVDA Key+N,H,Q  [NVDA main menu, help option,keystrokes quick reference suboption] will bring up the NVDA keyboard shortcuts document in your web browser for your searching pleasure.   There is so much crossover in terminology in JAWS and NVDA that doing a search on a term you know for one in the other often gets you straight to what you want to find.  If not, try a little guessing in your searches.  If that fails, ask here with one of the classic, "In JAWS, this is called/you do this this way, what is it called/how do you do same in NVDA?," type questions.  There will be plenty able to answer.

--

Brian - Windows 10 Pro, 64-Bit, Version 1903, Build 18362  

The color of truth is grey.

           ~ André Gide

 

 


 

On Mon, Aug 26, 2019 at 05:57 PM, Luke Davis wrote:
I hate to lay an RTFM on you, but very literally, have you read the manual?
Insert+n, h, and arrow until you hear "User manual", think it may be the first option.
Many things you don't currently understand will be explained well there, and we can help you better once you have that base of knowledge.
Well, Luke, I'm here to support you in this.

You have to have at least skimmed the fine manual, if not pored over it cover to cover, to obtain a base of knowledge first.  In the case of someone who's doing a screen reader to other screen reader transition, they're in a very good place to see direct parallels between screen readers A and B when reading the fine manual for B.

All screen readers have a built-in keyboard shortcut, generally under their main menu, help submenu, for things like the User Manual, Keyboard Shortcuts list, and the like.  One of the first things I teach is that these are present and how to access them.  You can often find an answer yourself, in seconds, by bringing up the appropriate reference document and doing a quick search.

It is not unreasonable to ask even newbies to something to do this first, after you are sure they know how to do it.   Asking a question on a list such as this imposes on the time of an awful lot of people, and even though we're all more than willing to help, it's generally considered good netiquette to have at least tried doing some legwork before turning to a list/group/forum.
 
--

Brian - Windows 10 Pro, 64-Bit, Version 1903, Build 18362  

The color of truth is grey.

           ~ André Gide

 

 


hurrikennyandopo ...
 

Hi

I guess I will have to put in a ticket for it then along with the log.

The following page might help him at https://github.com/nvaccess/nvda-community/wiki/FAQ

Gene nz

On 21/08/2019 2:04 PM, help.TVNZ wrote:
##- Please type your reply above this line -##
logo

Hello Hurrikennyandopo,
We'd love to hear what you thought of the support you received from us. Please take a moment to answer one simple question by clicking either link below:
How would you rate the support you received?
Good, I'm satisfied
Bad, I'm unsatisfied
Here's a reminder of what your ticket was about:
 
Tony Gordon (help.TVNZ)
Aug 20, 13:22 NZST
Hi Gene

As I said before I can't say how long that change, if at all, will take to make its way through the system.

Cheers
tony
 
Hurrikennyandopo
Aug 20, 08:39 NZST
Hi Tony

Thank you very much for taking this up and pointing it in the right directions to be fixed.

You do not know how much it means to a visually impaired, blind or dyslexic person who uses a screen reader to hear the correct information when navigating a web site like in this case.
To hear the correct information been read out.
This also includes the app versions of the TVNZ on demand app.

I will be looking forwards to hearing the name of the show/movie etc from the list knowing what I am going to watch before I go in to watch it as shown in the examples when it is fixed like you hear on 3 on demand..


Would you be able to let me know if possible when it has been done or should I just go in periodically to check on the 2 platforms i have hear? I would have to get a Apple user to check on their device the same.
It might even say what has been done in a app update?
But not for the web version I can just log in and test.


Gene nz



On 19/08/2019 11:26 AM, Tony Gordon (help.TVNZ) wrote:
Attachment(s)
NVDA Certified Expert.png
 
Hurrikennyandopo
Aug 19, 11:44 NZST
hi Tony

thanks for getting back to me it felt like no one was listening.
there was no contact other except for the 13th not even from the developers.

so I ended up putting 2 audio recordings up on my website so they could hear what was said plus for other people to complain.

There is also a third audio recording from 3 now on demand showing what should be said as you go down the list of shows it tells you what it is first before you go into watch the show.


That is clearly not happening with the web version or the android app and also I have been told it is on the apple app as well with voice over.

To see what I mean you can go to my website at http://www.accessibilitycentral.net



Just look for the heading about the importance of labeling one showing it not and one showing it has been.

Gene nz

On 19/08/2019 11:26 AM, Tony Gordon (help.TVNZ) wrote:
Attachment(s)
NVDA Certified Expert.png
 
Tony Gordon (help.TVNZ)
Aug 19, 11:26 NZST
Hi Gene

Thanks for all the additional information. I will forward this to the Product Owner for the web and apps and they will prioritise this work over other new features or initiatives.

I cannot give a time frame for any possible resolution.

Cheers
Tony
 
Hurrikennyandopo
Aug 15, 10:30 NZST
Hi Christine

The following is a example when I logged into the tvnz on demand app on my android phone using the talk back screen reader.

It is the same sort of problem there to.
But you will notice both on the web version and the app version if you say tap on something under a heading the next page that comes up will tell you what the show is time etc and can be used but when you go back to the list no but did notice it spoke one so there must be a over lay stopping it?

The link to the drop box account where it can be heard is https://www.dropbox.com/s/6ct57j8h6a2vsuy/using%20tvnz%20on%20demand%20with%20android%20phone%20.MP3?dl=0

The web version which I sent before I will put in here also the link to it is https://www.dropbox.com/s/prpyiz7oc0bwquz/what%20i%20hear%20on%20the%20tvnz%20on%20demand%20page%20with%20nvda.mp3?dl=0


A friend also is going to sus it out with a apple version of the app.

Looking forwards to a good out come.

Gene nz

On 13/08/2019 2:20 PM, Christine Gilchrist (help.TVNZ) wrote:
Attachment(s)
NVDA Certified Expert.png
 
Hurrikennyandopo
Aug 14, 09:55 NZST
Hi Christine

It also affects a voice over user using the tv on demand app on there apple device.

I just heard back from a person on the atig list and she said it was usable when she first got her apple tv then about a year ago it changed and does the same as it does for the web version and the android version the same sort of problems.
That have been pointed out of the shows etc not been spoken out before you go into the show.

She basically said it would read the headings but nothing in the list under neath each section plus it included the A to Z section places where it refer to the show.

If you say picked a show not knowing what it was say criminal minds under the C section in the list it would not be spoken out but would when you went in to watch the show.

I am guessing it was read out correctly on the page where it mentions about the show, time etc but not the page with the list of shows before.

Gene nz







On 13/08/2019 2:20 PM, Christine Gilchrist (help.TVNZ) wrote:
Attachment(s)
NVDA Certified Expert.png
 
Hurrikennyandopo
Aug 14, 09:25 NZST
Hi Christine
In the first email that was sent I also mentioned about screen readers on a mobile phone.

In the case of a apple device you had to turn on voice over under app...settings...accessibility then turn on voice over and in the case of a android phone apps...settings...accessibility..then turn on talk back. In both cases they will change some of the gestures when testing.

I downloaded the tvnz on demand app for my android phone then signed into it.

When I got to the main page where the shows are it would read out the heading for each section then say list of say 43 It would repeat the next section and tell you what it was and then say list of say 30.

What the shows were underneath when you swiped was not spoken out and I got my sighted wife to have a look to see what was happening Ithink she said they were graphics saying the name of the show but the alt text was not said by the screen reader .
So I am guessing it was left out or there is some type of over lay the developers should know.
She said the focus was moving and she could see it move to the next item.


Also when you went into the section where it lists the shows from A to Z it would say the letter then list but none of the shows under A right through to Z

Yet if I say went to the letter B section then picked some thing under that section I could not hear then a show starting with the letter B would come up and say what it was the time it went for etc that side seems accessible as I got a couple of shows to watch to test out.

But I do not want to go into every show to see what it is as they will see when they test.

I am waiting for a apple user to get back to me but the person when I said about it on the web said it was not useable on the apple tv but must of been at one time.
I just want her to confirm her problems and if they are the same.

It seems what ever has affected the website does the same for the android app minus new season or what ever it was saying on the web version.

So it seems to be those sections that refer to the show where they are listed yet other sections as they will see are accessible.

Please can you make sure the developers get what is send in this email to add it to the desk top version.

Hoping to hear a good out come or from the developer to get it sorted out and hopefully a time line of when it will be sorted.

if i do not really hear any thing about it been looked at then I would believe they are not testing or looking at the problems.


Gene nz



On 13/08/2019 2:20 PM, Christine Gilchrist (help.TVNZ) wrote:
Attachment(s)
NVDA Certified Expert.png
 
Hurrikennyandopo
Aug 13, 14:41 NZST
Hi Christine

Hopefully when I replied it did not come across at having a go at you. I apologize if it sounded that way but guess it was the response.

The audio from what was recorded on the on demand web page will give them a better idea of what I hear if i want to watch a show.

It was going down the shows section both from off the main page like whats new and under the A to Z section. It used to say the name of the shows before you went into it to watch. Not sure what they have done.

Hopefully either hearing what I hear or even testing with the nvda screen reader they will know what I mean.

There is a reason for web standards. Hopefully they can get it sorted I would hate to go up the ladder more.

But I also want to make sure it is happening elsewhere on devices where people use a screen reader to get to content or watch it.

I can also give them the home phone number to contact me directly if needed.


Gene nz



On 13/08/2019 2:20 PM, Christine Gilchrist (help.TVNZ) wrote:
Attachment(s)
NVDA Certified Expert.png
Christine Gilchrist (help.TVNZ)
Aug 13, 14:20 NZST
Really sorry, I did read your email but typed the incorrect wording.   As mentioned I have passed on your message, sorry for my error.
 
Hurrikennyandopo
Aug 13, 14:00 NZST
Hi Christine

I do not have a hearing problem and do not use sub titles.

I am visually impaired and use a screen reader to navigate websites etc.

It does not mean because I am blind I can not watch video etc on line or tv shows etc. from online as long as material is labled correctly.


I have no problems using say net flix online, channel 3 on demand or choice on demand as content is labled correctly but not on the tvnz on  demand page.

I am going to get other people to check as well with a screenreader either on there phone or using a desk top computer.
I am going to attach or maybe add a link to a drop box file so you can hear what I hear when navigating the tvnz on demand section where the shows etc are.

it used to say the name of the show like flash or what ever then would say if it was a new season etc
Then you could go in and watch it. I really do not want to go into every new season to see what the show is first.

The drop box link is https://www.dropbox.com/s/prpyiz7oc0bwquz/what%20i%20hear%20on%20the%20tvnz%20on%20demand%20page%20with%20nvda.mp3?dl=0

It sounds like you do not know what I am talking about from your response. That is why I tried to send a message to the people who could look at it.
May be you hearing the audio of it as I go through some of the content you will know what I mean.

I have also attached it as a attattachment in this email.

Gene nz



On 13/08/2019 11:38 AM, Christine Gilchrist (help.TVNZ) wrote:
Attachment(s)
NVDA Certified Expert.png
what i hear on the tvnz on demand page with nvda.mp3
Christine Gilchrist (help.TVNZ)
Aug 13, 11:38 NZST

Hi Gene,

Thanks for writing to us and sharing your thoughts about the service for the hearing impaired with us.

We appreciate you taking the time to let us know about this - and I am sure it will be of great interest to the producers of our website.

The production team now has your email – if they want to pick up anything further, I’m sure they’ll be in touch.

Thanks again for contacting us - we really appreciate it.

Kind regards

Christine Gilchrist
TVNZ



 
Hurrikennyandopo
Aug 12, 19:32 NZST
RE: Items on your website not labelled correctly (eg need to hear the name of the new episode, or name of the new season rather than just hearing the words new episode or new season etcetera)
My name is Gene Gibson and I am visually impaired and use a screen reader called NVDA which can be found at the following website at http://www.nvaccess.org
It is a piece of adaptive technology that a visually impaired, blind, or dyslexic person might use on a computer or their smart phones.
If a screen reader is used on a smart phone, it might be either the Talkback screen reader (on an Android phone) or on an Apple phone it would be Voiceover. These are usually found under the settings/accessibility section and need to be turned on. There are also other screen readers that you can use on a computer or laptop or tablet. These are on the Windows operating system, the Apple operating system and the Android operating system.
For a desktop user, you would use the keyboard to interact with the web pages. You would use quick navigation keys in browse mode, along with some other keys on the keyboard. If you are using a mobile device with a screen reader, you would use gestures.
Your TV on demand section used to be easy to use and navigate with my screen reader - even to play shows etcetera. Pretty much everything was reported correctly as you moved through the pages. It was pretty much like using a web page.
I had a report from another screen reader user saying she was having problems with the TV on demand part of the website, so I decided to have a look to see what the problem was. She wanted to catch up on Shortland Street. I tested it with different browsers, all with the same results, and am also testing it with some other screen readers and going to get other people to look into it as well.
The following web page (even though it was written a while back) will give you an idea on how to test the TV on demand page with the NVDA screen reader - so that you can hear what I hear also. The link to this page is https://marcozehe.wordpress.com/articles/how-to-use-nvda-and-firefox-to-test-your-web-pages-for-accessibility/
Stuff to be fixed
As you navigated through the TV on demand page it would say the following. Some of the material was read out correctly but would not say what the new season was of? It would what the new season was about, but only after you went into it, but not before.
TVNZ OnDemand
We’ve rounded up the best of the best for you. Finding your favourite TVNZ shows and discovering new ones has never been easier. Watch your favourites whenever, wherever.
SHARE PAGE
Home/TVNZ OnDemand
My Favourites
NEWEPISODE
FULL SEASON…FULL SEASON…FULL SEASON…FULL SEASON
MOVIE…Next slide…
What's New…NEW SEASON…NEW SEASON…NEW SEASON…NEW SEASON…NEW SEASON…NEW SEASON
MOVIE…NEW SEASON…FULL SEASON…FULL SEASON…FULL SEASON…Next slide…Full Seasons
FULL SEASON
I am a proficient user of a screen reader so have no problems navigating a website unless I have stuff that has not been labled correctly on a website like graphics, buttons etcetera – as I am hearing on this site. The buttons seem to be ok, but the graphics are not labelled properly.
I was getting this read out as I went down the page. It seems as though they are not labled correctly so the screen reader does not know what it refers to for that episode or season.
You could at one time (which I went looking for) jump down through shows from A to Z and it would say what they are. When I do come across this section now, it says the letter but no shows under that letter. It used to say what shows were under all the letters but does not now.
What has been changed? Is the web developer not using alt text etcetera on the graphics that the screen reader needs to go by?
I do not really want to go through the whole demand section saying what has to be fixed.
I cannot give you feedback myself about the accessibility of the phone app as I have not tested it with my mobile phone with Talkback (to see if I get the same results as on the website). I am not using the app but believe that others are.
Even when I went to put in a complaint there was a captcha that I could not even pass. I tried quite a few times. This was with the audio captcha before I could submit it as a complaint.
I have to get my wife to do this for me as I cannot pass it. Is there a reason why it is there?
I am happy to send an audio file so you know what I am hearing now.
The TV3 on demand website works well with my screen reader, as does the choice on demand site! It is only this one that I am having problems with.
Looking forward to working with you to resolve this back to what it used to be when it was working correctly.
Gene Gibson
Best regards,
The TVNZ Team
 

 
--
Image NVDA
        certified expert
Check out my website for NVDA tutorials and other blindness related materials at http://www.accessibilitycentral.net

To find out which library networks in New Zealand have a copy of the NVDA screen reader on them and there library locations please go to http://www.accessibilitycentral.net/nz%20libraries%20with%20nvda.html
To find a NVDA certified expert near you, please visit the following link https://certification.nvaccess.org/. The certification page contains the official list of NVDA certified individuals from around the world, who have sat and successfully passed the NVDA expert exam.



On 27/08/2019 10:10 AM, Brian Vogel wrote:
On Mon, Aug 26, 2019 at 05:57 PM, Luke Davis wrote:
I hate to lay an RTFM on you, but very literally, have you read the manual?
Insert+n, h, and arrow until you hear "User manual", think it may be the first option.
Many things you don't currently understand will be explained well there, and we can help you better once you have that base of knowledge.
Well, Luke, I'm here to support you in this.

You have to have at least skimmed the fine manual, if not pored over it cover to cover, to obtain a base of knowledge first.  In the case of someone who's doing a screen reader to other screen reader transition, they're in a very good place to see direct parallels between screen readers A and B when reading the fine manual for B.

All screen readers have a built-in keyboard shortcut, generally under their main menu, help submenu, for things like the User Manual, Keyboard Shortcuts list, and the like.  One of the first things I teach is that these are present and how to access them.  You can often find an answer yourself, in seconds, by bringing up the appropriate reference document and doing a quick search.

It is not unreasonable to ask even newbies to something to do this first, after you are sure they know how to do it.   Asking a question on a list such as this imposes on the time of an awful lot of people, and even though we're all more than willing to help, it's generally considered good netiquette to have at least tried doing some legwork before turning to a list/group/forum.
 
--

Brian - Windows 10 Pro, 64-Bit, Version 1903, Build 18362  

The color of truth is grey.

           ~ André Gide

 

 

--
Check out my website for NVDA tutorials and other blindness related materials at http://www.accessibilitycentral.net

To find out which library networks in New Zealand have a copy of the NVDA screen reader on them and there library locations please go to http://www.accessibilitycentral.net/nz%20libraries%20with%20nvda.html
To find a NVDA certified expert near you, please visit the following link https://certification.nvaccess.org/. The certification page contains the official list of NVDA certified individuals from around the world, who have sat and successfully passed the NVDA expert exam.


Gene
 

Something like the instructional material for sale by NVDA may well be better.  A lot of people prefer tutorials to manuals. 
 
As far as the question about the touch cursor in JAWS is concerned, the most similar thing in NVDA is object navigation.  I believe that a tutorial is much better for learning it than using the manual, though if you do well working with manuals  you are welcome to try.  I cant' compare them because I haven't used the Touch Cursor but object navigation is said to be similar to its function.
 
As for browse mode, whatever JAWS calls it now, it was called the Virtual PC cursor since it first came out until I stopped using JAWS in the early to mid 2000's.  I am not aware of a name change since then.  I have never seen it referred to as something else.  If there has been a name change, I hope we can get definite information.
 
Browse mode in NVDA is just about identical.  All or almost all the quick navigation commands you use are the same.  If you want to go into forms mode without using enter, instead of JAWS key z, you use NVDA key space bar.  It’s a toggle, just as in JAWS. 
 
In NVDA, using the desktop layout, both inserts are NVDA keys when using default settings, just as they are JAWS keys in JAWS default settings.
 
One important difference, actually two, are that find in NVDA browse mode is control NVDA key f.  Repeat find is NVDA key f3.
 
Below my signature are two messages I wrote perhaps a month or two ago giving information new users may well find useful.  You will see a reference or to to a comment I was responding to, but it will not in any way impair understanding. 
 
Gene
 
Message 1
 
You talked about making a slow transition to NVDA.  it won't necessarily be that slow.  A lot of what people do with a screen-reader isn't specifically using screen-reader commands.  A lot of it is using Windows and program commands.  there are certain commands you need to know with any screen--reader at the outset, in terms of efficient use and easier use with programs and Windows.
Here are commands and some information you will want to know right away.
 
Run NVDA, control alt n.
Unload NVDA, NVDA key q.  Press it, wait a moment, then press enter.
Working with the voice:
Open the voice dialog with control NVDA key v.
You are in a field where you select the voices available for the synthesizer you are using.  Itsa combo box.
Tab through the fields to see the adjustments you can make.  The second field is for speed, there is a punctuation field, and other fields.  There is an ok button once you have made the settings changes you want.  Using the default NVDA settings, the settings are saved as permanent in the program when you exit NVDA or whenever it shuts down properly such as when you shut down Windows.  You can change the settings whenever you want but they won't stay changed until you change them by exiting the program or manually save them, control NVDA key c.  My point is that if you change them and the program crashes before you manually save them or before the program shuts down correctly in the same session as you changed them, the next time the program opens, the old settings will be used.
 
Let's say you have made a number of changes or even one, to NVDA as an experiment.  If you haven't closed the program or manually saved the settings, you can set everything back as it was before you made the changes with control NVDA key r.  This is very useful to immediately change settings back to what they were if you intend one or more changes to just be during the current session.  Don't forget to change them back before closing the program or the new settings will be saved as the settings the program will use until you change them again. 
 
Read to end is NVDA key down arrow, that is down arrow on the main keyboard.
I use the caps lock as the NVDA key with this command.  I find it far more convenient than using either insert with down arrow.  You can set NvDA to use caps lock as an NVDA key.  Both inserts can still be used. 
Open keyboard settings with control NVDA key k. 
Tab to a check box that allows the caps lock to work as an NVDA key.  Check it with the space bar.  Tab to and activate the ok button.
Now you can use capslock down arrow as well as either insert down arrow for read to end.  Of course,, you may use caps lock as the NVDA key whenever you wish. 
To use the caps lock key as the caps lock key, press it twice quickly--twice quickly for on, twice quickly for off.
Read current line is NVDA key up arrow on the main keyboard.
However, I use the numpad for that command.  It requires only one hand and only one key to be pressed and it is clustered with the other review commands.
Note the pattern:
Read current line:
Numpad 8.
Read next line numpad 9.
Read previous line, numpad 7.
Current word, numpad 5.
Next word, numpad 6.
Previous word, numpad 4.
Current character, numpad 2.
Next character, numpad 3.
Previous character numpad 1.
All these reading commands are when using the default desktop layout.  If you want to use the laptop layout, I don't know those commands.  There is a different command for read to end in the laptop layout as well.
Speak title bar, NVDA key t.
Speak time, NVDA key 12.
If you use the system tray, that will take a little explanation.  NVDA doesn't explain how to use the system tray using it so ask here.
Just about all commands you used to use in the virtual PC cursor are identical to JAWS.
You may want speech instead of sounds and you may want to make a few other changes to how the equivalent of the Virtual PC Cursor works.  Its called browse mode.
If you want more information, ask here.  of course, you can get this information in the user guide and elsewhere, but it will be faster and more convenient to get a few commands here and a little explanation.
 
Aside from what I've said, if you are a more advanced screen-reader user, you will want to know how to use what NVDA calls object navigation.  You will also want to know how to use what NVDA calls screen review, the rough equivalent of the JAWS cursor even if you aren't more advanced. 
I won't go into all that here, but I'm presenting many things you may want to learn at the outset rather than later, though object navigation is something you may want to learn after screen-review.  It is something you haven't worked with before but if its taught properly, you will catch on to it after some looking around and playing around.  If you use materials to learn it and you have problems, ask here and I'll give some examples that may help you learn to use it better.  Explanation, to an extent, when using object navigation is helpful but my experience is that you really learn it by playing around and following a few concrete examples along with and after a little explanation.
 
Here is something very important.  When you use screen review, always go back to object navigation afterwords.  Don't put it off or forget.  If you stay in screen-review, many from the keyboard commands will work properly but some won't and you will have no idea why.  That's why, you are still in screen review.
 
Others may have a good deal of other information you will be interested in such as about instructional material or commands I haven't discussed but my object is to get you using NVDA in a reasonable number of situations as easily and quickly as possible.
 
Gene
 
Message 2
I haven't used Waterfox but it should be either fully accessible or just about fully.  The same with Firefox, and Chrome, both of which I use.  They are completely or just about completely accessible.
 
I haven't used Word much nor open source word processors so I'll let others discuss that. 
 
Whether you use JAWS or not, it’s a good idea to have a demo on your system in case it works better for something enough that you want to use it for a short time during the forty minute running time. 
 
There is an NVDA add-on that allows you to use a system tray dialog similar to that in JAWS, but for now, I'll discuss using the system tray itself.
To get to the system tray, use the command Windows key b.
You can use first letter navigation in the system tray.  You can move using the left and right arrows from item to item as well.
The new version of DropBox doesn't work fully with the system tray add-on in NVDA.  If you want to use the familiar menu you have probably used, move to the Dropbox icon and press enter.  The familiar menu will open. 
 
Here are the commands to use in the System tray.
Double left click is enter.
Single left click is space bar.
Right click is the context menu key.  I would think shift f10 would work as well if you don't have a context menu key, but I haven't checked.
 
Gene