Date   

Re: NVDA say all command not working.

Eric Hofman
 

Hi Gene

Having Laptop keyboard layout selected does not preclude the use of Insert key as the NVDA modifier key it Just enables the use of the Caps lock key as a Modifier Key and re-assigns the key commands that are assigned to the key comprised in the Num pad as most laptops don’t have a numpad.

 

In NVDA and also JAWS if you select laptop keyboard layout even with a desktop keyboard you can then use either Insert or Caps lock as your modifier key and either the desktop or Laptop key commands, which can actually be quite helpful with some of the more acrobatic keyboard commans (where smaller hands or where dexterity is an issue.)

 

Although the laptop keyboard does have a numpad and an insert key, I choose to leave set to laptop in consultation with the user.

 

I thank you for your advise and input into this issue.

 

Kind regards

Eric  

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gene
Sent: Sunday, 13 January 2019 10:28 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA say all command not working.

 

If a numpad is present, why did you change the setting to laptop?  Laptop keyboard layout doesn't mean you have to use it with a desktop.  It is intended to be used with any keyboard with a numpad or if you have a USB numpad connected to a computer that doesn't have a numpad.  The laptop keyboard layout is intended to be used on computers without numpads and those are usually laptops, which is why it is named laptop layout.

 

Set the keyboard back to desktop layout.  If you don't, the command the person wants to use won't work or leave at desktop, if it is already there. 

Gene

----- Original Message -----

Sent: Saturday, January 12, 2019 5:30 PM

Subject: Re: [nvda] NVDA say all command not working.

 

Hi Joseph and list

On Friday I was able to re-contact my client to continue troubleshooting this issue. At that time I was able to use team viewer to remote into his system. During this contact and access to his system I was able to;

1 Establish that he is in fact using a laptop keyboard that has a Numpad.

2 NVDA setting show that desktop keyboard layout was selected now altered  to reflect Laptop keyboard.

3 He has no add-ons installed according to the add-on manager in NVDA

4 He is using Windows One core synth with Microsoft David voice.

5 Restarting NVDA with add-ons  disabled does indeed resolve the problem.

6 Resetting to NVDA to factory defaults had no impact in the issue when running NVDA normally

 

At this point the remote connection with team viewer became very laggy and un-usable and my client had to attend to other matters. So we had to abandon and will continue on Monday or Tuesday at which time I endeavour to verify NVDA and Windows version and build details.

 

I thanks everyone for their assistance an contribution to this issue thus far offer my thanks and appreciation.

 

Kind regards

Eric Hofman

 

 

 

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Joseph Lee
Sent: Thursday, 10 January 2019 12:14 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA say all command not working.

 

Hi Eric,

Is your client using any NVDA add-ons at the moment? If yes, it might be possible that a recent add-on update may have contributed to this problem. If it turns out add-ons might be to blame, have your client follow Gene’s advice of restarting NVDA with add-ons disabled and see if that makes a difference.

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Eric Hofman
Sent: Wednesday, January 9, 2019 6:12 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA say all command not working.

 

Hi Joseph

Thank you so much the warm welcome and for taking the time to assist with this issue.

  • I have confirmed with the client that they were using the “Down arrow key” as opposed to the NUMPAD “down arrow”. Unfortunately I neglected to state this in my original message, please accept my apologies for that oversight.

I confirmed they are using a desktop keyboard and believe that their NVDA config is set to desktop keyboard but I will contact and confirm this and relay your message.

 

Thank you again for your time and assistance with this issue.

 

Kind regards

Eric Hofman

 

 

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Joseph Lee
Sent: Thursday, 10 January 2019 11:57 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA say all command not working.

 

Hello Eric,

First, welcome to NVDA users list.

If you don’t mind, can you pass on the following message to your client please:

 

Hi,

This is Joseph Lee, one of the developers of NVDA screen reader.

I heard from a person you work with that say all command (NVDA+down arrow) isn’t working for you all the way. This might be caused by one or more of the following:

  • Which key you are pressing: many desktop keyboards (and some laptops) come with two arrow keys: the regular arrow keys, and the set as part of the Numpad. I’m thinking that you might be pressing the Numpad down arrow key with NVDA key, which performs a completely different action. Unless otherwise stated, when NvDA people talk about arrow keys, we usually refer to regular arrow keys.
  • Keyboard layout: NVDA comes with two keyboard layouts to suit the needs of desktop and laptop keyboard users. I’m thinking that somehow you may have switched to laptop keyboard layout. To confirm this, press Control+NVDA+K, then see what the keyboard layout is (the first combo box from keyboard settings).

 

