Date   

NVDA User Guide doesn't open in default browser

Louise Pfau
 

Hi.  I opened the NVDA User Guide to reference something, and I noticed that it didn't open in Microsoft Edge, which is set as my default browser.  Is the specific shortcut to the User Guide set to open in another browser?  I tried to open another web-based manual for comparison, and it opened in Edge.

Thanks,

Louise


Re: message announced by NVDA

Jaffar Sidek <jaffar.sidek10@...>
 

Hi Joseph.   Yup I got your drift.  Thanks for the explanation.  Cheers!

On 29/1/2021 1:02 am, Joseph Lee wrote:

Hi,

The UIA issues I’m talking about can be caused either by the app in question or NVDA not knowing certain UIA properties fully. The former is the case with older Chromium Edge releases where UIA implementation from Edge is incomplete, the latter was the case when NVDA didn’t know about notification event for several weeks during Version 1709 era (October 2017-April 2018).

As for bringing Windows 10 App Essentials to NVDA, as I stated a few days ago, parts of it are available in NVDA now, and I plan to transfer more code from that add-on to NVDA. In fact, NVDA 2020.4 includes support for Windows 10 Calculator, which came directly from Windows 10 App Essentials. The next version of the add-on will include code that may become part of NVDA later, specifically initial support for updated emoji panel being tested by Windows Insiders on development channel (build 21300 series); it is too early to put that code into NVDA because the feature can change without notice, hence I’m letting folks give it a try by incorporating it into WinTenApps first.

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Jaffar Sidek
Sent: Thursday, January 28, 2021 2:25 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] message announced by NVDA

 

Hi Joseph.  Correct me if I am wrong, but what you seem to be saying is that while WxWidgets uses MSAA as it's accessibility go to, NVDA itself relies on both the native Windows dialog and UIA to function properly, particularly with the more newly built apps.  If my assumption is correct, then your win10 issentials AddOn is bridging the gap so as to cause less of a conflict with access issues?  Would it then be better to embed Win10 issentials into NVDA itself?  Cheers!

On 28/1/2021 1:36 pm, Joseph Lee wrote:

Hi,

I think there’s another aspect to account for: it isn’t NVDA that has control over how messages are presented/announced: it is really wxWidgets that controls this. Part of the reason why NVDA’s user interface is accessible is because it isn’t NVDA that instructs Windows that its own message boxes are dialogs; rather, it is wxWidgets that reveals MSAA information to Windows about controls. Therefore, NVDA can announce its own dialog content simply because it is retrieving whatever accessibility API information Windows says about controls.

Speaking of GUI toolkits and NVDA: I’m researching how NVDA will work under more recent wxPython releases (currently NVDA is powered by wxPython 4.0.3 based on wxWidgets 3.0.5). More recent wxPython releases such as 4.1.1 are powered by wxWidgets development code, and tests show most NVDA controls and scenarios will work apart from a weird bug where you can’t perform NVDA commands while NVDA menu is opened and a huge lag when message boxes are open. So far, wxWidgets will use MSAA to reveal information about controls to Windows, and in extension, to NVDA. As opposed to this, QT offers an option to use UIA to communicate control information to Windows and NVDA, and anyone who have experimented with Windows 10 apps may have come across all sorts of UIA issues with apps such as Settings and Mail (these are powered by all sorts of GUI toolkits which uses UIA to talk about controls; UIA issues is another reason why I release Windows 10 App Essentials development builds on a weekly basis).

Hope this helps.

Cheers,

JOseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of bering.p
Sent: Wednesday, January 27, 2021 9:24 PM
To: nvda@nvda.groups.io
Subject: [nvda] message announced by NVDA

 

Thank you Joseph for your reply.
I am satisfied with the general behavior of NVDA regarding the announcement of the object description.
But I think in the case of a message issued by NVDA using gui.messageBox and which
presents only a dialog box with a text and one or two buttons, the text must be announced whatever the state of the option.
obviously, this is a point of view and I am perhaps the only one to deactivate the announcement of the description of the objects for the "normal configuratio" profiln.
Best regards
Paul.



Paul.

Le 28/01/2021 04:36, Joseph Lee a écrit :

Hi,

An object’s description is typically retrieved through accessibility API’s, although screen readers can customize certain behavior. This is the approach used by NVDA: NvDA defines dialog text as a dialog’s description. As you’ve observed, if report object descriptions is off, NVDA will not announce description text for controls such as dialog text.

