When a user is keyboard-navigating the MFA setup flow, if they tab to the button to select the "Okta verify" option and they hit return/enter to step into that flow, they sometimes transition to the device-type selection page and then immediately transition to the barcode-scan page. The sometimes part depends on how fast they hit enter/return. If they tap it incredibly quickly, then it's fine; you get the device type selection screen as expected. However, if they press the enter/return key for any longer than about a half-second then they skip the device-type selection screen.
Expected behavior
Any length of a keypress should transition to the device-type selection screen. Another keypress should transition the user to the barcode-scan screen.
What went wrong?
It appears that the device-type screen is just listening for a key event as soon as it renders which can be satisfied before the user even sees that page. The key event should probably just make a default radio selection if something has to happen on enter/return and then the user can just tab to the next-button.
Steps to reproduce
Log in with a user that has MFA requirements that have yet to be set up, with Okta-verifier in the included options.
Keyboard navigate through the Okta-verifier option and observe.
swiftone
commented
4 years ago
I'm submitting a
Background info
When a user is keyboard-navigating the MFA setup flow, if they tab to the button to select the "Okta verify" option and they hit return/enter to step into that flow, they sometimes transition to the device-type selection page and then immediately transition to the barcode-scan page. The sometimes part depends on how fast they hit enter/return. If they tap it incredibly quickly, then it's fine; you get the device type selection screen as expected. However, if they press the enter/return key for any longer than about a half-second then they skip the device-type selection screen.
Expected behavior
Any length of a keypress should transition to the device-type selection screen. Another keypress should transition the user to the barcode-scan screen.
What went wrong?
It appears that the device-type screen is just listening for a key event as soon as it renders which can be satisfied before the user even sees that page. The key event should probably just make a default radio selection if something has to happen on enter/return and then the user can just tab to the next-button.
Steps to reproduce
Your environment