Hope this helps.

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Eric Hofman
Sent: Wednesday, January 9, 2019 3:50 PM
To: nvda@nvda.groups.io
Subject: [nvda] NVDA say all command not working.

 

Hi All

I have a client who is using the latest version of NVDA on a Windows 10 Laptop with Office 2016.

The client is reasonably proficient with using NVDA and reports that when attempting to use the “SAY ALL” ( INSERT+DOWN ARROW ) in word, Outlook, notepad various other programs, that the command fails to read to the end of the Page or Document from the currently focused point. The client states it will usually read to the end of the line, sentence, or paragraph and that repeating the command will prompt NVDA to continue reading but again not to the end as expected.

 

This issue is reported to me as having been occurring for approximately 4 to 6 weeks, So has survived several system reboots. I have ensured via phone that the client is using the latest version and currently there are no updates available for the client.

 

I have been unable to reproduce this issue on a test system or my work system with the latest version or the previous versions of NVDA. Reset to factory defaults would be the next obvious step but I would like to know if this is a known issue or if there is some way of resolving this without a reset to defaults.

 

Any advice or assistance is greatly appreciated.

 

Regards

Eric Hofman

 

 

 

Eric Hofman
AT Helpdesk Support Officer
Commercial & National Services
Vision Australia
373 Old Cleveland Road Coorparoo QLD 4151

T: +617 3727 2230 (I: 701230)
E: Eric.Hofman@...
www.visionaustralia.org

 

The history, culture, diversity and value of all Aboriginal and Torres Strait Islander peoples are recognised, acknowledged and respected.

 


Re: Minimum Specs for NVDA with Other Intensive Applications

David Goldfield
 

I'm also running Windows 10 on a machine which I believe was first sold around 2009 running Vista. It was a refurbished machine which I bought in 2013 from Computers for the Blind which, when I purchased it, was running Windows 7. I've since upgraded it to Windows 10 and, so far, its performance, while not stellar, is acceptable and runs Windows 10 very nicely.


David Goldfield, Assistive Technology Specialist WWW.David-Goldfield.Com

On 1/12/2019 4:49 PM, Brian Vogel wrote:
Sarah,

         Although recently there's been a rather tectonic shift with regard to the relationship between Windows 10 and "old" versus "new" hardware, even now there's no hard and fast drop dead date with regard to updates, so long as the machine can still get them and meets the minimum requirements.   I've got a machine from the Vista era that was running Windows 10, and the only reason I stopped is that, for some odd reason, there was absolutely no compatible mouse pad driver to be found, and believe me I looked at the time.   I've got another that's a now at least 10 year old desktop machine that's happily sailing along with Windows 10.

         I fully expect that support for Windows 10 will be dropped from machines that run conventional BIOS as opposed to UEFI.

--

Brian - Windows 10 Home, 64-Bit, Version 1809, Build 17763  

A great deal of intelligence can be invested in ignorance when the need for illusion is deep.

          ~ Saul Bellow, To Jerusalem and Back

 

 


Re: Minimum Specs for NVDA with Other Intensive Applications

 

Well I know 4th -6th gen computers are still sold about the place and are still acceptable.

I doubt all of those will just drop.

At least none of thats going to happen while win7 and win8 and some of the older server versions still have lifecycles.

Even when those drop, 32 bit processers still exist not the latest but still.

About the time 32 bit win10 drops we may see the end to all bios units.

However not everyone will have the latest unit.



On 13/01/2019 10:49 AM, Brian Vogel wrote:
Sarah,

         Although recently there's been a rather tectonic shift with regard to the relationship between Windows 10 and "old" versus "new" hardware, even now there's no hard and fast drop dead date with regard to updates, so long as the machine can still get them and meets the minimum requirements.   I've got a machine from the Vista era that was running Windows 10, and the only reason I stopped is that, for some odd reason, there was absolutely no compatible mouse pad driver to be found, and believe me I looked at the time.   I've got another that's a now at least 10 year old desktop machine that's happily sailing along with Windows 10.

         I fully expect that support for Windows 10 will be dropped from machines that run conventional BIOS as opposed to UEFI.

--

Brian - Windows 10 Home, 64-Bit, Version 1809, Build 17763  

A great deal of intelligence can be invested in ignorance when the need for illusion is deep.

          ~ Saul Bellow, To Jerusalem and Back

 

 


Re: NVDA say all command not working.

Gene
 

If a numpad is present, why did you change the setting to laptop?  Laptop keyboard layout doesn't mean you have to use it with a desktop.  It is intended to be used with any keyboard with a numpad or if you have a USB numpad connected to a computer that doesn't have a numpad.  The laptop keyboard layout is intended to be used on computers without numpads and those are usually laptops, which is why it is named laptop layout.
 
