rubyforgood / rubyforgood/alongwithyou
No accessibility affordances anywhere in the mobile app
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 9
- Forks
- 4
- Avg merge
- 9h 34m
- Merged PRs (30d)
- 16
Description
Zero accessibility* props across mobile/src. In tasks.tsx the completion toggle is a ✓/○ text glyph inside a bare Pressable, a screen reader announces "✓ Buy milk" with no indication it's a toggle or what its state is. "Delete" is small text with no role. The error banner isn't a live region, so failures are never announced. Worth treating as a real gap given the product's audience, not a nit.
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
Start by auditing mobile/src, beginning with tasks.tsx and its completion toggle, Delete control, and error banner. Identify the relevant accessibility behavior for each reported gap, then verify that controls expose their purpose and state and that failures are announced; done means the mobile app has accessibility affordances in the reported areas.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- accessibility, mobile-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100