Page 1 of 1
DateGadget doesn't read when changing focused field and using screen reader
Posted: Sun Sep 01, 2024 11:03 pm
by Quin
Got an accessibility bug today...
I create a DateGadget like so:
Code: Select all
DateGadget(#DatSetDateTime, 15, 35, 210, 25, "%yyyy/%mm/%dd %hh:%ii", 0, #PB_Date_UpDown)
Have also done:
Code: Select all
DateGadget(#DatSetDateTime, 15, 35, 210, 25, "%yyyy/%mm/%dd %hh:%ii")
and
Code: Select all
DateGadget(#DatSetDateTime, 15, 35, 210, 25)
and I can hear the updated value when I use the up and down arrow keys, but I can't hear what I'm selecting with the left and right arrow keys. I just have to press up/down and hear what changed.
PB 6.11 (LTS) x64, Windows 10/11 IoT LTSC
Re: DateGadget doesn't read when changing focused field and using screen reader
Posted: Tue Sep 03, 2024 1:12 pm
by Quin
Wow, seemingly PB's DateGadget just doesn't like screen readers at all...
The reader I was using for all the tests in my first post was NVDA. I tried with Narrator, and it's...worse! Narrator doesn't read left or right arrow key presses, up/down arrow key presses or even the initial value of the field/its role when I tab to it...
Re: DateGadget doesn't read when changing focused field and using screen reader
Posted: Tue Sep 03, 2024 2:55 pm
by Fred
Re: DateGadget doesn't read when changing focused field and using screen reader
Posted: Tue Sep 03, 2024 3:54 pm
by Quin
*sighs* leave it to Microsoft to introduce a Windows control that's completely inaccessible with their own f#$king screen reader.
I wonder if anything can be done to help this? I called a few methods on a multiselect ListViewGadget from the IAccessible COM object to make it accessible in one app, wonder if we can do something similar?