Set the keyboard back to desktop layout.  If you don't, the command the person wants to use won't work or leave at desktop, if it is already there. 
Gene

----- Original Message -----
Sent: Saturday, January 12, 2019 5:30 PM
Subject: Re: [nvda] NVDA say all command not working.

Hi Joseph and list

On Friday I was able to re-contact my client to continue troubleshooting this issue. At that time I was able to use team viewer to remote into his system. During this contact and access to his system I was able to;

1 Establish that he is in fact using a laptop keyboard that has a Numpad.

2 NVDA setting show that desktop keyboard layout was selected now altered  to reflect Laptop keyboard.

3 He has no add-ons installed according to the add-on manager in NVDA

4 He is using Windows One core synth with Microsoft David voice.

5 Restarting NVDA with add-ons  disabled does indeed resolve the problem.

6 Resetting to NVDA to factory defaults had no impact in the issue when running NVDA normally

 

At this point the remote connection with team viewer became very laggy and un-usable and my client had to attend to other matters. So we had to abandon and will continue on Monday or Tuesday at which time I endeavour to verify NVDA and Windows version and build details.

 

I thanks everyone for their assistance an contribution to this issue thus far offer my thanks and appreciation.

 

Kind regards

Eric Hofman

 

 



 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Joseph Lee
Sent: Thursday, 10 January 2019 12:14 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA say all command not working.

 

Hi Eric,

Is your client using any NVDA add-ons at the moment? If yes, it might be possible that a recent add-on update may have contributed to this problem. If it turns out add-ons might be to blame, have your client follow Gene’s advice of restarting NVDA with add-ons disabled and see if that makes a difference.

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Eric Hofman
Sent: Wednesday, January 9, 2019 6:12 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA say all command not working.

 

Hi Joseph

Thank you so much the warm welcome and for taking the time to assist with this issue.

  • I have confirmed with the client that they were using the “Down arrow key” as opposed to the NUMPAD “down arrow”. Unfortunately I neglected to state this in my original message, please accept my apologies for that oversight.

I confirmed they are using a desktop keyboard and believe that their NVDA config is set to desktop keyboard but I will contact and confirm this and relay your message.

 

Thank you again for your time and assistance with this issue.

 

Kind regards

Eric Hofman

 

 

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Joseph Lee
Sent: Thursday, 10 January 2019 11:57 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA say all command not working.

 

Hello Eric,

First, welcome to NVDA users list.

If you don’t mind, can you pass on the following message to your client please:

 

Hi,

This is Joseph Lee, one of the developers of NVDA screen reader.

I heard from a person you work with that say all command (NVDA+down arrow) isn’t working for you all the way. This might be caused by one or more of the following:

  • Which key you are pressing: many desktop keyboards (and some laptops) come with two arrow keys: the regular arrow keys, and the set as part of the Numpad. I’m thinking that you might be pressing the Numpad down arrow key with NVDA key, which performs a completely different action. Unless otherwise stated, when NvDA people talk about arrow keys, we usually refer to regular arrow keys.
  • Keyboard layout: NVDA comes with two keyboard layouts to suit the needs of desktop and laptop keyboard users. I’m thinking that somehow you may have switched to laptop keyboard layout. To confirm this, press Control+NVDA+K, then see what the keyboard layout is (the first combo box from keyboard settings).

 

Hope this helps.

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Eric Hofman
Sent: Wednesday, January 9, 2019 3:50 PM
To: nvda@nvda.groups.io
Subject: [nvda] NVDA say all command not working.

 

Hi All

I have a client who is using the latest version of NVDA on a Windows 10 Laptop with Office 2016.

The client is reasonably proficient with using NVDA and reports that when attempting to use the “SAY ALL” ( INSERT+DOWN ARROW ) in word, Outlook, notepad various other programs, that the command fails to read to the end of the Page or Document from the currently focused point. The client states it will usually read to the end of the line, sentence, or paragraph and that repeating the command will prompt NVDA to continue reading but again not to the end as expected.

 

This issue is reported to me as having been occurring for approximately 4 to 6 weeks, So has survived several system reboots. I have ensured via phone that the client is using the latest version and currently there are no updates available for the client.

 

I have been unable to reproduce this issue on a test system or my work system with the latest version or the previous versions of NVDA. Reset to factory defaults would be the next obvious step but I would like to know if this is a known issue or if there is some way of resolving this without a reset to defaults.

 

Any advice or assistance is greatly appreciated.

 

Regards

