Date   

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.


Re: message announced by NVDA

Jaffar Sidek <jaffar.sidek10@...>
 

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: SPSS and NVDA

William
 

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.


In-Process is out

Quentin Christensen
 

Hi everyone,

The latest In-Process blog post is out, featuring:
- Information on the Translation freeze for 2020.4
- A spotlight on one of the features about to drop
- A training opportunity this weekend, and
- Thanks for an award and donations.


--
Quentin Christensen
Training and Support Manager


message announced by NVDA

bering.p
 

Yes, thanks.
Still, I saw it quite easy to do, but I might be wrong.
For example for gui.messageBox:
- saving "Report object description" option.
- activating "report object description" option
- call to gui.messageBox
- restoration "report object description" option.
And this can also be applied to other NVDA dialogs.
Best regards.
Paul.
Le 28/01/2021 06:36, Joseph Lee a écrit :

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.

 

 



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: message announced by NVDA

 

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.

 

 


message announced by NVDA

bering.p
 

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.

 



Suppressing reading of row and column information in MS Access

Ann Byrne
 

As I move from cell to cell in Access, NVDA reads row and column coordinates , twice. I have turned off reading of column and row in the document configuration, but it makes no difference. It would be hellpful if I could hear only the column headers but not row and column coordinates. Is there a way to do this?

Much thanks,

Ann


Re: message announced by NVDA

 

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: Long-standing Basic Edge/NVDA Issue

Quentin Christensen
 

I just tried opening the system menu in Edge then either restoring, maximizing (with x or arrowing and enter) and escaping, and it worked fine when I closed the menu when I was using NVDA 2020.4beta4.  It did crash, as you describe when using NVDA 2020.3.  We have made some improvements in 2020.4, so I'd recommend trying NVDA 2020.4 beta 4: https://www.nvaccess.org/post/nvda-2020-4beta4/  Do please let us know if the issue is fixed or continues with that version.

Kind regards

Quentin..


On Thu, Jan 28, 2021 at 1:10 PM hurrikennyandopo ... <hurrikennyandopo@...> wrote:

Hi


Which edge are you using is it the old one or the new one? If it is the old one I would replace it with the new one from Microsoft.


Just tried bringing up the menu to maximize etc there is no problems on any of the tabs I try it on.


usually when you bring up the menu you mentioned you locate the one you want then press the enter key on it. So then is it when you press the escape key to close that menu then edge dies?


I thought when I first looked it was more to do with closing tabs. I did bring up that menu you mentioned did not pick one then chose close then the program shut as in edge.


Gene nz


On 28/01/2021 1:51 pm, Janet Brandly wrote:

Hello all,

 

I am using Windows 10 with the last stable version of NVDA, and I have been having the following issue for several months now. When on a web page, if I want to confirm that it is maximized with “alt+space”, and close the system menu with “escape”, NVDA won’t read the page. I know that it has crashed because it won’t read either when I return to the desk top. NVDA will crash even if I only have 1 Edge window open. Any suggestions?

 

Thanks,

 

Janet



--
Quentin Christensen
Training and Support Manager


Re: message announced by NVDA

Sarah k Alawami
 

Did you submit a search on GitHub, or submit an issue? I thought one was. I can’t’ remember now.

 

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.

 

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: silencing certain reading of tables in NVDA

Sarah k Alawami
 

I think I’ve noticed this as well in programs such as excel. I’ll find out in a few weeks when I have to use it to make a report.

 

Tc all.

 

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.

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Louise Pfau
Sent: Wednesday, January 27, 2021 3:03 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] silencing certain reading of tables in NVDA

 

Hi.  I've noticed that when you turn off cell coordinates as described, it completely silences the reading of blank cells in Microsoft Excel spreadsheets.  Cells which contain data are read.  I had to turn it back on.  I don't know if the same thing happens in other programs with a tabular structure.

Thanks,

Louise


message announced by NVDA

bering.p
 

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.

7761 - 7780 of 88904