As for defining messages NVDA should announce all the time, in theory, it might be possible. In practice though, think about the following:

  1. Different people have different ways to define what “essential” messages are. Some would say dialog text should be announced all the time, while others may say NVDA should announce clipboard operations including in places where you can’t copy or paste things.
  2. Screen readers do not possess hundreds of magnifying glasses; that is, screen readers cannot announce everything on the screen.

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of bering.p
Sent: Wednesday, January 27, 2021 7:10 PM
To: nvda courrier <nvda@nvda.groups.io>
Subject: [nvda] message announced by NVDA

 

Hi.
I am surprised that this question is not answered .
So I return in my box with it.
Best regards.
Paul.

Le 23/01/2021 09:56, bering.p a écrit :

Hi to all.
I am sharing with you an observation I made concerning the announcement of messages by NVDA and which may be the subject of a PR.

When the option "Report object descriptions" is disabled, NVDA does not speak the text in dialog boxes.
This is annoying when it comes to a message informing the user or questioning him.
For example:
- following a manual search for update request.
- when an add-on uses "gui.messageBox" to query the user.

In this case, it is necessary to read the contents of the dialog box using "NVDA + b".

I think that any message emitted by NVDA should be announced regardless of the state of activation of the option.
What do you think ?
And if you agree, please do the PR.
best regards.
Paul.

 

 


is there an addon for signal?

Ibrahim Abedrabbo
 

Hi folks,

I am gradually transitioning from WhatsApp messenger to signal messenger. I installed the signal desktop client and it seems to be fine except  in reading group messages. Does anyone know if there is an NVDA add on for signal?

Cheers,

 

Ibrahim


Re: unigram accessibility

Lino Morales
 

Your better off using de Shark da doot da doot with Doug Lee's scripts buddy.

On 1/28/2021 12:41 AM, Governor staten wrote:
Hello list. I Downloaded an add-on for Unigram. It doesn't seem to do much. Is there more than one add-on out there? It could be that the program has changed and the add-on no longer works. Any help with this would be most appreciated.





Re: Focus Blue 4th generation problem?

Chantelle Buys
 

Thanks.

I'm also thinking that it's a display problem but, how to fix it?

Is there no way to reset a display to factory default?

Chantelle

On 1/28/21, Bob Cavanaugh <cavbob1993@gmail.com> wrote:
I'm going to take a wild guess on the problem of NVDA resetting your
settings to no braille. There's an option, I think off by default,
that reads "save configuration on exit." If this is unchecked, next
time NVDA starts, it will load the configuration it has saved. As for
your other problem, I have no idea but since you say the same thing
happens on your phone, I'd guess it's a braille display problem.

On 1/28/21, Chantelle Buys <cbuys6@gmail.com> wrote:
Afternoon everyone.

Just a quick question. I have a Focus Blue 40 cell display to try out
and have run into a strange problem.

Nvda resets the settings to no braille each time I restart the program
and for some or other reason, when you try to type lets say the
alphabet, it does the strangest thing. I would get the letters A/b
but, when I want to type c/d and so on, it would show other braille
symbols instead. I also realized that when I press dot1/4/7/8 after
pressing the power key to get to menu, the display won't do anything.

So, the same happens on android/IOS and since I don't know what's
going on here I just want to ask if any nvda user knows how to get the
braille keyboard to work the right way around and if somethings gone
wrong with the display?

Chantelle

--
Never give up, at any cost.









--
Never give up, at any cost.


Re: Focus Blue 4th generation problem?

Bob Cavanaugh <cavbob1993@...>
 

I'm going to take a wild guess on the problem of NVDA resetting your
settings to no braille. There's an option, I think off by default,
that reads "save configuration on exit." If this is unchecked, next
time NVDA starts, it will load the configuration it has saved. As for
your other problem, I have no idea but since you say the same thing
happens on your phone, I'd guess it's a braille display problem.

On 1/28/21, Chantelle Buys <cbuys6@gmail.com> wrote:
Afternoon everyone.

Just a quick question. I have a Focus Blue 40 cell display to try out
and have run into a strange problem.

