Hi Jaipal Negi, the problem is that each of your text field has a "Selected" state and is therefore identified as a button by a screen reader. You need to remove the selected state, as it is not necessary.
The user should not be tabbing through text fields, they should only be tabbing to interactive elements (buttons, form controls etc). Text content is navigated using the arrow keys on the keyboard (and various other shortcuts) when using a screen reader (since Jan 2020 update) .
Since January this year, the published output from Storyline now behaves more inline with web standards, meaning that text content can now be read by screen readers without using a tab key to navigate to it. Screen readers now have finer control over the text content since Applications Mode has been removed.
With this being the case, your shortcut keys for navigating slides are conflicting with screen readers. The arrow keys are used to navigate text content. You will need to find a different key combination for slide navigation so that it doesn't conflict with the screen reader.
1 Reply
Hi Jaipal Negi, the problem is that each of your text field has a "Selected" state and is therefore identified as a button by a screen reader. You need to remove the selected state, as it is not necessary.
The user should not be tabbing through text fields, they should only be tabbing to interactive elements (buttons, form controls etc). Text content is navigated using the arrow keys on the keyboard (and various other shortcuts) when using a screen reader (since Jan 2020 update) .
Since January this year, the published output from Storyline now behaves more inline with web standards, meaning that text content can now be read by screen readers without using a tab key to navigate to it. Screen readers now have finer control over the text content since Applications Mode has been removed.
With this being the case, your shortcut keys for navigating slides are conflicting with screen readers. The arrow keys are used to navigate text content. You will need to find a different key combination for slide navigation so that it doesn't conflict with the screen reader.
This discussion is closed. You can start a new discussion or contact Articulate Support.