Date   

Re: Compatibility of EnhancedPhoneticReading AddOn?

David Griffith
 

I emailed the developer several weeks ago to ask for it to be updated  in the then upcoming NVDA release but got no response at all so I suspect it has actually been abandoned.

As you say we were lucky that Rui Fontes stepped into the breach to update it.

As it essential for Hearing impaired users of NVDA like myself I strongly believe this is a case where this functionality should be incorporated into the core of NVDA to assist deaf blind users to prevent vulnerability to breakage in the future.

David Griffith

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Brian Vogel
Sent: 22 July 2021 18:05
To: nvda@nvda.groups.io
Subject: Re: [nvda] Compatibility of EnhancedPhoneticReading AddOn?

 

I'm reviving this topic for one reason only, this particular add-on is, from all appearances, entirely "home grown" as it does not appear on the Community Add-Ons page nor on the Add-Ons Compatibility Page (which includes some non-official add-ons as well).

Rui Fontes has provided a modification for compatibility with NVDA 2021.1 here:  https://www.dropbox.com/s/q75mnyttr34zjpm/EnhancedPhoneticReading_0.5a2_Gen.nvda-addon?dl=1

Anyone who might happen to know how to contact the original developer of this add-on should do so to determine whether he or she is still maintaining it, and whether he or she has any intention of doing an update to the original source for compatibility with NVDA 2021.1.  I have no idea who created or is maintaining this add-on, but responsibility for ongoing maintenance falls to them or their successor(s).
--

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

Yep.  Discipline.  Accountability.  Joy.  Fun.  Responsibility.

That's what life is about.  And in that order.

        ~ Liza Minnelli

 


Re: Compatibility of EnhancedPhoneticReading AddOn?

 

I'm reviving this topic for one reason only, this particular add-on is, from all appearances, entirely "home grown" as it does not appear on the Community Add-Ons page nor on the Add-Ons Compatibility Page (which includes some non-official add-ons as well).

Rui Fontes has provided a modification for compatibility with NVDA 2021.1 here:  https://www.dropbox.com/s/q75mnyttr34zjpm/EnhancedPhoneticReading_0.5a2_Gen.nvda-addon?dl=1

Anyone who might happen to know how to contact the original developer of this add-on should do so to determine whether he or she is still maintaining it, and whether he or she has any intention of doing an update to the original source for compatibility with NVDA 2021.1.  I have no idea who created or is maintaining this add-on, but responsibility for ongoing maintenance falls to them or their successor(s).
--

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

Yep.  Discipline.  Accountability.  Joy.  Fun.  Responsibility.

That's what life is about.  And in that order.

        ~ Liza Minnelli

 


Re: Clock and calendar Add-on for NVDA - Compatibility with NVDA 2021.1 & forward

 

On Thu, Jul 22, 2021 at 12:13 PM, zvonimir stanečić, 9a5dsz wrote:
I've pushed thecorresponding changes to the github repo, but I don't know how to release it.
-
I presume you are a member of the NVDA Add-On Development group, but if not, please join and ask there, as that's outside the scope of the NVDA Group.

It's also clear that "those that know how" haunt the above noted group.

NVDA Add-On Developers Group, AKA NVDA Add-Ons Central

This group is focused on the development of NVDA Add-Ons.  It is not an end-user support group, though end-user input to aid the development process and/or testing is welcome.

Archive: https://nvda-addons.groups.io/g/nvda-addons/topics .

 
--

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

Yep.  Discipline.  Accountability.  Joy.  Fun.  Responsibility.

That's what life is about.  And in that order.

        ~ Liza Minnelli

 


Re: Clock and calendar Add-on for NVDA - Compatibility with NVDA 2021.1 & forward

zvonimir stanečić, 9a5dsz
 

Hi,
I've pushed thecorresponding changes to the github repo, but I don't know how to release it.
Best,
Zvonimir

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of tony via groups.io
Sent: Thursday, July 22, 2021 5:51 PM
To: nvda@nvda.groups.io
Subject: [nvda] Clock and calendar Add-on for NVDA - Compatibility with NVDA 2021.1 & forward

