ToastHawaii / ToastHawaii/osm-apps-catalog
Improve accessibility by offering feedback option
- Dominant language
- TypeScript
- Stars
- 21
- Forks
- 5
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 10
Description
### Problem to solve
### Further details
https://firefox-source-docs.mozilla.org/devtools-user/accessibility_inspector/index.html
### Proposal
https://a11y.digitaldialog.swiss/de/checklist based on https://www.w3.org/TR/wcag/#text-alternatives
make anyware a statemand that we want support that and you can contact use if you have problem
- [ ] show a statement somewhere, that we want to improve accessibility and that we are happy if user contacts us if they find a accessibility related issue.
### Links / references
Contributor guide
Research direction
Start by reviewing the accessibility inspector documentation and the linked WCAG text-alternatives and accessibility checklist references. Locate the appropriate user-facing area for an accessibility statement; done means the statement is visible and explains how users can contact the project about accessibility issues.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- accessibility, frontend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100