mirror of
https://github.com/hoppscotch/hoppscotch.git
synced 2026-04-25 16:55:59 +03:00
[GH-ISSUE #4879] [bug]: accessible names of buttons are literally "button" #1834
Labels
No labels
CodeDay
a11y
browser limited
bug
bug fix
cli
core
critical
design
desktop
discussion
docker
documentation
duplicate
enterprise
feature
feature
fosshack
future
good first issue
hacktoberfest
help wanted
i18n
invalid
major
minor
need information
need testing
not applicable to hoppscotch
not reproducible
pull-request
question
refactor
resolved
sandbox
self-host
spam
stale
testmu
wip
wont fix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/hoppscotch#1834
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @zersiax on GitHub (Mar 12, 2025).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/4879
Is there an existing issue for this?
Current behavior
I have so far only tested this on the demo site, however, the various buttons on Hoppscotch.io literally report as being "button" to screen readers, which are used by blind/visually impaired users to use computers and software of any kind.
From what I can see the aria-label for these buttons is currently set to the literal hardcoded string "button" which is almost humorously unhelpful, akin to me filling in this issue with the phrase "noun verb adjective" rather than actual words.
Steps to reproduce
Logs and Screenshots
Environment
Production
Hoppscotch Version
Cloud
Interceptor
Not Applicable - Issue not related to network requests
Browsers Affected
Not browser-specific
Operating System
Windows
Additional Information
This could have a number of causes, anything from aria-label being set to the control's type rather than it's name, to a dev not knowing what the property was for, to someone getting accessibility warnings from a linter and deciding "button" was a good string to fill in for this.
This, and I'm sure other issues like it, render the app entirely unusable for professionals in the field who need a tool like this to get work done. Please give this its due diligence.