Hi Group,

Although I changed nothing, starting this morning NVDA began making
beeping and other kinds of sounds as I scroll up or down or move among
buttons and check boxes.
-- Where in the menus can I change it to as it used to be?
Nevzat Adil
Library of Congress Certified
Literary Braille Proofreader
C: 512 502 4403
e-mail: nevzatadil@...
Facebook: m.facebook.com/LiteraryBrailleProofreader

Windows Magnifier

• Author: Cyrille Bougot
• NVDA compatibility: 2018.3 and beyond
• Download stable version
• Download development version

This add-on improves the use of Windows Magnifier with NVDA.

Features

• Allows to report the result of some native Magnifier keyboard commands.
• Allows to reduce the cases where table navigation commands conflict with Magnifier's commands.
• Adds some keyboard shortcuts to toggle various Magnifier options.

Settings

The setting panel of Windows Magnifier add-on allows to configure how NVDA reacts to native Windows Magnifier commands. You may want to have more or less commands reported according to what you are able to see. This panel may be opened choosing Preferences -> Settings in the NVDA menu and then selecting the Windows Magnifier category in the Settings window. The keyboard shortcut NVDA+Windows+O then O also allows to open this settings panel directly.

The panel contains the following options:

• Report view moves: controls what is reported when you move the view with Control+Alt+Arrows commands. The three options are:

  • Off: Nothing is reported.
  • With speech: a speech message indicates the position of the zoomed view on the dimension the view is being moved.
  • With tones: a tone is played and its pitch indicates the position of the zoomed view on the dimension the view is being moved.

  This option only affects full view mode.

• Report turn on or off: If checked, the Magnifier's state is reported when you use Windows++ or Windows+Escape commands to turn it on or off.

• Report zoom: If checked, the Magnifier's zoom level is reported when you use Windows++ or Windows+- zoom commands.
• Report color inversion: If checked, the color inversion state is reported when you use the control+Alt+I toggle command.
• Report view change: If checked, the view type is reported when you use a command that changes the view type (Control+Alt+M, Control+Alt+F, Control+Alt+D, Control+Alt+L)
• Report lens or docked window resizing: If checked, a message is reported when you use the resizing commands (Alt+Shift+Arrows). In docked window mode, the height or the width is reported. In lens mode, the new dimension cannot be reported for now. These resizing command do not seem to be available on all versions of Windows; if your Windows version does not support them, you should keep this option unchecked.

• In documents and list views, pass control+alt+arrows shortcuts to Windows Magnifier: There are three possible choices:

  • Never: The command is not passed to Windows Magnifier and standard NVDA table navigation can operate. When used in documents out of a table, the Control+Alt+Arrow command reports a "Not in a table" error message. This is the standard behaviour of NVDA without this add-on.
  • Only when not in table: In table or in list views, Control+Alt+Arrow commands perform standard table navigation. When used in documents out of a table, Control+Alt+Arrow commands perform standard Magnifier view move commands. If you still want to move Windows Magnifier view while in table or in list view, you will need to press NVDA+F2 before using Control+Alt+Arrow commands. This option is the best compromise if you want to use Control+Alt+Arrow for both Magnifier and table navigation.
  • Always: Control+Alt+Arrow commands moves the Magnifier's view in any case. This option may be useful if you do not use Control+Alt+Arrow to navigate in table, e.g. because you have changed table navigation shortcuts in NVDA or because you exclusively use Easy table navigator add-on for table navigation.

Commands added by this add-on

In addition to native Magnifier commands, this add-on provide additional commands that allow to control Magnifier's options without opening its configuration page. All the commands added to control Magnifier options are accessible through the Magnifier layer command NVDA+Windows+O:

• NVDA+Windows+O then C: Toggles on or off caret tracking.
• NVDA+Windows+O then F: Toggles on or off focus tracking.
• NVDA+Windows+O then M: Toggles on or off mouse tracking.
• NVDA+Windows+O then T: Toggles on or off tracking globally.
• NVDA+Windows+O then S: Toggles on or off smoothing.
• NVDA+Windows+O then R: Switches between mouse tracking modes (within the edge of the screen or centered on the screen); this feature is only available on Windows 10 build 17643 or higher.
• NVDA+Windows+O then X: Switches between text cursor tracking modes (within the edge of the screen or centered on the screen); this feature is only available on Windows 10 build 18894 or higher.
• NVDA+Windows+O then V: Moves the mouse cursor in the center of the magnified view (command available in full screen view only).
• NVDA+Windows+O then O: Opens Windows Magnifier add-on settings.
• NVDA+Windows+O then H: Displays help on Magnifier layer commands.

There is no default direct gesture for each command, but you can attribute one normally in the input gesture dialog if you wish. The same way, You can also modify or delete the Magnifier layer access gesture (NVDA+Windows+O). Yet, you cannot modify the shortcut key of the Magnifier layer sub-commands.

Magnifier's native commands

The result of the following Magnifier native commands may be reported by this add-on, according to its configuration:

• Start Magnifier: Windows++ (on alpha-numeric keyboard or on numpad)
• Quit Magnifier: Windows+Escape
• Zoom in: Windows++ (on alpha-numeric keyboard or on numpad)
• Zoom out: Windows+- (on alpha-numeric keyboard or on numpad)
• Toggle color inversion: Control+Alt+I
• Select the docked view: Control+Alt+D
• Select the full screen view: Control+Alt+F
• Select the lens view: Control+Alt+L
• Cycle through the three view types: Control+Alt+M
• Resize the lens with the keyboard: Shift+Alt+Left/Right/Up/DownArrow. Note: although this does not seem to be documented, this shortcut seems to have been withdrawn in recent Windows versions such as Windows 2004.
• Move the magnified view: Control+Alt+Arrows (reporting only affects full screen mode)

Here is also a list of other Magnifier native commands, just for information:

• Control+Alt+mouseScrollWheel: Zooms in and out using the mouse scroll wheel.
• Control+Windows+M: Opens the Magnifier's settings window.
• Control+Alt+R: Resizes the lens with the mouse.
• Control+Alt+Space: Quickly shows the entire desktop when using full screen view.

None of the Magnifier native commands can be modified.

Notes

• For computers equipped with an Intel graphic card, control+alt+arrow (left/right/up/down) are also shortcuts to modify the orientation of the screen. These shortcut are enabled by default and conflict with Windows Magnifiers shortcuts to move the view. You will need to disable them to be able to use them for the Magnifier. They can be disabled in the Intel control panel or in the Intel menu present in the system tray.

• Depending on your Windows version, Alt+Shift+Arrow are Windows Magnifier shortcuts to resize the magnified view (lens or docked). When Magnifier is active (even in full screen mode), these shortcuts are captured by Magnifier and cannot be passed to the application, even if you press NVDA+F2 before. To use these shortcuts in the current application, you need to quit the Magnifier (Windows+Escape) and re-open it after (Windows++). For example in MS word, to decrease title level:

  • Press Windows+Escape to quit Magnifier.
  • Press Alt+Shift+RightArrow to decrease current title level.
  • Press Windows++ to re-open the Magnifier.

• For more information about Windows Magnifier's features and shortcuts, you may want to consult the following pages:

  • Use Magnifier to make things on the screen easier to see
  • Windows keyboard shortcuts for accessibility

Change log

Version 1.0

• Initial release.

Hi,

As for that, I don't know.

Cheers,

Joseph

So, we are finally getting close to including addon updater in core of nvda.

So when exactly will we get all this in the main program?

--

It's a downloadable file, But have no idea where to save it to work with NVDA.

On 7/7/21, Sascha Cowley via groups.io
<sascha.camille@...> wrote:

