Benchmark Results Dashboard has no aria-live regions - status/summary changes are silent to screen readers
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 92/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- html
- Domain
- accessibility, frontend
Research direction
Open benchmark.html and locate #benchStatus and #benchSummary, then compare their markup with the aria-live conventions for the listed status elements in profiler.html. Verify that status, filter, sort, and tab updates are announced to screen readers while #benchError retains its existing alert behavior.
Written by the indexing model from the issue text.
Description
Where: benchmark.html (#744) - #benchStatus, #benchSummary.
Current gap: The rest of the Profiler consistently marks its live-updating status text as aria-live="polite" - profiler.html has it on #fileStatus, #resultsAnnouncer, #referenceStatus, #statusA/#statusB, and #compareAnnouncer. benchmark.html has zero aria-live attributes anywhere, so #benchStatus (updated on every load/error) and #benchSummary (updated on every filter/sort/tab change - the exact "X of Y rows shown" feedback a sighted user relies on) are completely silent to a screen-reader user.
Repro:
$ grep -n "aria-live" benchmark.html
(zero matches)
$ grep -n "aria-live" profiler.html
184: <p class="profiler-status" id="fileStatus" aria-live="polite" hidden></p>
186: <p class="sr-only" id="resultsAnnouncer" aria-live="polite" aria-atomic="true"></p>
...
Suggested approach: add aria-live="polite" to #benchStatus and #benchSummary in benchmark.html, matching the established convention (#benchError already correctly has role="alert").
- Dominant language
- HTML
- Stars
- 47
- Forks
- 45
- Avg merge
- 3h 1m
- Merged PRs (30d)
- 69
Getting set up
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from yakew7/Fair-Code
-
Numeric column headers keep their type in Python (the integer 2020) and are text in the web engineOpenbug help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
bug help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
bug help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
bug help wanted
Difficulty 4/5 3-5 days Newbie friendliness 52/100
Maintainers usually reply within 1 day
-
documentation enhancement help wanted
Difficulty 3/5 1-2 days Newbie friendliness 67/100
Maintainers usually reply within 1 day
All issues in yakew7/Fair-Code
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
jitsi/jitsi-meet#18021 ·
Maintainers usually reply within 1 day
-
chore UI
Difficulty 2/5 1-3 hours Newbie friendliness 87/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
react-component/slider#1097 ·
-
status:approved type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
bug needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day