Orange-OpenSource / Orange-OpenSource/IOT-Map-Component
Accessibility audit
Open
Nobody has claimed this yet.
accessibility
epic
- Dominant language
- TypeScript
- Stars
- 24
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
List of identified a11y issues after the a11y audit by @SimonF30
- #39
- #40
- #41
- #42
- #43
- #44
- #45
- #46
- #47
- #48
- #49
- #50
- #51
- #52
- #53
- #54
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 opening the linked issues #39 through #54, since this issue only lists the accessibility audit findings and names no files or tests. Determine the requirements for each linked issue and consider the work complete when the applicable checklist items are resolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- angular, react, typescript
- Domain
- accessibility, frontend
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100