Orange-OpenSource / Orange-OpenSource/IOT-Map-Component
Non-logical focus shift
Open
Nobody has claimed this yet.
accessibility
- Dominant language
- TypeScript
- Stars
- 24
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
Non-logical focus shift
ID: issue-0-11
Test: Make the focus path sequential and logical without keyboard traps
Recommendations: https://a11y-guidelines.orange.com/fr/web/developper/navigation-clavier/#rendre-le-parcours-du-focus-sequentiel-et-logique-sans-piege-clavier
Description
- The focus movement does not follow a logical order (reading direction).
- The zoom buttons and the layer display should take the focus first
- (see https://github.com/Leaflet/Leaflet/issues/7479)
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 reproducing the keyboard focus path in the map component and compare it with Leaflet issue #7479 and the linked Orange accessibility guidance. Done means focus follows a sequential, logical reading order, with the zoom buttons and layer display reached first and no keyboard traps.
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