NUKnightLab / NUKnightLab/TimelineJS3
Previous, Next buttons use aria-label instead of content for name
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 3.2k
- Forks
- 645
- PR merge metrics
- No merged PRs in 30d
Description
| Issue Description | WCAG Criteria | Status | Category | Example | Notes |
|---|---|---|---|---|---|
| Previous, Next buttons use aria-label instead of content for name. | QA | Identified | Screen reader, Voice Control | <button class="tl-slidenav-previous" type="button" aria-label="previous, Women in Computing, " style="top: 458px; display: block;"> <div class="tl-slidenav-content-container"> <div class="tl-slidenav-icon"> </div> <div class="tl-slidenav-title">Women in Computing</div> <div class="tl-slidenav-description"></div> </div></button> | aria-label tends to not be translated. Removing aria-label and replacing with a visually-hidden span containing "Previous" or "Next" will result in the same button name. |
Contributor guide
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.
Research direction
Search the JavaScript source for the tl-slidenav-previous and tl-slidenav-next button markup, then inspect how their accessible names are generated. Replace the aria-label approach as described and verify that each button retains a usable name from its visible or visually hidden content, including the timeline title.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- accessibility
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100