The standard VoiceOver modifier is the control + option keys pressed at the same time. For using VoiceOver with steppers in order to increment or decrement the stepper VoiceOver instructs us to use control+option+up/down arrow key. On using this with the SpinButton, the VoiceOver annouces that the value is incrementing/decrementing but the actual value doesn't change.
When VoiceOver is enabled and we're currently inside the SpinButton, pressing control + option + up/down arrow key announces that stepper is incrementing/decrementing but actual value doesn't change.
When VoiceOver is enabled and we're inside the SpinButton, pressing control + option + up/down arrow key should announce that stepper is incrementing/decrementing and the actual value should change as well.
https://www.apple.com/voiceover/info/guide/_1121.html
When VoiceOver is on, you can use VoiceOver commands to navigate and interact with items on the screen. You enter VoiceOver commands by holding down the Control and Option keys together, along with one or more other keys. The Control and Option keys are called the “VoiceOver keys,” or “VO keys” for short. They are shown in commands as VO, as in VO-F1. You can assign VoiceOver commands to numeric keypad keys, keyboard keys, braille display input keys, and trackpad gestures, so you can use the commands with fewer keystrokes.
Hey @paulgildea @khmakoto do we have any updates on this? 😀 I was hoping this could be prioritized as we need accessibility sign off for a feature in OWA.
@paulgildea I don't have a Mac with which to test/address this, could you reassign to someone else?
@paulgildea any updates on this? 😀
@mnajdova Is possible to get a repo of this issue?
@paulgildea @mnajdova Do we have any updates on this?
@smhigley as FYI
@Ashwin-Nikam - if you simply press up/down arrow, the value is changing. In terms the key combo (control + option + up/down arrow) VO told to use, it's indeed not working.
@smhigley - could you advice how to address this?
@Ashwin-Nikam - I just notice this issue is happening in all the spin buttons and looks like this is a VO bug. You can repro the same issue in this simple aria example
This issue has been automatically marked as stale because it has marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment. Thank you for your contributions to Fluent UI!
Just for more information: this isn't so much a VoiceOver bug as a gap in the language/platform. Until synthetic events for assistive tech are possible to create (i.e. through the AOM https://github.com/WICG/aom/blob/gh-pages/explainer.md#user-action-events-from-assistive-technology), custom spinbuttons will not be accessible to touch screen readers.
It just isn't possible to author a spinbutton (aside from the native <input type="number">) and handle the specific events used by mobile screen readers on the web today. That's why the increment/decrement buttons are still needed, and also why custom spinbuttons are generally discouraged 😃
This issue has been automatically marked as stale because it has marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment. Thank you for your contributions to Fluent UI!
Most helpful comment
@Ashwin-Nikam - I just notice this issue is happening in all the spin buttons and looks like this is a VO bug. You can repro the same issue in this simple aria example