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: need HTML structure in chat window in web version #5789

Open
ssawczyn opened this issue Apr 8, 2020 · 4 comments
Open

Accessibility: need HTML structure in chat window in web version #5789

ssawczyn opened this issue Apr 8, 2020 · 4 comments
Labels
accessibility Issue related to accessibility topics/handicapped users confirmed Confirmed bug, should not go stale

Comments

@ssawczyn
Copy link

ssawczyn commented Apr 8, 2020

As a screen reader user, I want to be able to quickly navigate through chat messages. Unfortunately, because the HTML of the chat window does not contain semantic hierarchy, I cannot quickly navigate using my screen reader. Screen readers allow the user to quickly navigate content when semantic structure (headings, lists, landmark regions) is in place making the experience far more efficient for the user.

Consider:

  • Implementing chat messages as an unordered list ,UL> with an
  • containing each individual message. The LI should also contain the time stamp and sender of each message.
  • Implement headings or landmark regions to identify secants of the chat window: chat history, emojis, any other areas that would constitute a specific section of the chat UI.
@Echolon
Copy link

Echolon commented May 13, 2020

Hi,
The team is aware of accessibility. Any reports are now grouped in the pinned issue #6090.


I'm a community contributor and not directly affiliated with the Jitsi team.

@Echolon Echolon closed this as completed May 13, 2020
@missmatsuko
Copy link

@Echolon This issue is one of the ones referenced in #6090. I don't think it should be closed until it's actually addressed, then #6090 can be closed when all the referenced issues are closed. That makes more sense to me, unless someone directed you to do this?

@Echolon
Copy link

Echolon commented May 13, 2020

Will keep it open then.

But its not deleted. We are trying to condense the information to a more practical way.

@Echolon Echolon reopened this May 13, 2020
@l3d00m l3d00m added the accessibility Issue related to accessibility topics/handicapped users label May 16, 2020
@stale
Copy link

stale bot commented Aug 15, 2020

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.

@stale stale bot added the wontfix Issue won't be fixed label Aug 15, 2020
@Echolon Echolon added confirmed Confirmed bug, should not go stale and removed wontfix Issue won't be fixed labels Aug 15, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
accessibility Issue related to accessibility topics/handicapped users confirmed Confirmed bug, should not go stale
Projects
None yet
Development

No branches or pull requests

4 participants