Will be any update the add on for the Clock and calendar Add-on for NVDA

thank you


Re: Problem with having Admin Rights under UAC when using NVDA Remote

Carlos Esteban Martínez Macías
 

Sorry for my typing error, is options. Yes, is possible edit a message in groups.yo, but I don’t use the web of groups.yo many times.

Regards.

 

 

Carlos Esteban Martínez Macías.

Soporte a usuarios, comunidad de NVDA en español.

Web www.nvda.es

Experto certificado en NVDA

 

De: Carlos Esteban Martínez Macías via groups.io
Enviado: jueves, 22 de julio de 2021 11:08
Para: nvda@nvda.groups.io
Asunto: Re: [nvda] Problem with having Admin Rights under UAC when using NVDA Remote

 

Hi all.

No, NV Access say in the user guide that for copy the optioins in the scure screen, the form is press NVDA+control+g, and press de button “Use currently saved settings during sign-in and on secure screens (requires administrator privileges)”. Of course, your action is the same that NVDA make, but I don’t know if a part of the process is different when NVDA copy it.

Regards.

 

 

Carlos Esteban Martínez Macías.

Soporte a usuarios, comunidad de NVDA en español.

Web www.nvda.es

Experto certificado en NVDA

 

De: Jelal Bairamoglou
Enviado: martes, 20 de julio de 2021 23:16
Para: nvda@nvda.groups.io
Asunto: Re: [nvda] Problem with having Admin Rights under UAC when using NVDA Remote

 

 

I removed all items from the following path: %HomeDrive%\Program Files (x86)\NVDA\systemConfig
I copied all items from the following path
%AppData%\nvda
Does not work properly as with previous addon.
The problem occurred after the new upgrade: remote-2.4.nvda-addon.

On 21/7/2021 1:21 π.μ., Carlos Esteban Martínez Macías via groups.io wrote:

Hi all.

You can test disable addons, but led enabled NVDA Remote and if you want, a synth Driver and another important addon for you, copy again the options for secure screens and go back to enable all the addons for your install copy. In some cases, this is the solution for this problems, but depend of your NVDA copy.

Regards.

 

 

Carlos Esteban Martínez Macías.

Soporte a usuarios, comunidad de NVDA en español.

Web www.nvda.es

Experto certificado en NVDA

 

De: Jelal Bairamoglou
Enviado: lunes, 19 de julio de 2021 10:43
Para: nvda@nvda.groups.io
Asunto: Re: [nvda] Problem with having Admin Rights under UAC when using NVDA Remote

 

 

I have checked this for both computers and does not work.

They all worked all the problem occurred after the remote upgrade.

 

On 19/7/2021 6:43 π.μ., George McCoy wrote:

> I read, in the first iteration documentation that UaC works if both

> computers have NVDA set to speak at the logon screen. I have several

> clients whose systems are set up that way and I have no issues with UAC.

> George

>

 

 

 

 

 


--

Músico (pianista) y ayuda a usuarios ciegos y con discapacidad visual en el uso de lectores de pantalla y tecnología. Experto certificado en el lector de pantalla NVDA.

Musician (pianist) and help to the blind people and with visual disability in use of screen readers and technology. Certified expert in the screen reader NVDA.

 


--

Músico (pianista) y ayuda a usuarios ciegos y con discapacidad visual en el uso de lectores de pantalla y tecnología. Experto certificado en el lector de pantalla NVDA.

Musician (pianist) and help to the blind people and with visual disability in use of screen readers and technology. Certified expert in the screen reader NVDA.

 


--

Músico (pianista) y ayuda a usuarios ciegos y con discapacidad visual en el uso de lectores de pantalla y tecnología. Experto certificado en el lector de pantalla NVDA.

Musician (pianist) and help to the blind people and with visual disability in use of screen readers and technology. Certified expert in the screen reader NVDA.


Re: Shortcut commands stopping working in NVDA

 

