Bring your karma
Join the waitlist today
HUMBLECAT.ORG

Blind and Visually Impaired Community

Full History - 2016 - 10 - 07 - ID#56dhyk
2
JAWS 17 and Windows 10 - No text feedback during login screen, help! (self.Blind)
submitted by HaylonMc
I have a co-worker that I've been trying to assist in getting his laptop setup as best as possible here at work.

One of the problems he's experiancing is that his screen reading software, $1 will not load during startup even though I've uninstalled/installed it and checked/unchecked the box to have it load at startup.

The installer never creates a reg entry for a service to load the app at windows startup, has anyone here run into a similar issue and was able to resolve it?

There is SO little data online about JAWS and troubleshooting. I've sent an email to the support email address of the company that owns it so hopefully that will help. Just figured I'd ask here too in case anyone here has run into a similar issue.

As another fun issue, since JAWS was not starting properly to notify my co-worker of when his laptop was fully started up and waiting for his password, I figured I'd activate Narrator in the mean time. I can't even get that tool to start at login either!

Ease of Access Center -> Left hand pane, click on "Change sign-in settings" -> Hear text on screen read aloud (Narrator) At sign-in and After sign-in is checked and Narrator only starts up after login... any ideas on this one as well?

This is all new to me so any assistance in these tools would be greatly appreciated.

Thanks!

EDIT: I also thought about this question I'd like to ask blind computer users. How difficult is it to switch to another application like NVDA as opposed to JAWS which the user is used too. Is this a major disruption in usage model?
fastfinge 1 points 6y ago
Hmmm. First thing that comes to mind: does the user have admin access on the machine? Changing the narrator or JAWS settings to make them start up on the login screen should be popping up a UAC prompt requiring you to allow admin access. If it's not doing that, there might be some kind of domain policy getting in the way. Unfortunately, my only real familiarity with corporate Windows administration involves maintaining exchange servers way back in 2003, so I have no real idea how corporate deployment works these days.

As for just switching the user to NVDA: it's not that hard to learn; I switched years and years ago, and it only took me a day or two to learn the new commands. However, JAWS still works better in a few corporate applications (especially Lotus Notes and various terminal programs). Can you give me a list of the applications your user needs for his/her job? Assuming NVDA works with them all, I'd say just switch.
HaylonMc [OP] 2 points 6y ago
Thank you for your reply. I found that the problem is due to a GPO that is preventing most of the accessibility tools from launching at startup due to a security concern.

I'm now working with our security group to get that resolved for this user.
This nonprofit website is run by volunteers.
Please contribute if you can. Thank you!
Our mission is to provide everyone with access to large-
scale community websites for the good of humanity.
Without ads, without tracking, without greed.
©2023 HumbleCat Inc   •   HumbleCat is a 501(c)3 nonprofit based in Michigan, USA.