starred/hoppscotch

Fork 0

mirror of https://github.com/hoppscotch/hoppscotch.git synced 2026-04-25 16:55:59 +03:00

[GH-ISSUE #2137] [bug]: A lot of controls are not labeled for accessibility #720

New issue

Closed

opened 2026-03-16 16:51:41 +03:00 by kerem · 6 comments

kerem commented

2026-03-16 16:51:41 +03:00

Owner

Originally created by @zersiax on GitHub (Feb 28, 2022).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/2137

Originally assigned to: @sweetkane on GitHub.

Is there an existing issue for this?

I have searched the existing issues

Current behavior

When I view hoppscotch.io with a screen reader, a lot of buttons and anchor tags on the page have no discernible text, making it impossible to figure out what these controls are for. I expect these to be properly labeled as per WCAG standards so people who don't rely on their eyesight can make use of the tool. This is easy enough to fix by just setting a textual label on these components, can even be an aria-label which only labels elements for screen readers and won't take up visual space.

Steps to reproduce

Load Narrator/VoiceOver/Orca/NVDA depending on what your OS is.
Visit hoppscotch.io.
Tab through the controls on the page. This is not how screenreader users generally navigate a page, but it will give a decent idea of just how many elements are unlabeled.

Environment

Production

Version

Cloud

Originally created by @zersiax on GitHub (Feb 28, 2022). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/2137 Originally assigned to: @sweetkane on GitHub. ### Is there an existing issue for this? - [X] I have searched the existing issues ### Current behavior When I view hoppscotch.io with a screen reader, a lot of buttons and anchor tags on the page have no discernible text, making it impossible to figure out what these controls are for. I expect these to be properly labeled as per WCAG standards so people who don't rely on their eyesight can make use of the tool. This is easy enough to fix by just setting a textual label on these components, can even be an aria-label which only labels elements for screen readers and won't take up visual space. ### Steps to reproduce 1. Load Narrator/VoiceOver/Orca/NVDA depending on what your OS is. 2. Visit hoppscotch.io. 3. Tab through the controls on the page. This is not how screenreader users generally navigate a page, but it will give a decent idea of just how many elements are unlabeled. ### Environment Production ### Version Cloud

kerem

2026-03-16 16:51:41 +03:00

closed this issue
added the
a11y
label

kerem commented

2026-03-16 16:51:57 +03:00

Author

Owner

@liyasthomas commented on GitHub (Feb 28, 2022):

Hi @zersiax, thank you for opening this issue ticket. I'll be trying our max to improve the screen reader experience and increase the overall site accessibility.

@liyasthomas commented on GitHub (Feb 28, 2022): Hi @zersiax, thank you for opening this issue ticket. I'll be trying our max to improve the screen reader experience and increase the overall site accessibility.

kerem commented

2026-03-16 16:52:02 +03:00

Author

Owner

@sweetkane commented on GitHub (Mar 22, 2022):

Hello. I am a senior studying CS at the University of Michigan. I am supposed to make an open source contribution for my Software Engineering class, and I would love to take care of this issue if it hasn't been fixed already. Could you possibly reassign it to me?

@sweetkane commented on GitHub (Mar 22, 2022): Hello. I am a senior studying CS at the University of Michigan. I am supposed to make an open source contribution for my Software Engineering class, and I would love to take care of this issue if it hasn't been fixed already. Could you possibly reassign it to me?

kerem commented

2026-03-16 16:52:07 +03:00

Author

Owner

@liyasthomas commented on GitHub (Mar 23, 2022):

Hi @sweetkane, you can pick up this issue. Assigning it to you.

@liyasthomas commented on GitHub (Mar 23, 2022): Hi @sweetkane, you can pick up this issue. Assigning it to you.

kerem commented

2026-03-16 16:52:12 +03:00

Author

Owner

@sweetkane commented on GitHub (Apr 17, 2022):

Hello. I have made changes for this issue. Can I have access to create a branch and make a pull request?

@sweetkane commented on GitHub (Apr 17, 2022): Hello. I have made changes for this issue. Can I have access to create a branch and make a pull request?

kerem commented

2026-03-16 16:52:17 +03:00

Author

Owner

@liyasthomas commented on GitHub (Apr 17, 2022):

Hi @sweetkane, if your changes are in your fork of Hoppscotch, you can directly open a pull request to our main branch.

@liyasthomas commented on GitHub (Apr 17, 2022): Hi @sweetkane, if your changes are in your fork of Hoppscotch, you can directly open a pull request to our `main` branch.

kerem commented

2026-03-16 16:52:22 +03:00

Author

Owner

@thgcode commented on GitHub (May 24, 2023):

Hello!
I thought of creating a new issue, but found this one, I tested hoppscotch with NVDA and it read only "button" on the buttons. If pressing tab it read the button name, but not when pressing the arrow keys. I think it could because the button name is set to "button" and the description set to the button name, that is somehow confusing the screen reader, but some buttons are correct like the body button or the parameters button.

@thgcode commented on GitHub (May 24, 2023): Hello! I thought of creating a new issue, but found this one, I tested hoppscotch with NVDA and it read only "button" on the buttons. If pressing tab it read the button name, but not when pressing the arrow keys. I think it could because the button name is set to "button" and the description set to the button name, that is somehow confusing the screen reader, but some buttons are correct like the body button or the parameters button.

kerem referenced this issue

2026-03-17 00:29:12 +03:00

[PR #720] [CLOSED] Send SSL certificate #2815