Date   

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.


Re: Long-standing Basic Edge/NVDA Issue

hurrikennyandopo ...
 

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


Re: Long-standing Basic Edge/NVDA Issue

Gene
 

I have seen little or no difference in reading web pages whether browsers are maximized or not.  In addition, the browsers I've used will remember if you have maximized them and will remain maximized when you open it again.  In short, if others have this problem, it may be something worth addressing, but as a practical matter, the problem shouldn't matter if you maximize the browser and assume it remains maximized. 
 
Gene

-----Original Message-----
Sent: Wednesday, January 27, 2021 6:51 PM
Subject: [nvda] Long-standing Basic Edge/NVDA Issue

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


Long-standing Basic Edge/NVDA Issue

Janet Brandly
 

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


Re: braille bar NVDA store

Quentin Christensen
 

I've never heard of this one - have you got a web page link to the company who makes these please?

Kind regards

Quentin.

On Thu, Jan 28, 2021 at 5:40 AM marinos.poulimas <marinos.poulimas@...> wrote:
hello to all my friends i want to ask two questions question 1 how can i
connect the braille bar below to NVDA it is not supported what can i do
the version of NVDA I use is marked below I have marked and I also use
the Windows bar braille the braille bar has no functional problems I
just do not know how to synchronize it with the program NVDA question 2
you can write to me anyone who knows a store that has things for
computers and mobile phones like selling braille bars if there is no
possibility at least to look for a new newer and more modern braille bar
Where can I use it with computer and android phone if you have in mind
if you know a store Please send me a link thank you
I MARINOS
have Windows 7 service pack 1 32 bit.
NVDA
20,19,2,1
Braille Bar.
Optelec Alva 544.







--
Quentin Christensen
Training and Support Manager


Re: silencing certain reading of tables in NVDA

Andre Fisher
 

Again, this is where configuration profiles would come in handy. You could have this on for Excel, but off for your web browser.


Re: silencing certain reading of tables in NVDA

Louise Pfau
 

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


Re: Navigating A Web Page

Sascha Cowley
 

Use the "Maybe later" button.

On 2021-01-28 06:53, Hicks Steven (CORNWALL IT SERVICES) via groups.io wrote:

How did you close the dialog?

 

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Sascha Cowley via groups.io
Sent: 22 January 2021 22:59
To: nvda@nvda.groups.io
Subject: Re: [nvda] Navigating A Web Page

 

I was able to get the button to activate just fine by pressing space or enter on it in browse mode.

It did not work at first because there was a modal covering it. If you jump to the top of the page, there is a dialog prompting you to create an account or login. Either do that, or close the dialog and the play button should work.

 

 

This message originated from outside of NHSmail. Please do not click links or open attachments unless you recognise the sender and know the content is safe.

 



********************************************************************************************************************

This message may contain confidential information. If you are not the intended recipient please inform the
sender that you have received the message in error before deleting it.
Please do not disclose, copy or distribute information in this e-mail or take any action in relation to its contents. To do so is strictly prohibited and may be unlawful. Thank you for your co-operation.

NHSmail is the secure email and directory service available for all NHS staff in England and Scotland. NHSmail is approved for exchanging patient data and other sensitive information with NHSmail and other accredited email services.

For more information and to find out how you can switch, https://portal.nhs.net/help/joiningnhsmail


Re: Firefox Notifications

Sascha Cowley
 

Use F6 and Shift+F6 to cycle through the various browser areas, including the notifications.


Re: Navigating A Web Page

Hicks Steven (CORNWALL IT SERVICES) <steven.hicks@...>
 

How did you close the dialog?

 

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Sascha Cowley via groups.io
Sent: 22 January 2021 22:59
To: nvda@nvda.groups.io
Subject: Re: [nvda] Navigating A Web Page

 

I was able to get the button to activate just fine by pressing space or enter on it in browse mode.

It did not work at first because there was a modal covering it. If you jump to the top of the page, there is a dialog prompting you to create an account or login. Either do that, or close the dialog and the play button should work.

 

 

This message originated from outside of NHSmail. Please do not click links or open attachments unless you recognise the sender and know the content is safe.

 



********************************************************************************************************************

This message may contain confidential information. If you are not the intended recipient please inform the
sender that you have received the message in error before deleting it.
Please do not disclose, copy or distribute information in this e-mail or take any action in relation to its contents. To do so is strictly prohibited and may be unlawful. Thank you for your co-operation.

NHSmail is the secure email and directory service available for all NHS staff in England and Scotland. NHSmail is approved for exchanging patient data and other sensitive information with NHSmail and other accredited email services.

For more information and to find out how you can switch, https://portal.nhs.net/help/joiningnhsmail


Re: user account won't speek in nvda

 

hi.
make sure that in nvda general settings, these items be checked.
Automatically start NVDA after I log on to Windows
Use NVDA on the Windows logon screen (requires administrator privileges)
Use currently saved settings on the logon and other secure screens
(requires administrator privileges)

On 1/27/21, Bobby Vinton <vinton.bobby5277@gmail.com> wrote:
Just to let you know I had to install nvda from scratch and when I was
on the log on screen nvda would not speek and also user account won't
speek at all and every thing is at all defaults. I am wondering what
could be causing this.






--
By God,
were I given all the seven heavens
with all they contain
in order that
I may disobey God
by depriving an ant
from the husk of a grain of barley,
I would not do it.
imam ali

9081 - 9100 of 90214