Eric Hofman

 

 

 

Eric Hofman
AT Helpdesk Support Officer
Commercial & National Services
Vision Australia
373 Old Cleveland Road Coorparoo QLD 4151

T: +617 3727 2230 (I: 701230)
E: Eric.Hofman@...
www.visionaustralia.org

 

The history, culture, diversity and value of all Aboriginal and Torres Strait Islander peoples are recognised, acknowledged and respected.

 


Re: NVDA say all command not working.

Eric Hofman
 

Hi Joseph and list

On Friday I was able to re-contact my client to continue troubleshooting this issue. At that time I was able to use team viewer to remote into his system. During this contact and access to his system I was able to;

1 Establish that he is in fact using a laptop keyboard that has a Numpad.

2 NVDA setting show that desktop keyboard layout was selected now altered  to reflect Laptop keyboard.

3 He has no add-ons installed according to the add-on manager in NVDA

4 He is using Windows One core synth with Microsoft David voice.

5 Restarting NVDA with add-ons  disabled does indeed resolve the problem.

6 Resetting to NVDA to factory defaults had no impact in the issue when running NVDA normally

 

At this point the remote connection with team viewer became very laggy and un-usable and my client had to attend to other matters. So we had to abandon and will continue on Monday or Tuesday at which time I endeavour to verify NVDA and Windows version and build details.

 

I thanks everyone for their assistance an contribution to this issue thus far offer my thanks and appreciation.

 

Kind regards

Eric Hofman

 

 



 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Joseph Lee
Sent: Thursday, 10 January 2019 12:14 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA say all command not working.

 

Hi Eric,

Is your client using any NVDA add-ons at the moment? If yes, it might be possible that a recent add-on update may have contributed to this problem. If it turns out add-ons might be to blame, have your client follow Gene’s advice of restarting NVDA with add-ons disabled and see if that makes a difference.

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Eric Hofman
Sent: Wednesday, January 9, 2019 6:12 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA say all command not working.

 

Hi Joseph

Thank you so much the warm welcome and for taking the time to assist with this issue.

  • I have confirmed with the client that they were using the “Down arrow key” as opposed to the NUMPAD “down arrow”. Unfortunately I neglected to state this in my original message, please accept my apologies for that oversight.

I confirmed they are using a desktop keyboard and believe that their NVDA config is set to desktop keyboard but I will contact and confirm this and relay your message.

 

Thank you again for your time and assistance with this issue.

 

Kind regards

Eric Hofman

 

 

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Joseph Lee
Sent: Thursday, 10 January 2019 11:57 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA say all command not working.

 

Hello Eric,

First, welcome to NVDA users list.

If you don’t mind, can you pass on the following message to your client please:

 

Hi,

This is Joseph Lee, one of the developers of NVDA screen reader.

I heard from a person you work with that say all command (NVDA+down arrow) isn’t working for you all the way. This might be caused by one or more of the following:

  • Which key you are pressing: many desktop keyboards (and some laptops) come with two arrow keys: the regular arrow keys, and the set as part of the Numpad. I’m thinking that you might be pressing the Numpad down arrow key with NVDA key, which performs a completely different action. Unless otherwise stated, when NvDA people talk about arrow keys, we usually refer to regular arrow keys.
  • Keyboard layout: NVDA comes with two keyboard layouts to suit the needs of desktop and laptop keyboard users. I’m thinking that somehow you may have switched to laptop keyboard layout. To confirm this, press Control+NVDA+K, then see what the keyboard layout is (the first combo box from keyboard settings).

 

Hope this helps.

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Eric Hofman
Sent: Wednesday, January 9, 2019 3:50 PM
To: nvda@nvda.groups.io
Subject: [nvda] NVDA say all command not working.

 

Hi All

I have a client who is using the latest version of NVDA on a Windows 10 Laptop with Office 2016.

The client is reasonably proficient with using NVDA and reports that when attempting to use the “SAY ALL” ( INSERT+DOWN ARROW ) in word, Outlook, notepad various other programs, that the command fails to read to the end of the Page or Document from the currently focused point. The client states it will usually read to the end of the line, sentence, or paragraph and that repeating the command will prompt NVDA to continue reading but again not to the end as expected.

 

This issue is reported to me as having been occurring for approximately 4 to 6 weeks, So has survived several system reboots. I have ensured via phone that the client is using the latest version and currently there are no updates available for the client.

 

I have been unable to reproduce this issue on a test system or my work system with the latest version or the previous versions of NVDA. Reset to factory defaults would be the next obvious step but I would like to know if this is a known issue or if there is some way of resolving this without a reset to defaults.

 

