Skip to content
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

Accessibility issues #752

Closed
3 tasks
liliakai opened this issue Apr 7, 2016 · 4 comments
Closed
3 tasks

Accessibility issues #752

liliakai opened this issue Apr 7, 2016 · 4 comments

Comments

@liliakai
Copy link
Contributor

liliakai commented Apr 7, 2016

  • Make conversation list items part of the tab order
  • Add aria-hidden on main UI when modals are open
  • Use radio button group + label on notification settings
@liliakai liliakai added this to the On the roadmap milestone Apr 7, 2016
@anselmh
Copy link

anselmh commented Apr 7, 2016

Reading of tab order issues and similar things: For a more consistent, reliable and better focus support and thus better accessibility, you might want to give http://allyjs.io/ a try. But it’s just a suggestion, feel free to ignore this if you don’t need it/if it doesn’t fit to the project. :)

@He-Ro
Copy link

He-Ro commented May 3, 2016

#512 is somewhat related. If this issue gets resolved, then #512 can also be closed.

@jwillem
Copy link

jwillem commented Mar 20, 2017

#1096 this issue should make it possible to immediately type a message after coming back from other desktop-app. It is currently prevented, when the input-field had no focus before switching to other app from signal.

@stale
Copy link

stale bot commented Sep 23, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

7 participants