On Thu, Jul 22, 2021 at 11:50 AM, Curtis Delzer wrote:
But, Gene is pointing out a behavior which has nothing to do whatever with anything truly "sticking" in the real world, but only in the electronic one.
-
Which I came to understand, and acknowledged long ago (over 18 hours ago) here:  https://nvda.groups.io/g/nvda/message/86555 

Please read through the entirety of a topic before posting any reply.  One of the reasons the group rules strongly encourage this is so that things that have already been resolved don't generate additional, and unnecessary, traffic.
 
And, yes, I will be getting more picky about this in the coming weeks and months.  All members should be entirely up to speed, preferably by using threaded/conversation view in their chosen e-mail clients, and having read the entirety of a topic's new content before responding.  It's not too much to ask.
--

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

Yep.  Discipline.  Accountability.  Joy.  Fun.  Responsibility.

That's what life is about.  And in that order.

        ~ Liza Minnelli

 


Re: Problem with having Admin Rights under UAC when using NVDA Remote

Carlos Esteban Martínez Macías
 

Hi all.

No, NV Access say in the user guide that for copy the optioins in the scure screen, the form is press NVDA+control+g, and press de button “Use currently saved settings during sign-in and on secure screens (requires administrator privileges)”. Of course, your action is the same that NVDA make, but I don’t know if a part of the process is different when NVDA copy it.

Regards.

 

 

Carlos Esteban Martínez Macías.

Soporte a usuarios, comunidad de NVDA en español.

Web www.nvda.es

Experto certificado en NVDA

 

De: Jelal Bairamoglou
Enviado: martes, 20 de julio de 2021 23:16
Para: nvda@nvda.groups.io
Asunto: Re: [nvda] Problem with having Admin Rights under UAC when using NVDA Remote

 

 

I removed all items from the following path: %HomeDrive%\Program Files (x86)\NVDA\systemConfig
I copied all items from the following path
%AppData%\nvda
Does not work properly as with previous addon.
The problem occurred after the new upgrade: remote-2.4.nvda-addon.

On 21/7/2021 1:21 π.μ., Carlos Esteban Martínez Macías via groups.io wrote:

Hi all.

You can test disable addons, but led enabled NVDA Remote and if you want, a synth Driver and another important addon for you, copy again the options for secure screens and go back to enable all the addons for your install copy. In some cases, this is the solution for this problems, but depend of your NVDA copy.

Regards.

 

 

Carlos Esteban Martínez Macías.

Soporte a usuarios, comunidad de NVDA en español.

Web www.nvda.es

Experto certificado en NVDA

 

De: Jelal Bairamoglou
Enviado: lunes, 19 de julio de 2021 10:43
Para: nvda@nvda.groups.io
Asunto: Re: [nvda] Problem with having Admin Rights under UAC when using NVDA Remote

 

 

I have checked this for both computers and does not work.

They all worked all the problem occurred after the remote upgrade.

 

On 19/7/2021 6:43 π.μ., George McCoy wrote:

> I read, in the first iteration documentation that UaC works if both

> computers have NVDA set to speak at the logon screen. I have several

> clients whose systems are set up that way and I have no issues with UAC.

> George

>

 

 

 

 

 


--

Músico (pianista) y ayuda a usuarios ciegos y con discapacidad visual en el uso de lectores de pantalla y tecnología. Experto certificado en el lector de pantalla NVDA.

Musician (pianist) and help to the blind people and with visual disability in use of screen readers and technology. Certified expert in the screen reader NVDA.

 


--

Músico (pianista) y ayuda a usuarios ciegos y con discapacidad visual en el uso de lectores de pantalla y tecnología. Experto certificado en el lector de pantalla NVDA.

Musician (pianist) and help to the blind people and with visual disability in use of screen readers and technology. Certified expert in the screen reader NVDA.


Re: Clock and calendar Add-on for NVDA - Compatibility with NVDA 2021.1 & forward

 

Tony,

The following may sound harsh and curt, but it's not intended that way.