Any advice or assistance is greatly appreciated.

 

Regards

Eric Hofman

 

 

 

Eric Hofman
AT Helpdesk Support Officer
Commercial & National Services
Vision Australia
373 Old Cleveland Road Coorparoo QLD 4151

T: +617 3727 2230 (I: 701230)
E: Eric.Hofman@...
www.visionaustralia.org

 

The history, culture, diversity and value of all Aboriginal and Torres Strait Islander peoples are recognised, acknowledged and respected.

 


Request for comments for people using StationPlaylist Studio add-on: should NVDA announce microphone status if NVDA restarts while Studio and microphone are in use?

 

Hi all,

 

The following is meant for users of StationPlaylist Studio add-on for NVDA. Any comments about the below proposal should be sent to me privately, via one or more social media channels, or to a dedicated NVDA SPL list (to subscribe to that list, send an email to nvda-spl+subscribe@nvda-spl.groups.io).

 

SPL Studio add-on for NVDA includes a feature to give you periodic reminder about microphone status, activated when you turn on microphone from Studio. For the most part, it works as designed except when it comes time to reset add-on settings to defaults or under some circumstances after microphone is enabled. I’m happy to announce that these issues will be resolved in an upcoming add-on release. These fixes will also become part of a project to let users revert to saved Studio add-on settings when pressing Control+NVDA+R once, or reset add-on settings to defaults if this command is pressed three times quickly (this will show up in March 2019 at the earliest).

 

While resolving microphone status announcement bugs, I realized that some of you may run into the following situation:

 

Suppose you’re broadcasting with Studio and microphone is enabled, and you ask NVDA to give you an audible warning when microphone has been active for a while and/or give you periodic status announcements. Somehow, due to an accident or as requested by add-on update installer, you restart NVDA. If this happens, when you move back to Studio window, NVDA won’t announce microphone status even if you asked NVDA to announce it after a while.

 

To resolve this, I’m thinking about letting the Studio add-on announce microphone status automatically if you restart NvDA while Studio is in use and microphone is enabled. To avoid causing problems with metadata streaming status announcement at startup, I plan to make it a beep (same beep as microphone active alarm), with an optional braille message in consideration for broadcasters using braille displays. My dilemma is where this should be done: while focused on Studio or from anywhere.

 

Questions:

 

  • Is this feature something you might find yourself using?
  • If microphone status should be announced for the above scenario, where do you think NVDA should announce this: while focusing on Studio for the first time or from anywhere?
  • Should this feature be configurable, and if yes, should this be a global setting or a profile specific setting?

 

You can send in your comments in four ways:

 

  1. Writing to me privately. Be sure to include “microphone status at startup” as part of the subject line so I can respond to the correct email.
  2. Twitter: you can either DM (direct message) me or mention me (my handle is @joslee) regarding this proposal.
  3. Facebook: you can directly message me (user name is josephsl).
  4. NVDA SPL list: there exists a dedicated list for broadcasters using Studio add-on. If you want, you can subscribe to it and stay up to date on development happenings about this add-on (subscription address is nvda-spl+subscribe@nvda-spl.groups.io).

 

I’ll accept comments until end of January so I can go over them in February, and hopefully make a decision in March. If this proposal is accepted, this will show up as part of a stable release (not long-term support version) later in 2019 (not long-term or 18.09.x release because it is about to enter bug fix only mode soon).

 

Thanks.

Cheers,

Joseph


Re: Minimum Specs for NVDA with Other Intensive Applications

Sarah k Alawami
 

Interesting, gives me a lot to chew on, that is, if I have any teeth left. Lol!

Take care

On 12 Jan 2019, at 13:49, Brian Vogel wrote:

Sarah,

         Although recently there's been a rather tectonic shift with regard to the relationship between Windows 10 and "old" versus "new" hardware, even now there's no hard and fast drop dead date with regard to updates, so long as the machine can still get them and meets the minimum requirements.   I've got a machine from the Vista era that was running Windows 10, and the only reason I stopped is that, for some odd reason, there was absolutely no compatible mouse pad driver to be found, and believe me I looked at the time.   I've got another that's a now at least 10 year old desktop machine that's happily sailing along with Windows 10.

         I fully expect that support for Windows 10 will be dropped from machines that run conventional BIOS as opposed to UEFI.

--

Brian - Windows 10 Home, 64-Bit, Version 1809, Build 17763  

A great deal of intelligence can be invested in ignorance when the need for illusion is deep.

          ~ Saul Bellow, To Jerusalem and Back

 

 


Re: Minimum Specs for NVDA with Other Intensive Applications

 

