toggle quoted message
Show quoted text
What about the thing with the start menu not reading with JAWS but reading with Narrator.
On 01/07/2023 11:45 AM TJ McElroy gMail <mcelroy.tj@...> wrote:
When accessing the setting menu using
windows + i
option, a search box first appears.
I rarely use the search box, instead if you tab once, you will be in a list view.
You may be able to change the list view, however if you do not change it, you can cursor left and right, up and down selecting different options, similar to when in the control panel.
When you find the option you want, hit enter on it, then tab to select the different settings.
#caveat: once you hit enter on a selected option, some options have a selection list that you can refine or choose different options.
navigate this list by cursoring up and down then once on your selected option, hit enter, then tab to choose other options.
an example would be choosing personalization options from the main list view.
this will bring up a list view to cursor up and down on to refine your personalization option,
hit enter on your choice then tab to choose your chosen option,
once you have tabbed to an option, hit enter and you have selected that option
again, it is similar to the control panel. I am not saying it is better,, but it is usable.
On 1/7/2023 2:20 PM, Annabelle Susan Morison wrote:
By the way, I know somebody named TJ. He was a classmate of mine in Audio Engineering back in 2009 at Lane Community College in Eugene, Oregon. I use both of those commands you mentioned. JAWS reads the Control Panel just fine, but it's the new fangled Settings window that JAWS can't seem to read. Why did Microsoft have to switch out the Control Panel for something that JAWS can't read? Same thing with the Start Menu.
How are you accessing the setting options?
For instance, I usually use the:
windows key + I
to access the settings options, however I still use the control panel every now and then.
On 1/6/2023 4:25 PM, Annabelle Susan Morison wrote:
It was reading them fine before Windows started updating.
Regardless of these issues, you really need to let Windows 10 update. Any version of Windows that is under Windows as a Service, that is 10 and 11 for sure, must be allowed to update.
The 22H2 feature update was quite trivial. While it may have triggered a latent problem, it almost certainly didn't cause it, and your having done a "nuke and pave" by clean reinstalling Windows 10 means it's an ideal time to update with the cleanest baseline possible.
Brian - Virginia, USA - Windows 11 Pro, 64-Bit, Version 22H2, Build 22621; Office 2016, Version 16.0.15726.20188, 32-bit; Android 12 (MIUI 13)
It’s not lack of contact with the world off campus that leads to the liberal views common in academia — it’s being trained to think critically and practicing this craft daily as we look at the world around us that makes us the libs conservatives so dislike.
~ Eliot A. Brenowitz, Seattle; New York Times, Letters, Tales of Town and Gown: Is the Campus Isolated?, August 20, 2022