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

Improve Accessibility #230

Open
12 tasks
rashfael opened this issue May 2, 2021 · 0 comments
Open
12 tasks

Improve Accessibility #230

rashfael opened this issue May 2, 2021 · 0 comments

Comments

@rashfael
Copy link
Contributor

rashfael commented May 2, 2021

Currently venueless is barely to not accessible, which is obviously big time bad.
Here follows an attempt to find and break apart problems and propose solutions.

Let's divide the broad target of "accessibility" into something more concrete:

Keyboard Navigation Accessibility

Make venueless controlable with ONLY keyboard
This also greatly benefits screen reader users, so I won't list things twice.

  • trap focus inside dialogs
  • things that show on mouseover should show on focus (like video controls)
  • make rooms sidebar arrow key navigable and use tab for bigger regions
  • make chat log keyboard/arrow key navigable
  • add keyboard shortcuts for quick nav (and advertise them like slack does)
  • highlight focused elements properly

Screen Reader Accessibility

Make venueless readable and interactable with a screen reader

  • give every interactive element aria-labels or equivalent information
  • hide decorative elements (icons, user avatars when username is present)
  • Users should get through the greeting dialog (aria-modal enough?)
  • Define enough landmark roles for users to navigate around (already partially added)
  • handle live content like chat (how do deal with the conflict of "running video" and "new chat content")
  • how to handle the background room, announce the transition?

What is okay to not show screen readers? Is the reaction cloud relevant information? If yes, how would we show that to a screen reader? We probably cannot announce the new reactions every 10 seconds.

Misc

some general accessibility issues which don't fit into the big stories above

  • color contrast (we already do that for static things, but customers can choose bad theme colors, and we should warn them when they set badly contrasting colors)

I'm happy to add more points and am honestly desperate for opinions, since the standards are not really forthcoming with guidelines for highly dynamic apps like venuess. My current plan is: Get inspired by Slack/Discord (which use different ARIA stuff) and perhaps Youtube and some others and test things out with NVDA to the best of my ability.

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

No branches or pull requests

1 participant