This functionality is available through the instantTranslate (
https://addons.nvda-project.org/addons/instantTranslate.en.html ) addon.

--
Nevzat Adil
Library of Congress Certified
Literary Braille Proofreader
C: 512 502 4403
e-mail: nevzatadil@...
Facebook: m.facebook.com/LiteraryBrailleProofreader

This functionality is available through the instantTranslate addon.

Hi Group[,

I was told NVDA has language translation capability, but checking the
menus I was not able to spot it.
For instance, with a combination of keystrokes NVDA will translate a
language into another.
Does anyone know about this?
--
Nevzat Adil
Library of Congress Certified
Literary Braille Proofreader
C: 512 502 4403
e-mail: nevzatadil@...
Facebook: m.facebook.com/LiteraryBrailleProofreader

We are building an Albanian RHVoice.  We would like to get feedback from NVDA native Albanian speakers, as we progress. 

Please contact inq@...

Thanks,
- LP

Hi,

Hopefully to clarify more than one question (because I do see this on the mentioned Win10 Forum, which is undergoing a name change process at the moment):

I can assure you all that screen reader vendors and Microsoft are aware of user interface oddities. For example, there are UI label issues affecting major screen readers (Narrator included), details of which require explanation of the toolkit used to code UI elements (beyond the scope of this list, I'm afraid). I have published workarounds for NVDA users in the form of Windows App Essentials add-on development builds, but there are other issues to be discovered. Given prevalence of UI issues with current Windows 11 Insider Preview builds (namely how data is exposed to screen readers), I have advised Windows UI team to resolve issues as soon as possible.

My advice for Windows 11 discussion: follow Brian's advice. I will do everything I can to make sure screen reader users navigating Windows 11 are not forgotten and treated with respect, provided that I won't collapse due to a combination of graduate school prep anxiety and nightly debugging and debate sessions with Windows Insiders and Microsoft people. I can assure you that NVDA users will receive workarounds through Windows App Essentials add-on in the foreseeable future (this is one of those moments where I might just beg Microsoft to pay for graduate school or give grants to NV Access, but I feel that's too much; that's my feeling regarding current state of UI issues with Windows 11 preview, but I remain hopeful that things can be resolved by end of this year). Also, I said it before but I'm putting in all caps: SUPPORT FOR Windows 11 FROM NVDA IS EXPERIMENTAL AND THINGS CAN CHANGE WITHOUT NOTICE, DO NOT USE Windows 11 PREVIEW RELEASE WITHOUT KEEPING BUGS IN MIND!

P.S. I know that folks rarely see me write the above in all caps, but please, please, please, remember the above warning.

Cheers,

Joseph

On Tue, Jul 6, 2021 at 08:25 PM, Joseph Lee wrote:

I expect policies about unmaintained add-ons might change in the future

-
Well, I hope those changes might reflect consideration of the input here.  And I do mean consideration, not that each and every one of us who's offered an opinion will get what we want.

There seems to be a general consensus over time that how things are organized is "not organic" as far as what one would expect and that eases finding what one might be looking for in a somewhat natural/logical way.
--

Brian - Windows 10, 64-Bit, Version 21H1, Build 19043  

I do not understand why some seek to separate a person from their actions.  The self is composed of an individual’s thoughts, actions, and expression, which are contained in and actuated by the body.  What you do and say is the clearest indicator of who you are.

      ~ Brian Vogel

 

Hi,

A few months ago there was a discussion about unmaintained add-ons on add-ons list. The consensus is that it is really up to add-on authors to show responsibility, with an option for the community to take care of (maintain) an add-on after waiting on authors for a few months. The fact that one of the add-ons that I haven't maintained for a while just received an update from someone is an example of willingness by the community to keep an eye on unmaintained add-ons.

I expect policies about unmaintained add-ons might change in the future (won' t go into details because it is up to nV Access and add-ons community to communicate future activities0.

Cheers,

Joseph