You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There seems to be some inconsistency in the "Enter" key functionality of the setup wizard, where in some places, using the "Enter" key works to advance the form no matter what, and in other places, it requires using keyboard navigation and tabbing to the "continue" (or other primary button), and enter only works as expected when the element is in focus.
This should be solved by ensuring that when in the setup wizard, the enter key functions the same as a click on the primary button in all forms when not using keyboard navigation. It should work with keyboard navigation (using tab and seeing a focus outline appear) as well. When using keyboard navigation, the "enter" key should work as expected within the form element, and should not interfere with expected keyboard navigation options.
All form field validations should be triggered on the enter key, just as with a "click" on the relevant primary button.
(cc @radinamatic for any further A11y notes or guidance to add)
The text was updated successfully, but these errors were encountered:
There seems to be some inconsistency in the "Enter" key functionality of the setup wizard, where in some places, using the "Enter" key works to advance the form no matter what, and in other places, it requires using keyboard navigation and tabbing to the "continue" (or other primary button), and enter only works as expected when the element is in focus.
This should be solved by ensuring that when in the setup wizard, the enter key functions the same as a click on the primary button in all forms when not using keyboard navigation. It should work with keyboard navigation (using tab and seeing a focus outline appear) as well. When using keyboard navigation, the "enter" key should work as expected within the form element, and should not interfere with expected keyboard navigation options.
All form field validations should be triggered on the enter key, just as with a "click" on the relevant primary button.
(cc @radinamatic for any further A11y notes or guidance to add)
The text was updated successfully, but these errors were encountered: