Orange-OpenSource / Orange-OpenSource/IOT-Map-Component
Markers should be announced as buttons
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 24
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
Map focus and screen reader
ID: issue-0-14
Test: Ensure that key features are usable with screen readers
Recommendations: https://a11y-guidelines.orange.com/fr/web/developper/aides-techniques/#sassurer-que-les-principales-fonctionnalites-sont-utilisables-avec-les-lecteurs-decran
Description
Markers should be announced as buttons (see https://github.com/Leaflet/Leaflet/issues/7428)
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
Start at the map marker rendering entry point in the TypeScript component and compare the expected behavior with Leaflet issue #7428. Verify the result with a screen reader: each marker should be announced as a button and remain usable as a key map feature.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- angular, react, typescript
- Domain
- accessibility, frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100