Unable to move between fields using keyboard navigation after upgrading to 8.6.4
Recently upgraded from 8.2.3 to 8.6.4 and have noticed tabbing between fields no longer works the same.
I have reviewed the accessibility doc for supported keyboard navigation but this does not resolve our issue. When tabbing or using the arrow keys across a section with dynamic layouts containing text input and dropdowns, there are times when the navigation completely skips over dynamic layouts.
If the focus does manage to make it to a text box/dropdown after trying different settings, then the arrow keys no longer move back to the field the focus came from.
I have attempted using different layout formats and accessibility roles to define the structure but this does not help. Is there something we are missing with the new accessibility configurations?
https://docs-previous.pega.com/user-experience/86/supported-keyboard-navigation
***Edited by Moderator Marije to add past BUG tags***
Updated: 24 Aug 2022 5:30 EDT
Pegasystems Inc.
GB
@AndrewP there was a problem in versions before 8.6.1.
The behavior which we are seeing on Tabbing an item on RDL, it leaves the section is by design in 8.6. This change was incorporated for accessibility. You already found Supported keyboard navigation document. Navigate to Repeating dynamic layout part where it says "Tab to exit the repeating dynamic layout"
As a part of this bug, Tab navigation feature is provided in the application for RDL in 8.6.1 version. As part of BUG-657454 we provided a configuration to switch keyboard navigation to use tab key instead of Table keyboard navigation.
I believe this is the expected behavior of repeating dynamic layouts. Tabindex=" -1" is occasionally useful in complex widgets and menus that utilize arrow keys, or other shortcut keys. It can ensure that only one element within a widget, such as the active tab within a group of interactive tabs for a tab panel, or in this instance, one of multiple editable fields, is navigable with the Tab key, while still allowing focus to be set on other components within the widget.
Here is a reference article with more information pertaining to that.
@AndrewP there was a problem in versions before 8.6.1.
The behavior which we are seeing on Tabbing an item on RDL, it leaves the section is by design in 8.6. This change was incorporated for accessibility. You already found Supported keyboard navigation document. Navigate to Repeating dynamic layout part where it says "Tab to exit the repeating dynamic layout"
As a part of this bug, Tab navigation feature is provided in the application for RDL in 8.6.1 version. As part of BUG-657454 we provided a configuration to switch keyboard navigation to use tab key instead of Table keyboard navigation.
I believe this is the expected behavior of repeating dynamic layouts. Tabindex=" -1" is occasionally useful in complex widgets and menus that utilize arrow keys, or other shortcut keys. It can ensure that only one element within a widget, such as the active tab within a group of interactive tabs for a tab panel, or in this instance, one of multiple editable fields, is navigable with the Tab key, while still allowing focus to be set on other components within the widget.
Here is a reference article with more information pertaining to that.
- The TAB order is mainly decided by the order of the element in DOM structure.
- Different templates generate different DOM structure for various requirements, hence TAB key order also differs.
- The same information is mentioned on the template hover as well. Open section > click on 'Change' template > hover over templates and click on 'Learn More' > read the description as per different templates.
- Kindly try creating new template as per your requirements in order to achieve the desired tabbing order. You can refer to below link to get more information on creating design templates.
If you need further help and believe it is not working as documented please log a support incident for this and let us know the INC number so that we can help track it.