HSLdevcom / HSLdevcom/digitransit-ui
Accessibility: Itinerary details is not properly read out with voice over
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 267
- Forks
- 145
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 75
Description
Voice over is not read out properly in the itinerary details.
How to reproduce:
- Install Screen Reader for Chrome
- Choose origin and destination addresses
- Make sure there are transit routes returned
- Click on an itinerary suggestion
- Listen to the screen reader voice over reading the itinerary details
Contributor guide
No contributing guide indexed for this repository
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
Start by reproducing the reported steps in the itinerary details with Chrome's screen reader and compare how the itinerary suggestion is read aloud. Done means the itinerary details are conveyed properly by voice-over; the issue does not name a file or test to inspect.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- accessibility, frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100