The NVDA Add-Ons are the responsibility of their respective developers.  The NVDA Add-Ons Compatibility Page lists the present add-ons, their compatibility status, as well as contact information for the developer or developers of that given add-on.  This is what is listed there for the add-on you're inquiring about:

Clock and calendar Add-on for NVDA


The only people who could answer your question are the developers, who may or may not have already been contacted, but you should email them anyway.  When you get a reply as to whether an update is in the pipeline or not, please post that answer here.

Everyone needs to be looking at the above referenced compatibility and pursuing questions about what the intent is about compatibility with them.  After you know what the answer is, it is a real service to the user community if you post that answer here on the main NVDA group.
--

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

Yep.  Discipline.  Accountability.  Joy.  Fun.  Responsibility.

That's what life is about.  And in that order.

        ~ Liza Minnelli

 


Re: Clock and calendar Add-on for NVDA - Compatibility with NVDA 2021.1 & forward

Chris Smart
 

ask the developer of the add-on.

On 2021-07-22 11:50 a.m., tony via groups.io wrote:
Will be any update the add on for the Clock and calendar Add-on for NVDA

thank you




Clock and calendar Add-on for NVDA - Compatibility with NVDA 2021.1 & forward

tony
 

Will be any update the add on for the Clock and calendar Add-on for NVDA

thank you


Re: Shortcut commands stopping working in NVDA

Jackie
 

Pranav, I was, actually.

On 7/22/21, Curtis Delzer <curtis@calweb.com> wrote:
But, Gene is pointing out a behavior which has nothing to do whatever
with anything truly "sticking" in the real world, but only in the
electronic one. Jaws does this where it believes a given control or alt
key gets stuck in the past, where I've fixed it by pressing the added
key which jfw always indicated was stuck, when in fact, if it were
mechanically stuck I'd hear either repeats of the control key, or alt
key, or interrupted speech because my synth would be interrupted by a
real sticky mechanical action. :)
Tapping the "stuck" key usually fixed the action in JFW, I'll try and
see if it fixes NVDA, but I doubt it.


Curtis Delzer
HS
K 6 V F O
Rialto, CA

curtis@calweb.com

On 7/21/2021 4:33 PM, Brian Vogel wrote:
On Wed, Jul 21, 2021 at 06:54 PM, Gene wrote:

If it turns out to be keys getting stuck, that may lead to a
solution.

-
Gene,

Before I say what I'm about to say, I want to preface it with this
contribution is greatly appreciated, at least by me.  This is a great
diagnostic to undertake.

With that being said, if the root cause were traced to literal sticky
keys, the solution is getting a new keyboard.  There is nothing that the
developers of NVDA could or should do about sticking keyboard keys.
--

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

Yep.  Discipline.  Accountability.  Joy.  Fun.  Responsibility.

That's what life is about.  And in that order.

        ~ Liza Minnelli





--
Subscribe to a WordPress for Newbies Mailing List by sending a message to:
wp4newbs-request@freelists.org with 'subscribe' in the Subject field OR by
visiting the list page at http://www.freelists.org/list/wp4newbs
& check out my sites at www.brightstarsweb.com & www.mysitesbeenhacked.com


Re: Update appears to have broken Musescore accessibility with NVDA

Jujube
 

Oh wow I will have to check that. I also use Musescore a bit but I
have not opened it as of late. I know NVDA has some of the best
support for Musescore and I have to admit that it was certainly a
factor in choosing it as my main screen reader so yeah...

On 7/22/21, Christopher Bartlett <themusicalbrewer@gmail.com> wrote:
This may not affect a lot of people, but I went to edit a musical score
this morning, and I had lost access to most of my controls. I know that
the Musescore folk have been doing a lot of accessibility-focused work, so
I was a little surprised. I'll also be reporting this on their forums.
(fora?)

Christopher Bartlett
p.s. Example, when attempting to edit a tempo marking, a dialogue is
supposed to appear, allowing you to change the BPM, and the note length
that forms the beat. After updating to 2021.1, that dialogue may be
visible, I don't know, but NVDA doesn't appear to see it, either in normal
mode, nor even as an object in object navigation mode.


