The fact JAWS does not indicate that prompt at the launch of VS2022 for the
first time does not in itself indicate a problem. It is my understanding that
JAWS stopped giving that prompt on the first launch of VS in the last couple
(few) version of JAWS, and starting with VS2019. So I am surprised you said you
use to get that prompt for VS2019, unless it was an older version of JAWS.
Other than that, I too suggest the uninstall and reinstallation of JAWS if the
test of running JAWS in default mode does not work.
HTH.\
Rodney
Rodney Haynie
Senior Software Engineer
INFOMC, Inc.
101 West Elm Street, Suite G10, Conshohocken, PA 19428
W: 484.567.0620 | C: 610.574.5212
www.infomc.com<http://www.infomc.com/>
[Image result for twitter icon]<https://twitter.com/InfoMCInc>[Image result for
linkedin icon]<https://www.linkedin.com/company-beta/33977/>
From: program-l-bounce@xxxxxxxxxxxxx <program-l-bounce@xxxxxxxxxxxxx> On Behalf
Of Castellanos, Gabe
Sent: Tuesday, January 25, 2022 2:30 PM
To: program-l@xxxxxxxxxxxxx
Subject: [External] [program-l] Re: Jaws not speaking VS 2022 windows
This email was not sent from InfoMC.
Hi Dante,
One question I have is, in the past when I first opened visual studio 2019
atleast, jaws would say something like "Jaws is making one time modifications
to allow jaws to read inside of visual studio windows" in this case I haven't
heard jaws say that. Are you aware of those modifications? And / or why I may
not have heard it this install?
Visual studio was installed through a company owned deployment manager, so I am
also wondering if they may have locked VS down from being changed?
Not really sure... just throwing ideas out.
-Gabe
From: program-l-bounce@xxxxxxxxxxxxx<mailto:program-l-bounce@xxxxxxxxxxxxx>
<program-l-bounce@xxxxxxxxxxxxx<mailto:program-l-bounce@xxxxxxxxxxxxx>> On
Behalf Of Dante Gagne
Sent: Tuesday, January 25, 2022 1:22 PM
To: program-l@xxxxxxxxxxxxx<mailto:program-l@xxxxxxxxxxxxx>
Subject: [program-l] Re: Jaws not speaking VS 2022 windows
CAUTION: This email originated from outside of Crowe. Do not click links, open
attachments or forward unless you recognize the sender and know the content is
safe.
This is news to me... and if JAWS stopped working on VS 2022, I'd hope that I'd
be hearing about it pretty quickly. I'll let the folks who know JAWS better
help you debug, but if there's anything I can do on the VS side, I'll monitor.
-D
From: program-l-bounce@xxxxxxxxxxxxx<mailto:program-l-bounce@xxxxxxxxxxxxx>
<program-l-bounce@xxxxxxxxxxxxx<mailto:program-l-bounce@xxxxxxxxxxxxx>> On
Behalf Of Castellanos, Gabe
Sent: Tuesday, January 25, 2022 9:24 AM
To: program-l@xxxxxxxxxxxxx<mailto:program-l@xxxxxxxxxxxxx>
Subject: [program-l] Jaws not speaking VS 2022 windows
You don't often get email from
gabe.castellanos@xxxxxxxxx<mailto:gabe.castellanos@xxxxxxxxx>. Learn why this
is important<http://aka.ms/LearnAboutSenderIdentification>
Hi all,
I just received a new work laptop with the latest version of Jaws installed (
2022) and nvda 2021.3.1 and I have visual studio 2022 professional installed.
Jaws wont speak anything when I have VS 2022 opened. I screen shared with a
coworker and he could see my cursor tabbing through the window, but I didn't
receive any feedback from jaws.
When trying vs 2022 NVDA does read out the cursor and window.
I tried to OCR the vs 2022 window with jaws, and that also didn't give me any
feedback. Which leads me to think its something with the jaws configuration
perhaps?
Has anyone else ran into this issue and / or have any ideas as to further
troubleshooting the issue?
Thanks for your help
-Gabe
This email message is from Crowe LLP or one of its subsidiaries and may contain
privileged or confidential information or other information exempt from
disclosure under applicable law. If you are not the intended recipient, please
notify the sender by reply email immediately and delete this message without
reading further or forwarding to others. This email is not intended to be a
contract or other legally binding obligation, and any tax advice expressed in
this email should not be construed as a formal tax opinion unless expressly
stated. Visit
www.crowe.com/disclosure<https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.crowe.com%2Fdisclosure&data=04%7C01%7Cgabe.castellanos%40crowe.com%7C344a2c461e384cca1e1608d9e02f9297%7C6ff60d36925f4785a854510f909ee561%7C0%7C0%7C637787317209456040%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=UkYXmXPg9DbTPBHOTg%2FX2Y7UmykSIQNsQf7%2BT4bgyKQ%3D&reserved=0>
for more information about Crowe LLP and its subsidiaries.
This email message is from Crowe LLP or one of its subsidiaries and may contain
privileged or confidential information or other information exempt from
disclosure under applicable law. If you are not the intended recipient, please
notify the sender by reply email immediately and delete this message without
reading further or forwarding to others. This email is not intended to be a
contract or other legally binding obligation, and any tax advice expressed in
this email should not be construed as a formal tax opinion unless expressly
stated. Visit www.crowe.com/disclosure<http://www.crowe.com/disclosure> for
more information about Crowe LLP and its subsidiaries.