This is an [access-S3 issue](https://wiki.mozilla.org/Accessibility/Triage) that does not block a user but makes it difficult to use, because visually hidden but not accessibility hidden content creates additional tab stops for keyboard-only users (with and without screen readers) and switch device users who are already require more effort to navigate the content. This makes the navigation more cumbersome than it should be. It would also be confusing for users with cognitive difficulties, because an unlabelled but focusable element may be crucial for the flow - or may not. They'd need to guess what it could do. This appear to be an accessibility issue on the side of the chatbot service. Firefox team is going to pass this information to the provider, but until it is resolved, I'm marking this bug as `stalled`.
Bug 1905703 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-S3 issue](https://wiki.mozilla.org/Accessibility/Triage) that does not block a user but makes it difficult to use, because visually hidden but not accessibility hidden content creates additional tab stops for keyboard-only users (with and without screen readers) and switch device users who are already require more effort to navigate the content. This makes the navigation more cumbersome than it should be. It would also be confusing for users with cognitive difficulties, because an unlabelled but focusable element may be crucial for the flow - or may not. They'd need to guess what it could do. This appears to be an accessibility issue on the side of the chatbot service. Firefox team is going to pass this information to the provider, but until it is resolved, I'm marking this bug as `stalled`.