NVDA Community Addons/ addons/ WordNav  (33%)

WordNav

  • 作者: Tony Malykh
  • ダウンロード 安定版
  • NVDA 互換性: 2019.3 以降

WordNav NVDA add-on improves built-in navigation by word, as well as adds extra word navigation commands with different definition for the word. It also provides word selection commands.

多くのテキストエディタは、Control+左矢印/右矢印コマンドでの単語ナビゲーションをサポートしています。ただし、単語の定義は、プログラム個々に変化します。これは、Monacoなどの、モダンなウェブベースのテキストエディタについて、特にそうです。NVDAは、与えられたプログラムで単語を正確に読み上げるためには、単語の定義を知らなくてはなりません。もし、NVDAが正確な定義を知らない場合、単語が飛ばされる、または、複数回発音されます。さらに、いくつかのウェブベースのテキストエディタは、カーソルを単語の最初ではなく、終わりに置きます。これにより、視覚障害ユーザーにとっては、編集がより困難になります。この問題に取り組むために、私は、単語の定義をNotepad++から取り、プログラムの単語の定義に頼らず、むしろNVDA側で行から単語に分ける、拡張された単語ナビゲーションコマンドを作りました。Control+左矢印/右矢印ジェスチャーは、プログラムに送られないため、読み上げの一貫性を確保します。

Word navigation and word definitions

Currently WordNav supports five definitions of the word, assigned to different gestures:

  • 左コントロール+矢印: Notepad++の定義で、英数文字を単語として扱い、隣の句読点記号もまた単語として扱います。多くのユーザーにとって最も便利な単語の定義であるはずです。
  • 右コントロール+矢印: 細かい単語定義で、camelCaseIdentifiersとunderscore_separated_identifiersを複数の部分に分け、カーソルが長い識別子内に行くようにします。
  • LeftControl+Windows+Arros: Bulky word definition treats almost all punctuation symbols adjacent to text as part of a single word, therefore it would treat paths like C:\directory\subdirectory\file.txt as a single word.
  • 右コントロール+ウィンドウズ+矢印: 複数単語定義で、いくつかの単語を組にします。単語数を設定出来ます。
  • Unassigned: custom regular expression word definition: allows user to define a custom regular expression for word boundaries.

ジェスチャーは、WordNav設定パネルで変更出来ます。

Word selection

Word selection is supported starting with WordNav v2.0. Just add shift modifier to any word navigation gestures to select words. There is also one extra gesture for word selection:

  • control+shift+numpad1 and control+windows+shift+numpad1 select word to the right similar to their rightArrow counterparts, but they also include trailing spaces into selection.

Please note, however, that currently used accessibility APIs have multiple issues related to word selection. Please get yourself familiar with the following list of issues and workarounds:

  • UIA applications (e.g. Notepad, Visual Studio, Microsoft Word) don't support setting caret at the beginning of selection. In those applications caret location is stored on WordNav side. As an adverse side effect, word navigation commands might not play well with line and paragraph selection commands (shift+up/downArrow, control+shift+up/downArrow) and results might be unpredictable. For convenience, character selection commands (shift+left/rightArrow) have been updated in WordNav for UIA applications and should work well.
  • Basic single line Windows edit controls also don't allow to set the caret in front of selection, so the previous point also applies to them. This affects all single line edit boxes within NVDA.
  • IAccessible2 doesn't provide a way to set selection spanning across multiple paragraphs. There is no known workaround for this issue. This affects rich multiline edit boxes in Chrome and Firefox, such as compose email text area in GMail and compose email window in Thunderbird.
  • In notepad++ selection update messages come unreasonably slow. As a workaround, WordNav announces selection on NVDA side for word selection commands and silences late notifications for the following 0.5 seconds. As a result, if you press word selection command followed by another (e.g. character) selection command in quick succession, you might miss selection notification for the latter one if it came within 0.5 seconds from the last word selection command.
  • In multiline edit boxes supporting TOM interface NVDA incorrectly identifies cursor location when selection is present. This has been fixed in nvaccess/nvda#16455, which is scheduled to be included in NVDA v2024.2 release. Before that release word selection commands won't work correctly in TOM edit boxes, such as NVDA log viewer.

備考

  • Windows 10のバーチャルデスクトップ機能を使用したい場合は、Control+Windows+矢印のショートカットキーを、WordNav設定パネル、またはNVDA入力ジェスチャーダイアログで無効かするのを覚えておいて下さい。
  • Compatibility with VSCode requires NVDA add-on IndentNav v2.0 or later to be installed. Additionally, VSCode extension Accessibility for NVDA IndentNav must be installed in VSCode.

Downloads

Please install the latest version from NVDA add-on store.