--
Christopher Bartlett






Re: Shortcut commands stopping working in NVDA

Curtis Delzer
 

But, Gene is pointing out a behavior which has nothing to do whatever with anything truly "sticking" in the real world, but only in the electronic one. Jaws does this where it believes a given control or alt key gets stuck in the past, where I've fixed it by pressing the added key which jfw always indicated was stuck, when in fact, if it were mechanically stuck I'd hear either repeats of the control key, or alt key, or interrupted speech because my synth would be interrupted by a real sticky mechanical action. :)
Tapping the "stuck" key usually fixed the action in JFW, I'll try and see if it fixes NVDA, but I doubt it.


Curtis Delzer
HS
K 6 V F O
Rialto, CA

curtis@calweb.com

On 7/21/2021 4:33 PM, Brian Vogel wrote:
On Wed, Jul 21, 2021 at 06:54 PM, Gene wrote:
If it turns out to be keys getting stuck, that may lead to a solution.
-
Gene,
Before I say what I'm about to say, I want to preface it with this contribution is greatly appreciated, at least by me.  This is a great diagnostic to undertake.
With that being said, if the root cause were traced to literal sticky keys, the solution is getting a new keyboard.  There is nothing that the developers of NVDA could or should do about sticking keyboard keys.
--
Brian -Windows 10, 64-Bit, Version 21H1, Build 19043
Yep.  Discipline.  Accountability.  Joy.  Fun.  Responsibility.
That's what life is about.  And in that order.
        ~ Liza Minnelli


Re: Update appears to have broken Musescore accessibility with NVDA

umut korkmaz
 

Hi Christopher,

I sent you information in the first two messages.

I am using nvda latest version and musescore latest version. I don't have the problems you describe.

Regards,

Umut KORKMAZ

 

Windows 10 için Posta ile gönderildi

 

Kimden: Christopher Bartlett
Gönderilme: 22 Temmuz 2021 Perşembe 18:33
Kime: nvda@nvda.groups.io
Konu: [nvda] Update appears to have broken Musescore accessibility with NVDA

 

This may not affect a lot of people, but I went to edit a musical score this morning, and I had lost access to most of my controls.  I know that the Musescore folk have been doing a lot of accessibility-focused work, so I was a little surprised.  I'll also be reporting this on their forums.  (fora?)

 

Christopher Bartlett

p.s.  Example, when attempting to edit a tempo marking, a dialogue is supposed to appear, allowing you to change the BPM, and the note length that forms the beat.  After updating to 2021.1, that dialogue may be visible, I don't know, but NVDA doesn't appear to see it, either in normal mode, nor even as an object in object navigation mode.


 

--

Christopher Bartlett

 


Re: Update appears to have broken Musescore accessibility with NVDA

umut korkmaz
 

You can specify the Tempo (BPM) value of our work in the New score wizard at first; If we want, we can add it to the size of our work later.

Now let's first add the New tempo value to our work:

In our example, let's assume that the first 8 measures have a tempo value of 120, and from the 9th measure a value of 75 tempo.

We make sure that we are at the beginning of the first measure by using the Right and Left arrow keys in normal or note writing mode. We can also make sure that we are in the first dimension by opening the search field with CTRL+F and typing 1 and pressing enter.

By pressing ALT+Shift+T, we come to the Tempo writing area.

We find the number 80 after the equal sign with the right arrow and delete it with the del key, and write our new value, the value 120 in our example. and exit with the escape key.

When we switch to note-writing mode with the N key and hover over the first measure:

Pause Measure Measure 1 Beat 1 Tempo Quarter note (crotchet) stem up = 120

NVDA will voice the phrase to us and we'll make sure our value is added.

Again, regardless of the mode, come to the beginning of the 9th measure and open the tempo writing area with ALT+Shift+T; By deleting the digits after the equals, we enter the value 75 this time and exit with the escape key.

