rubyforgood / rubyforgood/alongwithyou
Define the accessibility baseline and acceptance criteria
Open
Nobody has claimed this yet.
phase:0
type:foundation
- Dominant language
- TypeScript
- Stars
- 9
- Forks
- 4
- Avg merge
- 9h 34m
- Merged PRs (30d)
- 16
Description
Written and testable before Phase 1 build starts, not treated as later QA, per the risk register.
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 reviewing the risk register and the Phase 1 build plan referenced in the issue. Define a written, testable accessibility baseline and acceptance criteria before Phase 1 begins; done means the criteria are documented and can be used during implementation rather than deferred to QA.
Written by the indexing model from the issue text.
Assessment
- Domain
- accessibility, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100