Re: [SUSPECT URL!]Re: [nvda] Need to speed up Slow voice on Windows start-up
|
Gene
Testing using Narrator might not tell you useful
information in this case. I'm sure you can turn off Narrator's start at
bootup option if it is on, but aside from that, my point is that you can test
this problem and still have speech. Test with JAWS and then test with NVDA
or in reverse order if you wish. Or make sure you can, in fact, log in
without speech first by trying it with the screen-reader running and making sure
you know the exact procedure.
Specifics aside, my general point is that you
shouldn't test without speech unless such testing is necessary and that, if you
do so, you should be sure you know how to do necessary actions without speech,
such as in this case, log in. Or you should make sure you can run Narrator
if necessary on the login screen. In other words, something to make sure
you aren't locked out of your computer because you can't log in. When
testing something else, if you need to take a critical action without speech,
you should know exactly how.
Gene ----- Original Message -----
From: Ervin, Glenn
Sent: Monday, August 13, 2018 10:11 AM
Subject: Re: [SUSPECT URL!]Re: [nvda] Need to speed up Slow voice on
Windows start-up I would have been worried that invoking Narrator at the login screen would have left Narrator going at subsequent logins, thus causing the same problem. Glenn
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of
Gene
I'll look at the original message again. but I commented because of this passage in your original message: When I restarted I was then blind” audially! However, I took a chance and typed my password in in the usual way and got back to the desktop in silence.
This sounds as though you didn't know if you could enter your password without speech. for that reason, I tried to think of other ways to test what you were testing. At this point, without looking at the original message again, I'm not sure if my suggestion of how to test fit what you were doing. But my whole point is that if there is a way to test without losing accessibility, unless you are sure you can do something without speech, it is far better to keep accessibility if that means you may not be able to do something critical such as sign in.
Gene ----- Original Message ----- From: Cearbhall O'Meadhra Sent: Saturday, August 11, 2018 11:54 AM Subject: Re: [nvda] Need to speed up Slow voice on Windows start-up
Gene,
You are mistaken, if you read my description again, you will see that indeed both the JAWS and the NVDA settings were on. This duplication is what was being tested. The loss of accessibility was a risk, as you rightly say. However, my experience has demonstrated that there is only one edit box in the start-up screen and it was only necessary to put the password in in the usual way that it had been done before to get into the full Windows session.
This could not have been tested if the NVDA switch was left active. The silence itself was the test.
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of
Gene
The point is that the speech on bootup setting in the Ease of Access Center was turned off and the effect of that was being tested. The person booted up without speech and he said that, luckily, he was able to enter his password. What if he hadn't been able to, something he didn't know. If you trouble shoot, if you are testing something that doesn't require a loss of accessibility, you should take steps to retain accessibility. In this case, NVDA could have been told to run at boot up and nothing would have been lost in the trouble shooting that was being done.
The NVDA setting wasn't being tested, it hadn't been on. the incorrect setting for what was desired had been on in the Ease of Access Center. The desired setting could have been turned on with no loss of accessibility and no impairment of the test being done.
Gene ----- Original Message ----- From: Brian Vogel Sent: Saturday, August 11, 2018 9:57 AM Subject: Re: [nvda] Need to speed up Slow voice on Windows start-up
On Sat, Aug 11, 2018 at 08:45 AM, Gene wrote:
It strikes me that troubleshooting steps
were being described in detail, not the final and permanent state of
affairs. Brian - Windows 10 Home, 64-Bit, Version 1803, Build 17134 A little kindness from person to person is better than a vast love for all humankind. ~ Richard Dehmel
|
|
|