Sarah,

         Although recently there's been a rather tectonic shift with regard to the relationship between Windows 10 and "old" versus "new" hardware, even now there's no hard and fast drop dead date with regard to updates, so long as the machine can still get them and meets the minimum requirements.   I've got a machine from the Vista era that was running Windows 10, and the only reason I stopped is that, for some odd reason, there was absolutely no compatible mouse pad driver to be found, and believe me I looked at the time.   I've got another that's a now at least 10 year old desktop machine that's happily sailing along with Windows 10.

         I fully expect that support for Windows 10 will be dropped from machines that run conventional BIOS as opposed to UEFI.

--

Brian - Windows 10 Home, 64-Bit, Version 1809, Build 17763  

A great deal of intelligence can be invested in ignorance when the need for illusion is deep.

          ~ Saul Bellow, To Jerusalem and Back

 

 


Re: Minimum Specs for NVDA with Other Intensive Applications

Sarah k Alawami
 

Thanks. I'm sed to the mac where after a certain model, or 6 yers after that model is released no more software updates will be issued to that model. Nice. I'll keep this on my mental desktop.

Take care

On 12 Jan 2019, at 12:49, Brian Vogel wrote:

Sarah,

           Depending on which Windows you're looking to find information about, one, the other, or both of the below will fill the bill:

Windows Lifecycle Fact Sheet

Windows 10 Release Information
--

Brian - Windows 10 Home, 64-Bit, Version 1809, Build 17763  

A great deal of intelligence can be invested in ignorance when the need for illusion is deep.

          ~ Saul Bellow, To Jerusalem and Back

 

 


Re: Uninstall Norton Anti Virus

Kevin Cussick
 

and I can remember using this tool and not accessible with any screen reader. app remover I think got rid of it.

On 12/01/2019 16:52, David Goldfield wrote:
While I haven't ran this tool in years I believe the Kaspersky removal tool did require a captcha. I honestly don't remember why I needed to uninstall it but I think it was when I was upgrading from Windows 7 to Windows 10.
David Goldfield, Assistive Technology Specialist WWW.David-Goldfield.Com<http://WWW.David-Goldfield.Com>
On 1/12/2019 11:42 AM, Brian Vogel wrote:
On Sat, Jan 12, 2019 at 11:18 AM, Gene wrote:
But how many such removal tools require safe mode and how many require a captcha solution?
None that I am aware of require either. They're just tools that exist for use in case "the usual uninstall method" somehow does not complete successfully.
--
Brian - Windows 10 Home, 64-Bit, Version 1809, Build 17763
A great deal of intelligence can be invested in ignorance when the need for illusion is deep.
~ Saul Bellow, To Jerusalem and Back


Re: Minimum Specs for NVDA with Other Intensive Applications

 

Sarah,

           Depending on which Windows you're looking to find information about, one, the other, or both of the below will fill the bill:

Windows Lifecycle Fact Sheet

Windows 10 Release Information
--

Brian - Windows 10 Home, 64-Bit, Version 1809, Build 17763  

A great deal of intelligence can be invested in ignorance when the need for illusion is deep.

          ~ Saul Bellow, To Jerusalem and Back

 

 


Re: Minimum Specs for NVDA with Other Intensive Applications

Sarah k Alawami
 

Oh yeah. My mac which is 6 years old just got a new ssd (why that died I dunno, maybe when the battery blue up) but yeah apart from my f and j dots gone and some keys I need to bang on to get to work, the computer still runs fine. Its end of life is next year though which sucks as I love this computer. That is, no more os updates for it. By the way is there a way to find out the end of life for a windows laptop where you get no more windows updates especially if it is built by you?. My windows laptop is going to be 2 years old in June but it should still be fine for 5 ro 7 mor eyears if I treat it good, which I probably won't. Lol! Can't wait to try word on ot for when I go back to school.

Take care

On 12 Jan 2019, at 4:24, enes sarıbaş wrote:

hi,

Brian, I couldn't have said it myself. Moving to an SSD was by far the most dramatic jump in computer performance I experienced. I wouldn't go back to a mechanical hard drive if someone paid me to do it. Like Gene, when I was on  a mechanical drive, I thought the SSD performance jump was hype. SSDs always justify the cost, and I think are the part of the ocmputer that result in the most noticable jump in speed. For instance, with a hard drive, firefox took about 10-15 seconds to load. Similarly word did as well. Now any program I click on loads instantaniously. For this reason, I have no intention of replacing this PC as it feels like a newly bought pc.

On 1/11/2019 2:53 PM, Brian Vogel wrote:
On Fri, Jan 11, 2019 at 06:27 AM, Darren Harris wrote:
Ssd drives as has been said do help with loading times definitely but once the programme/application is active it all comes down to ram and CPU.
Absolutely, positively incorrect in practice.   Active programs are constantly doing disc I/O of various sorts, and more importantly, so is the operating system.  The gains in speed from an SSD versus an HDD are incredibly significant to how quick things are for the end user.

And the above is coming from someone who still has only HDDs in his computers.
 
--

Brian - Windows 10 Home, 64-Bit, Version 1809, Build 17763  

A great deal of intelligence can be invested in ignorance when the need for illusion is deep.

          ~ Saul Bellow, To Jerusalem and Back

 

 


Re: RES: [nvda] can't select radio buttons in a webpage

 

Alexandre,

          As Gene has indicated, under Chrome and on this page the only way to activate these things with a screen reader is to use screen reader mousing controls.

          By the way, and not that Gene is incorrect in any way, if you happen to have a keyboard with a "hard insert" key (as in dedicated an which only has as it's function Insert) you can use that along with the number pad slash character as well.

           If you have a laptop with a full number pad you should be able to use the desktop keystrokes as he's given them.  If you have a laptop without a number pad, and presuming the NVDA key is still INSERT, then the keystokes are:

                    Move mouse to current navigator object       INS+Shift+M
                    Left click mouse                                            INS+[
--

Brian - Windows 10 Home, 64-Bit, Version 1809, Build 17763  

A great deal of intelligence can be invested in ignorance when the need for illusion is deep.

          ~ Saul Bellow, To Jerusalem and Back

 

 


Re: RES: [nvda] can't select radio buttons in a webpage

Gene
 

Don't go into forms mode.
Move to whatever radio button you want to select in browse mode.
On the numpad, issue the command numpad insert, numpad slash.
That is, hold numpad insert and while doing so, press the slash key.  That is the key to the right of the numlock. 
Now release both keys.
Now press slash by itself again.
If you check the state of the radio button now, it will be checked.
If you don't have a numpad and are using the laptop keyboard option, someone else can give you the commands. 
 
The first command is to route the mouse to where you are.
The second command left clicks the mouse.
 
Gene

----- Original Message -----
Sent: Saturday, January 12, 2019 1:14 PM
Subject: RES: [nvda] can't select radio buttons in a webpage

Very strange. I just reboot and repeat the tests without success.

First I went to the radio button with f and press spacebar. It didn’t select.

Second I turned forms mode on with capslock + spacebar and tried to select the radio button without success too.

p.s. I know that forms mode is a jaws’s terminology. But I can’t remember how it is called in nvda... 😂  

 

Enviado do Email para Windows 10

 

De: Gene
Enviado:sábado, 12 de janeiro de 2019 16:48
Para: nvda@nvda.groups.io
Assunto: Re: [nvda] can't select radio buttons in a webpage

 

Do you know how to route and click the mouse?  You should always try that if other methods don't work.  it works here. 

 

I also tested the page with firefox and the radio buttons work correctly.

 

Gene

----- Original Message -----

Sent: Saturday, January 12, 2019 12:38 PM

Subject: [nvda] can't select radio buttons in a webpage

 

                                                               Hi friends!

Although the following page is in portuguese, if you press f you will be placed in the first group of radio buttons.

I was trying to select the button whose labe is investimentos. But I couldn’t.

I made this test in schrome.

https://internetbanking.ourinvest.com.br/Cadastro/DadosIniciais

 

 

Enviado do Email para Windows 10

 

 


RES: [nvda] can't select radio buttons in a webpage

Alexandre Alves Toco
 

Very strange. I just reboot and repeat the tests without success.

First I went to the radio button with f and press spacebar. It didn’t select.

Second I turned forms mode on with capslock + spacebar and tried to select the radio button without success too.

p.s. I know that forms mode is a jaws’s terminology. But I can’t remember how it is called in nvda... 😂  

 

Enviado do Email para Windows 10

 

De: Gene
Enviado:sábado, 12 de janeiro de 2019 16:48
Para: nvda@nvda.groups.io
Assunto: Re: [nvda] can't select radio buttons in a webpage

 

Do you know how to route and click the mouse?  You should always try that if other methods don't work.  it works here. 

 

I also tested the page with firefox and the radio buttons work correctly.

 

Gene

----- Original Message -----

Sent: Saturday, January 12, 2019 12:38 PM

Subject: [nvda] can't select radio buttons in a webpage

 

                                                               Hi friends!

Although the following page is in portuguese, if you press f you will be placed in the first group of radio buttons.

I was trying to select the button whose labe is investimentos. But I couldn’t.

I made this test in schrome.

https://internetbanking.ourinvest.com.br/Cadastro/DadosIniciais

 

 

Enviado do Email para Windows 10

 

 


Re: can't select radio buttons in a webpage

 

This is another of those instances where I'd almost like to throttle the designers of this page.

First, visually, those three radio buttons are not presented as radio buttons, but as a single bar of side-by-side buttons marked by dividers.  Then, when I listen to NVDA, it notes that this is implemented as a table on top of it all, which adds another layer of indirection depending on how the rendering engine works (and it's clearly different between Firefox and Chrome.

These could have easily been implemented and presented as a straight radio button list, which would have made more sense.  That, or make the first level of the decision tree clicking on a button for one of those three things then leading the user to what has to be filled in otherwise afterward.

This is just crappy design, period, when one web object is masked entirely as far as how either someone who sees, or someone who uses a screen reader, would recognize that it's a "pick one of these three" switch (at least in this case).  You figure that out quickly enough when you see how it behaves as you interact with it visually, but it's still a bad design choice.  People know what radio buttons are, or at least anyone who's been using the internet for more than a few weeks knows what radio buttons are.  They're an object as old as dirt, metaphorically speaking, in the world of web coding.

--

Brian - Windows 10 Home, 64-Bit, Version 1809, Build 17763  

A great deal of intelligence can be invested in ignorance when the need for illusion is deep.

          ~ Saul Bellow, To Jerusalem and Back

 

 


Re: can't select radio buttons in a webpage

Gene
 

Do you know how to route and click the mouse?  You should always try that if other methods don't work.  it works here. 
 
I also tested the page with firefox and the radio buttons work correctly.
 
Gene

----- Original Message -----
Sent: Saturday, January 12, 2019 12:38 PM
Subject: [nvda] can't select radio buttons in a webpage

                                                               Hi friends!

Although the following page is in portuguese, if you press f you will be placed in the first group of radio buttons.

I was trying to select the button whose labe is investimentos. But I couldn’t.

I made this test in schrome.

https://internetbanking.ourinvest.com.br/Cadastro/DadosIniciais

 

 

Enviado do Email para Windows 10

 


can't select radio buttons in a webpage

Alexandre Alves Toco
 

                                                               Hi friends!

Although the following page is in portuguese, if you press f you will be placed in the first group of radio buttons.

I was trying to select the button whose labe is investimentos. But I couldn’t.

I made this test in schrome.

https://internetbanking.ourinvest.com.br/Cadastro/DadosIniciais

 

 

Enviado do Email para Windows 10

 


Re: Uninstall Norton Anti Virus

David Goldfield
 

It's pretty sad when I have to go back and review one of my earlier blog posts to verify whether my memory of the captcha in the Kaspersky removal tool was correct. As of a few years ago the Kaspersky removal tool did present a captcha before it would allow me to remove Kaspersky Antivirus. Now that I reviewed my own post I now remember that I did this not due to a Windows upgrade but in order to solve a problem regarding installing a more recent version of Kaspersky Antivirus using a screen reader.


David Goldfield, Assistive Technology Specialist WWW.David-Goldfield.Com

On 1/12/2019 11:42 AM, Brian Vogel wrote:
On Sat, Jan 12, 2019 at 11:18 AM, Gene wrote:
But how many such removal tools require safe mode and how many require a captcha solution?
None that I am aware of require either.  They're just tools that exist for use in case "the usual uninstall method" somehow does not complete successfully.
 
--

Brian - Windows 10 Home, 64-Bit, Version 1809, Build 17763  

A great deal of intelligence can be invested in ignorance when the need for illusion is deep.

          ~ Saul Bellow, To Jerusalem and Back

 

 


Re: Uninstall Norton Anti Virus

David Goldfield
 

While I haven't ran this tool in years I believe the Kaspersky removal tool did require a captcha. I honestly don't remember why I needed to uninstall it but I think it was when I was upgrading from Windows 7 to Windows 10.

David Goldfield, Assistive Technology Specialist WWW.David-Goldfield.Com

On 1/12/2019 11:42 AM, Brian Vogel wrote:
On Sat, Jan 12, 2019 at 11:18 AM, Gene wrote:
But how many such removal tools require safe mode and how many require a captcha solution?
None that I am aware of require either.  They're just tools that exist for use in case "the usual uninstall method" somehow does not complete successfully.
 
--

Brian - Windows 10 Home, 64-Bit, Version 1809, Build 17763  

A great deal of intelligence can be invested in ignorance when the need for illusion is deep.

          ~ Saul Bellow, To Jerusalem and Back