We recently conducted user testing on one of our websites and encountered an issue that appears to affect the accessibility of the select component. During form navigation, some test users utilized the 'tab' key to move from one element to another. However, when they attempted to select their address from the Lob autocomplete, they were unable to tab to the address option they wanted to use. Instead, they were redirected from our site to the Lob website. (See gif below)
After researching the code-base, I found intentional window location changes. Is there any way to prevent redirection? The redirect happens within the handleChange function which is used in the onChange event.
Based on the comments, it seems that the onChange event is intentionally defined after the user has supplied properties to avoid any unintended damage to the functionality. Is there a way to configure the component so that users can select their address using their keyboard?

We recently conducted user testing on one of our websites and encountered an issue that appears to affect the accessibility of the select component. During form navigation, some test users utilized the 'tab' key to move from one element to another. However, when they attempted to select their address from the Lob autocomplete, they were unable to tab to the address option they wanted to use. Instead, they were redirected from our site to the Lob website. (See gif below)
After researching the code-base, I found intentional window location changes. Is there any way to prevent redirection? The redirect happens within the
handleChangefunction which is used in theonChangeevent.Based on the comments, it seems that the onChange event is intentionally defined after the user has supplied properties to avoid any unintended damage to the functionality. Is there a way to configure the component so that users can select their address using their keyboard?