Nvda resets the settings to no braille each time I restart the program
and for some or other reason, when you try to type lets say the
alphabet, it does the strangest thing. I would get the letters A/b
but, when I want to type c/d and so on, it would show other braille
symbols instead. I also realized that when I press dot1/4/7/8 after
pressing the power key to get to menu, the display won't do anything.

So, the same happens on android/IOS and since I don't know what's
going on here I just want to ask if any nvda user knows how to get the
braille keyboard to work the right way around and if somethings gone
wrong with the display?

Chantelle

--
Never give up, at any cost.






Re: NVDA Beta 4 error tone when opening outlook

 

Hi all,

I can’t speak to NV Access, but personally whenever you hear an error tone from NvDA (alpha and beta snapshots), I advise opening log viewer (NVDA+F1) and look at lines above developer info statement as it will record the error and traceback information so we (developers) can diagnose the problem. This is more so if you hear error tones constantly (from anywhere).

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Brian Vogel
Sent: Thursday, January 28, 2021 10:17 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA Beta 4 error tone when opening outlook

 

On Thu, Jan 28, 2021 at 01:07 PM, Gary Metzler wrote:

When using the beta this sound is normal.

-
Yes and no.  I agree with you, from a practical standpoint, that this tone generally doesn't indicate that anything's wrong that the end user would be concerned about unless there were an obvious bad behavior.  That being said, even in the beta it does indicate that an error condition of some sort has been encountered, and if your logging level happens to be set to debug you can look at the NVDA log to see what, exactly, it is that was not liked.
--

Brian - Windows 10 Pro, 64-Bit, Version 20H2, Build 19042  

The depths of denial one can be pushed to by outside forces of disapproval can make you not even recognize yourself to yourself.

       ~ Brian Vogel

 


Re: NVDA Beta 4 error tone when opening outlook

 

On Thu, Jan 28, 2021 at 01:07 PM, Gary Metzler wrote:
When using the beta this sound is normal.
-
Yes and no.  I agree with you, from a practical standpoint, that this tone generally doesn't indicate that anything's wrong that the end user would be concerned about unless there were an obvious bad behavior.  That being said, even in the beta it does indicate that an error condition of some sort has been encountered, and if your logging level happens to be set to debug you can look at the NVDA log to see what, exactly, it is that was not liked.
--

Brian - Windows 10 Pro, 64-Bit, Version 20H2, Build 19042  

The depths of denial one can be pushed to by outside forces of disapproval can make you not even recognize yourself to yourself.

       ~ Brian Vogel

 


Re: NVDA Beta 4 error tone when opening outlook

Gary Metzler
 

Hi Steve,

 

When using the beta this sound is normal.  There is nothing to worry about.

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Steve Nutt
Sent: Thursday, January 28, 2021 12:36 PM
To: nvda@nvda.groups.io
Subject: [nvda] NVDA Beta 4 error tone when opening outlook

 

Hi Guys,

 

I have just downloaded Beta 4 and I notice that every time I open Outlook, I get the two piano tone error sound from NVDA.

 

This is using Office 365.

 

Anyone else getting this?

 

Thanks.

 

All the best


Steve

 

--

Computer Room Services

77 Exeter Close

Stevenage

Hertfordshire

SG1 4PW

T: +44(0)1438-742286

M: +44(0)7956-334938

F: +44(0)1438-759589

E: steve@...

W: https://www.comproom.co.uk

 


Focus Blue 4th generation problem?

Chantelle Buys
 

Afternoon everyone.

Just a quick question. I have a Focus Blue 40 cell display to try out
and have run into a strange problem.

Nvda resets the settings to no braille each time I restart the program
and for some or other reason, when you try to type lets say the
alphabet, it does the strangest thing. I would get the letters A/b
but, when I want to type c/d and so on, it would show other braille
symbols instead. I also realized that when I press dot1/4/7/8 after
pressing the power key to get to menu, the display won't do anything.

So, the same happens on android/IOS and since I don't know what's
going on here I just want to ask if any nvda user knows how to get the
braille keyboard to work the right way around and if somethings gone
wrong with the display?

Chantelle

--
Never give up, at any cost.


Re: Strange Behavior When Adding Mozilla Apps Add-on to Latest Beta

Gene
 

That's because the program crashed.  it didn't shut down properly.  If the add-on works properly, its nothing to worry about.  Its when a program crashes when you are working with it that mattters, chrashing on shutdown doesn't unless the program does some sort of housekeeping during shutdown which NVDA doesn't, except for maybe some log entries.
 
