Quick Start: NVDA

Common Keys

  • Start NVDA: Ctrl+Alt+n or Start Menu/NVDAc
  • NVDA key: Insert or Caps Lock
  • NVDA Menu: NVDA + n
  • Quit NVDA: NVDA + q
  • Stop speech: Control
  • Pause Speech: Shift
  • Read current line: NVDA + Up Arrow
  • Read next line: NVDA + Down Arrow
  • Toggle browse/focus modes: NVDA + space
  • Single Letter Navigation:
    • h: heading
    • 1 to 6: headings at levels 1 to 6 respectively
  • Browse mode elements list (show available action list): NVDA + F7
https://www.nvaccess.org/files/nvda/documentation/userGuide.html?#LaunchingNVDA

Known Issues


"Clickable Clickable Clickable …"
Please note that NVDA has a well known issue or bug:
Sometimes you might hear a lot of repeated speech “Clickable Clickable Clickable …”, very annoying:
This is by design of NVDA. So good solution so far.
You can turned of by pressing NVDA+n/Preferences/Settings/Document Formattting/Uncheck “Clickable”.
For details, please refer to:
User Group discussion: https://nvda.groups.io/g/nvda/topic/stopping_the_word_clickable/5866351
Tech discussions with NVDA authors: https://github.com/nvaccess/nvda/issues/7430

Unexpected keyboard focus of inactive tab in a tablist

https://github.com/nvaccess/nvda/issues/8906
Press Insert+Space to switch to browse mode, and then press d or shift+d to move to a land mark (this will leave the tab list), and then press tab to return to the tab list. NVDA can’t remember the previous focused tab (e.g. tab 3). Instead NVDA always default to tab 1.
In our page we have set a land mark role=”main” on heading “Application Process” which can be reached by pressing d or shift+d.

Understanding screen reader interaction modes

https://tink.uk/understanding-screen-reader-interaction-modes/

Chrome Vox’s Bug

Using NVDA: both Title and Description are read.
Chrome Vox: Only Title is read.
Cause:
Obviously it’s a Chrome Vox’s Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=492253
Now I have fixed using a workaround. But from this page I got an important info:
This was marked as won't fix because ChromeVox the extension is no longer under active development. On Mac, you can use VoiceOver with Chrome. You can also use ChromeVox on Chrome OS (which is actively supported).
I installed Chrome Vox as an extension to Chrome, but this extension is no longer developed (bug is no longer fixed!).

Comments

Popular posts from this blog

Use GnuPG Tools or C# Code for PGP Encryption and Signature

Errors in Net Core Add-Migration

Confusing Concepts about SFTP: SSH2 vs OpenSSH