I'm navigating SAR dialogs via keystrokes and screen reader software here on account of being a blind chap. Everything I've needed to do so far has been achievable, but the UX would be way smoother for screen reader users if the tab order for each dialog could receive a little TLC.
To reproduce the issue, load any SAR dialog and try navigating the GUI using your keyboard (Tab to jump to the next control, Shift+Tab to jump back, Space to tick boxes/click buttons). Most of the GUIs are navigable this way, but each dialog has a few gotchas. The current workarounds for these situations where controls aren't included in the tab order involve some fairly advanced screen reader jiggery-pokery to navigate the object hierarchy.
Thanks in advance if there's anything that can be done to tighten this up. If I can be of any help with testing or can provide more clarification, just shout.
Hi,
I'm navigating SAR dialogs via keystrokes and screen reader software here on account of being a blind chap. Everything I've needed to do so far has been achievable, but the UX would be way smoother for screen reader users if the tab order for each dialog could receive a little TLC.
To reproduce the issue, load any SAR dialog and try navigating the GUI using your keyboard (Tab to jump to the next control, Shift+Tab to jump back, Space to tick boxes/click buttons). Most of the GUIs are navigable this way, but each dialog has a few gotchas. The current workarounds for these situations where controls aren't included in the tab order involve some fairly advanced screen reader jiggery-pokery to navigate the object hierarchy.
Thanks in advance if there's anything that can be done to tighten this up. If I can be of any help with testing or can provide more clarification, just shout.