When we switch to the note-writing mode with N and come to the beginning of the 9th measure; NVDA tells us this time:

Pause Measure Measure 9 Beat 1 Tempo Quarter note (crotchet) stem up = 75

and we will make sure that the transaction is successful.

In this case: The first eight measures will play at 120 BPM, and the 9th measure and beyond will play at a tempo of 75 BPM.

If we wish, we can add the tempo values ​​by coming to the beginning of the measures we want after we have written our piece, or we can add the tempo values ​​to the beginning of the measures we want first, and then write our note.

We do not need to press enter after opening the typing area with ALT+Shift+T and typing the value.

After typing the value, we may need to press the escape key more than once.

 

Windows 10 için Posta ile gönderildi

 

Kimden: Christopher Bartlett
Gönderilme: 22 Temmuz 2021 Perşembe 18:33
Kime: nvda@nvda.groups.io
Konu: [nvda] Update appears to have broken Musescore accessibility with NVDA

 

This may not affect a lot of people, but I went to edit a musical score this morning, and I had lost access to most of my controls.  I know that the Musescore folk have been doing a lot of accessibility-focused work, so I was a little surprised.  I'll also be reporting this on their forums.  (fora?)

 

Christopher Bartlett

p.s.  Example, when attempting to edit a tempo marking, a dialogue is supposed to appear, allowing you to change the BPM, and the note length that forms the beat.  After updating to 2021.1, that dialogue may be visible, I don't know, but NVDA doesn't appear to see it, either in normal mode, nor even as an object in object navigation mode.


 

--

Christopher Bartlett

 


Re: Shortcut commands stopping working in NVDA

Curtis Delzer
 

jaws exhibited this behavior and still does where a given control or alt key gets stuck and then if you've told jaws to say your keystrokes you'd hear the extra key when you didn't initially press it.
I will try that fix using NVDA and see if access to the NVDA commands return.

Curtis Delzer
HS
K 6 V F O
Rialto, CA

curtis@calweb.com

On 7/21/2021 3:54 PM, Gene wrote:
Occasionally, a problem where NVDA shortcut commands such as read title bar, open menus, etc. stop working has been discussed here.  I may have found out what is actually going on and it may either eliminate or almost fully eliminate the need to unload, then run NVDA again.
It appears to me that a key is getting stuck.  When this happens, try pressing the left shift key, then the right shift key quickly perhaps five or six times each.  Then see if the commands work again.
Caution: It used to be and probably still is the default that if you press either shift something like five times, it will turn on something.  I don’t recall if it is some sort of sounds Windows will make when certain keys are pressed or sticky keys.  At any rate, if you haven’t turned off this behavior, don’t press the shift five times.  Try three or four.
I’ve just been trying this recently.  I don’t have this happen enough to see if the same key, for example, one of the shift keys, or another key, such as either control, either alt, or the NVDA key, gets stuck in new occurrences or if the same key gets stuck and no others.
Experimentation by people will answer that question.
If it turns out to be keys getting stuck, that may lead to a solution.
Gene


Re: Update appears to have broken Musescore accessibility with NVDA

umut korkmaz
 

We can continue our work with a different tempo number than the one we started in a piece. Let's assume that the first 16 measures in our work are 4/4 (four quarters), and the next four measures are 9/8 (nine eights).

1. We write down our first 16 measurements.

2. When we reach the 17th measure, we press the letter n to make sure that we are in step-by-step note entry mode.

3. Press Shift+F9 to open the main palette window.

4. In the tree view, we find the option Numbers with the down arrow key.

5. Press the Shift+tab keys once, select the 9/8 procedure number from the list that comes up with the arrow keys and press the enter key.

Now, we can see that the first 16 meters of our work have the number of 4/4, and from the 17th measure, the number of 9/8.

Let's say we want to go back to the 4/4 procedure number after the 33rd measure. In this case, it will be sufficient to repeat the above operations and this time select the 4/4 option from the list and press enter.

We can also add a measure that is not in the size list.

For this:

Again, in the measurement numbers window, when you type 5 in the first writing field and 8 in the second writing field, then find the add button with the tab key and press the enter key, five octal procedure numbers are added to the list.

However, the procedure numbers added later cannot be read by NVDA yet.

 

Windows 10 için Posta ile gönderildi

 

Kimden: Christopher Bartlett
Gönderilme: 22 Temmuz 2021 Perşembe 18:33
Kime: nvda@nvda.groups.io
Konu: [nvda] Update appears to have broken Musescore accessibility with NVDA

 

This may not affect a lot of people, but I went to edit a musical score this morning, and I had lost access to most of my controls.  I know that the Musescore folk have been doing a lot of accessibility-focused work, so I was a little surprised.  I'll also be reporting this on their forums.  (fora?)

 

Christopher Bartlett

p.s.  Example, when attempting to edit a tempo marking, a dialogue is supposed to appear, allowing you to change the BPM, and the note length that forms the beat.  After updating to 2021.1, that dialogue may be visible, I don't know, but NVDA doesn't appear to see it, either in normal mode, nor even as an object in object navigation mode.


 

--

Christopher Bartlett

 


Re: Shortcut commands stopping working in NVDA

Curtis Delzer
 

happens to me also, and in my case all NVDA commands such as shutting down, 'NVDA+N, for getting into the menus, all is non responsive, so I just re-start NVDA which always fixes it.
control-alt-N is not non-responsive since it is a system command, not one internal to NVDA.

Curtis Delzer
HS
K 6 V F O
Rialto, CA

curtis@calweb.com

On 7/21/2021 4:49 PM, Don H wrote:
If this is a hardware issue why does restarting NVDA fix the issue?
On 7/21/2021 6:40 PM, Brian Vogel wrote:
On Wed, Jul 21, 2021 at 07:36 PM, Sarah k Alawami wrote:

    This is not anything new, now we need to figure out why this happens.

-
I say the following not to be snarky, but if it is actually sticking keys, we already know why this happens.

Another good thing, and dirt cheap, is to obtain a USB keyboard (and thrift stores are loaded with them, fully functional) to keep "as the testing spare" and check if the issue persists, when it occurs, on a different keyboard that's available for the machine.

If the shortcuts work immediately when you use the alternative keyboard, and consistently, you know you have a hardware issue of some sort with your primary keyboard.  While these are, relatively speaking, rare they are far from never happening.
--

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

Yep.  Discipline.  Accountability.  Joy.  Fun.  Responsibility.

That's what life is about.  And in that order.

         ~ Liza Minnelli


Update appears to have broken Musescore accessibility with NVDA

Christopher Bartlett
 

This may not affect a lot of people, but I went to edit a musical score this morning, and I had lost access to most of my controls.  I know that the Musescore folk have been doing a lot of accessibility-focused work, so I was a little surprised.  I'll also be reporting this on their forums.  (fora?)

Christopher Bartlett
p.s.  Example, when attempting to edit a tempo marking, a dialogue is supposed to appear, allowing you to change the BPM, and the note length that forms the beat.  After updating to 2021.1, that dialogue may be visible, I don't know, but NVDA doesn't appear to see it, either in normal mode, nor even as an object in object navigation mode.


--
Christopher Bartlett


Re: my request for NVDA

 

On Thu, Jul 22, 2021 at 10:02 AM, Sarah k Alawami wrote:
what is your windows build, I think you said your nvda build but I can’t remember now.
-
He mentioned Windows 10 Pro Version 21H1, which means the Build must be 19043, but it still helps to have the exact dot number on the build, too, which can be obtained via the winver command.  Most recent for home is 1110, I believe, but it sometimes can be different for Pro.  NVDA was stated as 2021.1.

But even with all that information, what we need is specific descriptions of the difficulties being encountered in the exact contexts of use, as both you and I have now noted.
--

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

Yep.  Discipline.  Accountability.  Joy.  Fun.  Responsibility.

That's what life is about.  And in that order.

        ~ Liza Minnelli

 

3581 - 3600 of 89986