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

Diagrams that produced bythis lib is not accessible for screen reader users (blind and visually impaired) #634

Closed
hamidrezaabroshan opened this issue Apr 16, 2022 · 2 comments
Labels
bug Something isn't working duplicate This issue or pull request already exists

Comments

@hamidrezaabroshan
Copy link

I'm a blind java developer and using Nvda screen reader to work with computer.
The diagrams that produced by this module is not accessible for screen readers E.G, by navigating the diagram, Screen reader only reads the diagram like a textual component or reads nothing at all.
Its because accessibility information not provided.
As this module is used for displaying bpmn files in bpmn modoler apps such as camunda modeler, it effects on my job as a developer.
You can provide accessibility info in canvas by using ARIA tag and alt text.
see accessibility in canvas and
accessibility in svg
and you can download free and open source screen reader nvda for testing accessibility.
The keywords are accessibility and screen readers.
I'm up for any help as much as I can.

Steps to reproduce the behavior:

  1. download and run Nvda screen reader.
  2. open a diagram.
  3. try to understand the diagram by navigating with arrow keys and tab.

Expected Behavior

  1. First, the diagram should be navigable by arrow keys or some shortcuts.
  2. the diagram details should be provided as accessibility info.
    Environment
  • Browser: firefox 99.
  • OS: windows 10
  • Library version: unknown.
@hamidrezaabroshan hamidrezaabroshan added the bug Something isn't working label Apr 16, 2022
@pinussilvestrus
Copy link
Contributor

Hello @hamidrezaabroshan, thank you very much for opening this issue and providing some details! That's pretty helpful to understand the full use case.

We already have an open issue to track this problem: #567. I think the requirements in that issue are already covering the ones that you are mentioning. Therefore, I would close this issue here as a duplicate to focus the discussions and investigations in a single place.

If there is anything else that needs to be considered, feel free to add 👍

@hamidrezaabroshan
Copy link
Author

Hi @pinussilvestrus,
That's ok.
Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working duplicate This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

2 participants