-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tab ordering is broken for keyboard-accessibility tabbing around the chat view #48
Comments
##435 is also related to this. |
…riot-web Update from Weblate.
In the chat room, the tabbing which feels broken is:
|
Let me describe how I am using Element with a screen reader now, because since the original issue has been filled approx 6 years ago, it has changed a lot and today I don't see this as a huge issue personally. I apologize, this message is quite long. While describing how I use it I have also described which features have been made accessible exclusivelly as a part of the element development. Thanks for including accessibility as a part of your general UX work. |
@pvagner Thank you for taking the time to write such a detailed update on how you use accessibility features to navigate. Do you feel that this issue is now suitably resolved to be closed? |
I'm going to close this issue for now as the app has changed significantly and the ordering has been addressed as part of the changes. If anyone feels that it should still be open, please reply with @kittykat and details of what remains to be resolved. |
* Ignore effect later than 48h * Add tests for `EffectsOverlay-test.tsx`
Rm/1890 ho c part2a
(e.g. for getting focus to the text box whilst in the main page; more likely to pick a linkify link at the top of scrollback)
The text was updated successfully, but these errors were encountered: