[GH-ISSUE #3334] General Accessibility Issue with Non-descriptive Button Labels in Hoppscotch #1110

New issue

Open

opened 2026-03-16 18:36:31 +03:00 by kerem · 2 comments

kerem commented

2026-03-16 18:36:31 +03:00

Owner

Originally created by @selametaydogdu on GitHub (Sep 8, 2023).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/3334

Several buttons on the Hoppscotch platform have the aria-label attribute set to "button". This poses an accessibility issue, as screen readers only read out "button" when interacting with these buttons, giving the user no context or indication of the button's function.

Example:
<button aria-label="button" ... >...

Sample text

...

Suggested Change:
Each button should have a descriptive aria-label that matches its actual purpose. For instance, the button with the text "Select Environment" should have the aria-label "Select Environment":

<button aria-label="Select Environment" ... >...

Select Environment

...

Originally created by @selametaydogdu on GitHub (Sep 8, 2023). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/3334 Several buttons on the Hoppscotch platform have the `aria-label` attribute set to "button". This poses an accessibility issue, as screen readers only read out "button" when interacting with these buttons, giving the user no context or indication of the button's function. Example: <button aria-label="button" ... >...<div class="truncate max-w-54">Sample text</div>...</button> Suggested Change: Each button should have a descriptive `aria-label` that matches its actual purpose. For instance, the button with the text "Select Environment" should have the `aria-label` "Select Environment": <button aria-label="Select Environment" ... >...<div class="truncate max-w-54">Select Environment</div>...</button>

kerem commented

2026-03-16 18:36:37 +03:00

Author

Owner

@nischalj10 commented on GitHub (Sep 20, 2023):

This is a good first issue. I see the label is not being used since a long time. Any reason why this practice has been stopped? I am sure this can be picked up by someone new to OSS contributions and be a good issue to get to know the hoppscotch codebase

@nischalj10 commented on GitHub (Sep 20, 2023): This is a good first issue. I see the label is not being used since a long time. Any reason why this practice has been stopped? I am sure this can be picked up by someone new to OSS contributions and be a good issue to get to know the hoppscotch codebase

kerem commented

2026-03-16 18:36:42 +03:00

Author

Owner

@lewislwood commented on GitHub (Oct 15, 2023):

It should be noted that the unlableled buttons also do not have unique identifiers. Normally I am able to manually label buttons with sighted assistance, using my screen reader. This work around has worked for me while accessibility issues are being addressed. When I lable one button all buttons are labelled with that label. This applies for Jaws & NVDA screen readers, I tried both. A simple ID unique field addresses this issue.
Keep in mind we use Headings and their levels to quickly acccess areas. If you see your eye quickly navigating to an area, we blind need something there to helps us. Headings, tables controls, etc help su.

@lewislwood commented on GitHub (Oct 15, 2023): It should be noted that the unlableled buttons also do not have unique identifiers. Normally I am able to manually label buttons with sighted assistance, using my screen reader. This work around has worked for me while accessibility issues are being addressed. When I lable one button all buttons are labelled with that label. This applies for Jaws & NVDA screen readers, I tried both. A simple ID unique field addresses this issue. Keep in mind we use Headings and their levels to quickly acccess areas. If you see your eye quickly navigating to an area, we blind need something there to helps us. Headings, tables controls, etc help su.