Gene

-----Original Message -----
Sent: Thursday, January 28, 2021 11:32 AM
Subject: [nvda] Strange Behavior When Adding Mozilla Apps Add-on to Latest Beta

I'm running 2020.4 beta 4. When I add Mozilla-1.12.nvda-addon and get to
the prompt to restart NVDA, I hear the ascending A chord telling me NVDA
has relloaded. I do not hear the descending chord first telling me it
was unloaded.

I also find an extra NVDA icon hanging around in the System Tray.


Cris







NVDA Beta 4 error tone when opening outlook

Steve Nutt
 

Hi Guys,

 

I have just downloaded Beta 4 and I notice that every time I open Outlook, I get the two piano tone error sound from NVDA.

 

This is using Office 365.

 

Anyone else getting this?

 

Thanks.

 

All the best


Steve

 

--

Computer Room Services

77 Exeter Close

Stevenage

Hertfordshire

SG1 4PW

T: +44(0)1438-742286

M: +44(0)7956-334938

F: +44(0)1438-759589

E: steve@...

W: https://www.comproom.co.uk

 


Strange Behavior When Adding Mozilla Apps Add-on to Latest Beta

Chris Smart
 

I'm running 2020.4 beta 4. When I add Mozilla-1.12.nvda-addon and get to the prompt to restart NVDA, I hear the ascending A chord telling me NVDA has relloaded. I do not hear the descending chord first telling me it was unloaded.

I also find an extra NVDA icon hanging around in the System Tray.


Cris


Re: message announced by NVDA

 

Hi,

The UIA issues I’m talking about can be caused either by the app in question or NVDA not knowing certain UIA properties fully. The former is the case with older Chromium Edge releases where UIA implementation from Edge is incomplete, the latter was the case when NVDA didn’t know about notification event for several weeks during Version 1709 era (October 2017-April 2018).

As for bringing Windows 10 App Essentials to NVDA, as I stated a few days ago, parts of it are available in NVDA now, and I plan to transfer more code from that add-on to NVDA. In fact, NVDA 2020.4 includes support for Windows 10 Calculator, which came directly from Windows 10 App Essentials. The next version of the add-on will include code that may become part of NVDA later, specifically initial support for updated emoji panel being tested by Windows Insiders on development channel (build 21300 series); it is too early to put that code into NVDA because the feature can change without notice, hence I’m letting folks give it a try by incorporating it into WinTenApps first.

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Jaffar Sidek
Sent: Thursday, January 28, 2021 2:25 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] message announced by NVDA

 

Hi Joseph.  Correct me if I am wrong, but what you seem to be saying is that while WxWidgets uses MSAA as it's accessibility go to, NVDA itself relies on both the native Windows dialog and UIA to function properly, particularly with the more newly built apps.  If my assumption is correct, then your win10 issentials AddOn is bridging the gap so as to cause less of a conflict with access issues?  Would it then be better to embed Win10 issentials into NVDA itself?  Cheers!

On 28/1/2021 1:36 pm, Joseph Lee wrote:

Hi,

I think there’s another aspect to account for: it isn’t NVDA that has control over how messages are presented/announced: it is really wxWidgets that controls this. Part of the reason why NVDA’s user interface is accessible is because it isn’t NVDA that instructs Windows that its own message boxes are dialogs; rather, it is wxWidgets that reveals MSAA information to Windows about controls. Therefore, NVDA can announce its own dialog content simply because it is retrieving whatever accessibility API information Windows says about controls.

Speaking of GUI toolkits and NVDA: I’m researching how NVDA will work under more recent wxPython releases (currently NVDA is powered by wxPython 4.0.3 based on wxWidgets 3.0.5). More recent wxPython releases such as 4.1.1 are powered by wxWidgets development code, and tests show most NVDA controls and scenarios will work apart from a weird bug where you can’t perform NVDA commands while NVDA menu is opened and a huge lag when message boxes are open. So far, wxWidgets will use MSAA to reveal information about controls to Windows, and in extension, to NVDA. As opposed to this, QT offers an option to use UIA to communicate control information to Windows and NVDA, and anyone who have experimented with Windows 10 apps may have come across all sorts of UIA issues with apps such as Settings and Mail (these are powered by all sorts of GUI toolkits which uses UIA to talk about controls; UIA issues is another reason why I release Windows 10 App Essentials development builds on a weekly basis).

