This is an [access-S2 issue](https://wiki.mozilla.org/Accessibility/Triage) that makes parts of the UI, especially the navigation inaccessible for users of assistive technologies to use. While the current implementation is not fully blocking most of a11y customers from using the feature, the issue is marked as `access-S2` because it does create barriers for many groups of users, especially those keyboard-only users who are new to relying on the keyboard input only, for users of switch devices and other alternative inputs. While this keyboard trap can be exited by the reverse navigation, it is not something that is expected to happen (it is a workaround) and some less experienced users or users with cognitive disabilities may not be aware of. As Ania pointed out in the comment above, these appear to be accessibility issues on the side of the chatbot service providers. Firefox team will need to pass this information to the provider, but until it is resolved, we could mark this bug as `stalled`.
Bug 1905305 Comment 2 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
This is an [access-S2 issue](https://wiki.mozilla.org/Accessibility/Triage) that makes parts of the UI, especially the navigation inaccessible for users of assistive technologies to use. While the current implementation is not fully blocking most of a11y customers from using the feature, the issue is marked as `access-S2` because it does create barriers for many groups of users, especially those keyboard-only users who are new to relying on the keyboard input only, for users of switch devices and other alternative inputs. While this keyboard trap can be exited by the reverse navigation, it is not something that is expected to happen (it is a workaround) and some less experienced users or users with cognitive disabilities may not be aware of. As Ania pointed out in the comment above, this appear to be an accessibility issue on the side of the chatbot service. Firefox team will need to pass this information to the provider, but until it is resolved, we could mark this bug as `stalled`.
This is an [access-S2 issue](https://wiki.mozilla.org/Accessibility/Triage) that makes parts of the UI, especially the navigation inaccessible for users of assistive technologies to use. While the current implementation is not fully blocking most of a11y customers from using the feature, the issue is marked as `access-S2` because it does create barriers for many groups of users, especially those keyboard-only users who are new to relying on the keyboard input only, for users of switch devices and other alternative inputs. While this *keyboard trap* can be exited by the reverse navigation, it is not something that is expected to happen (it is a workaround) and some less experienced users or users with cognitive disabilities may not be aware of. This trap is also appearing in the middle of the menu list, thus it is less likely that a user would expect any bad focus management too (as it may be the cause of the bug 1905327 that has a lower a11y severity). As Ania pointed out in the comment above, this appear to be an accessibility issue on the side of the chatbot service. Firefox team will need to pass this information to the provider, but until it is resolved, we could mark this bug as `stalled`.