Orange-OpenSource / Orange-OpenSource/IOT-Map-Component
Map focus and screen reader
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-13
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
When the map takes the focus the screen reader should indicate that it is a Map (see https://github.com/Leaflet/Leaflet/issues/7193)
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 by locating the map focus behavior in the component and review the linked Leaflet issue and accessibility recommendation. Verify how the map is exposed when it receives focus, then confirm with a screen reader that it is announced as a map.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- accessibility, frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100