Hope this helps.

Cheers,

JOseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of bering.p
Sent: Wednesday, January 27, 2021 9:24 PM
To: nvda@nvda.groups.io
Subject: [nvda] message announced by NVDA

 

Thank you Joseph for your reply.
I am satisfied with the general behavior of NVDA regarding the announcement of the object description.
But I think in the case of a message issued by NVDA using gui.messageBox and which
presents only a dialog box with a text and one or two buttons, the text must be announced whatever the state of the option.
obviously, this is a point of view and I am perhaps the only one to deactivate the announcement of the description of the objects for the "normal configuratio" profiln.
Best regards
Paul.



Paul.

Le 28/01/2021 04:36, Joseph Lee a écrit :

Hi,

An object’s description is typically retrieved through accessibility API’s, although screen readers can customize certain behavior. This is the approach used by NVDA: NvDA defines dialog text as a dialog’s description. As you’ve observed, if report object descriptions is off, NVDA will not announce description text for controls such as dialog text.

As for defining messages NVDA should announce all the time, in theory, it might be possible. In practice though, think about the following:

  1. Different people have different ways to define what “essential” messages are. Some would say dialog text should be announced all the time, while others may say NVDA should announce clipboard operations including in places where you can’t copy or paste things.
  2. Screen readers do not possess hundreds of magnifying glasses; that is, screen readers cannot announce everything on the screen.

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of bering.p
Sent: Wednesday, January 27, 2021 7:10 PM
To: nvda courrier <nvda@nvda.groups.io>
Subject: [nvda] message announced by NVDA

 

Hi.
I am surprised that this question is not answered .
So I return in my box with it.
Best regards.
Paul.

Le 23/01/2021 09:56, bering.p a écrit :

Hi to all.
I am sharing with you an observation I made concerning the announcement of messages by NVDA and which may be the subject of a PR.

When the option "Report object descriptions" is disabled, NVDA does not speak the text in dialog boxes.
This is annoying when it comes to a message informing the user or questioning him.
For example:
- following a manual search for update request.
- when an add-on uses "gui.messageBox" to query the user.

In this case, it is necessary to read the contents of the dialog box using "NVDA + b".

I think that any message emitted by NVDA should be announced regardless of the state of activation of the option.
What do you think ?
And if you agree, please do the PR.
best regards.
Paul.

 

 


Re: unigram accessibility

Sarah k Alawami
 

I never ever need to search, so no I have not had to try that. I also found links were at the time inaccessible, in the media and links section, but since I rarely used those and kept a running tally in my head as to order per chat if possible, I was fine, but I’m the exception, not the rule, which is unfortunate.

 

 

 

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Governor staten
Sent: Thursday, January 28, 2021 8:36 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] unigram accessibility

 

Chats, and typing in chats is fine. How about searching for things in that program? Have you tried that? It doesn't seem to work well with NVDA at all. The search screen is the main issue.

 

 


 

On 1/28/2021 11:11 AM, Sarah k Alawami wrote:

No add on needed, what seems to be the problem with Uigram? The last time I used it it read fine, you could lock the record button with control r and find the speed up button just perfectly. Everything to my knowledge  is labeled.
 
Sarah Alawami, owner of TFfP. We are also on lbry as well. 
 
Stay in touch with us via our discord. This is an easier way to both contact us, and get to know your fellow listeners.
 
-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Governor staten
Sent: Wednesday, January 27, 2021 9:42 PM
To: nvda@nvda.groups.io
Subject: [nvda] unigram accessibility
 
Hello list. I Downloaded an add-on for Unigram. It doesn't seem to do much. Is there more than one add-on out there? It could be that the program has changed and the add-on no longer works. Any help with this would be most appreciated.
 
 
 
 
 
 
 
 
 
 
 
 


Re: unigram accessibility

 

Chats, and typing in chats is fine. How about searching for things in that program? Have you tried that? It doesn't seem to work well with NVDA at all. The search screen is the main issue.





On 1/28/2021 11:11 AM, Sarah k Alawami wrote:
No add on needed, what seems to be the problem with Uigram? The last time I used it it read fine, you could lock the record button with control r and find the speed up button just perfectly. Everything to my knowledge  is labeled.

