ossappscollective / ossappscollective/OSS-DocumentScanner
[FEATURE REQUEST] improve accessibility
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 2.4k
- Forks
- 121
- Avg merge
- 1d 58m
- Merged PRs (30d)
- 17
Description
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
Contributor guide
No contributing guide indexed for this repository
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
The issue body is still the untouched feature-request template and names no files, tests, entry points, or specific accessibility problem. First inspect the Android app structure and existing accessibility guidance, then clarify the target users, affected screens, and acceptance criteria before choosing an implementation path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, cpp
- Domain
- accessibility, mobile-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100