You can also use the Window classes dialog, insert+7 if you're using JAWS to
reclass the controls JAWS thinks are buttons to check boxes, if that's your
thing.
----- Original Message -----
From: Zachary Kline
To: bvipilots@xxxxxxxxxxxxx
Sent: Thursday, March 16, 2017 8:17 PM
Subject: [bvipilots] Re: FSX, Questions about the Settings UI
Al,
I can speak to at least a couple of these points.
The checkboxes are weird. Basically, Window-Eyes can see them as checkboxes,
but no other screen reader can, as far as I’m aware. I have no idea why this
should be the case.
THe sliders always read at zero if you tab to them, but if you use NVDA
object navigation to explore the UI you can actually figure out the real
values. Just because it says zero doesn’t mean it actually is at zero.
Saving settings should be automatic. I have no idea why they aren’t sticking
for you. I *think* they might be saved on a per-flight basis, but don’t quote
me on that.
Best,
Zack.
On Mar 16, 2017, at 7:14 PM, Puzzuoli, Al <alpuzz@xxxxxxx> wrote:
Hi guys,
I still have some questions about the FSX interface. In settings, there are
some buttons which are toggles. It seems they should really have been coded as
check boxes; but alas, they’re not. Are there any tricks for determining the
state of these buttons with a screen reader?
Under sound, I see that you can adjust volume for various categories. So
for example, if I want to adjust volume for the engines, it looks like the
value is initially set at 0. If I down arrow, NVDA starts reading higher
numeric values, but does that actually increase or decrease the volume?
Normally, I would just play with it and find out, but that leads me to my last
question: What’s the recommended method for saving settings? It seems like any
changes I make are effective for the duration of the current FSX session, but
are gone the next time I restart the app. I see I can save setting files. Am I
supposed to save settings under a certain name to insure they are loaded by
default at startup?
Thanks,
Al