Sarah Alawami, owner of TFfP. We are also on lbry as well. 

Stay in touch with us via our discord. This is an easier way to both contact us, and get to know your fellow listeners.

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Governor staten
Sent: Wednesday, January 27, 2021 9:42 PM
To: nvda@nvda.groups.io
Subject: [nvda] unigram accessibility

Hello list. I Downloaded an add-on for Unigram. It doesn't seem to do much. Is there more than one add-on out there? It could be that the program has changed and the add-on no longer works. Any help with this would be most appreciated.













Re: SPSS and NVDA

 

I personally doubt that there will be any significant investment in changing the SPSS GUI interface.  This is ancient, and very stable, software that's entered "cash cow" status long, long ago.

It has a command line interface (CLI), and that's actually how I used it way back when.  I don't think the GUI even existed in the 1980s (though it may have).

From an accessibility standpoint, were I someone who had to use SPSS routinely, I'd invest way more time and effort in learning the CLI and how to access the datasets outside the SPSS GUI, which you can also do, than hoping that the GUI will become accessible at any time in the foreseeable future.
--

Brian - Windows 10 Pro, 64-Bit, Version 20H2, Build 19042  

The depths of denial one can be pushed to by outside forces of disapproval can make you not even recognize yourself to yourself.

       ~ Brian Vogel

 


Re: SPSS and NVDA

Sarah k Alawami
 

Have you contacted the developers of this app to show them what happens? It looks like this is a better route, in fact most of the time, it is. I say most as there are exceptions. For example, death or software abandonment. If you did contact the developer what was their response?

Good luck.

Sarah Alawami, owner of TFfP. We are also on lbry as well.

Stay in touch with us via our discord. This is an easier way to both contact us, and get to know your fellow listeners.

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of William
Sent: Thursday, January 28, 2021 2:20 AM
To: nvda@groups.io
Subject: Re: [nvda] SPSS and NVDA

Hifolks,


With the instructions from my friend, today I was able to complete many of the data analysis task by myself. e.g. I am able to import data from excel and do data preparation and some test like t-test.


I aware two areas that screen reader may pay attention to :

1. SPSS has a syntext function, which is a program code like interface.

screen reader can make use of this function, so that we can avoideinteracting with the ui, but only deal with codes.


2 on some areas, nvda still have accessibility issue.

e.g. sometimes when a window pop up, nvda did not read the content of
the window, even pressing nvda + b cannot read the pop up window. I have
to use review cursor to read the window.

sometimes, changing the view, e.g. change from variable view back to
data view, nvda will become silent.

And one of the most annoying thing is that, the savepop up window is not
accessible. When you press ctrl s or quit the program, SPSS will promt
you for saving the file, however, the pop up windows is not accessible
by pressing tab or any alternative ways. I have to manually move the
mouse on to the window, then click with right lick, then nvda can read
the button again.


I would say SPSS is usable for screen reader user.

But still lots of areas that need to be fixed.SuperSilly 於 30/12/2020
20:49 寫道:

Hi,

I could not find relevant information on whether SPSS is accessible
using NVDA.

Is there any person here has experience in using SPSS with NVDA?

Do you have any information on how I should do with it?


Thanks.


Re: unigram accessibility

Sarah k Alawami
 

No add on needed, what seems to be the problem with Uigram? The last time I used it it read fine, you could lock the record button with control r and find the speed up button just perfectly. Everything to my knowledge is labeled.

Sarah Alawami, owner of TFfP. We are also on lbry as well.

Stay in touch with us via our discord. This is an easier way to both contact us, and get to know your fellow listeners.

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Governor staten
Sent: Wednesday, January 27, 2021 9:42 PM
To: nvda@nvda.groups.io
Subject: [nvda] unigram accessibility

Hello list. I Downloaded an add-on for Unigram. It doesn't seem to do much. Is there more than one add-on out there? It could be that the program has changed and the add-on no longer works. Any help with this would be most appreciated.


Re: Spinning numbers on a bank page?!

Josh Kennedy
 

did you try turning off browse mode with insert SPACE? Then tab through the numbers and use the up and down arrow keys or left and right arrow to set them and then tab to the button you want and press enter. Then if needed turn browse mode back on by pressing insert SPACE.

6621 - 6640 of 87777