Add missing accessibility description to p5.Color._parseInputs()
Open
Nobody has claimed this yet.
Area:Accessibility
Bug
- Dominant language
- JavaScript
- Stars
- 24k
- Forks
- 3.8k
- Avg merge
- 3d 16h
- Merged PRs (30d)
- 25
Description
Most appropriate sub-area of p5.js?
- Accessibility (Web Accessibility)
- Build tools and processes
- Color
- Core/Environment/Rendering
- Data
- DOM
- Events
- Friendly error system
- Image
- IO (Input/Output)
- Localization
- Math
- Unit Testing
- Typography
- Utilities
- WebGL
- Other (specify if possible)
p5.js version
1.4.0
Web browser and version
No response
Operating System
No response
Steps to reproduce this
I was asked by @lm-n to open an Issue regarding a missing accessibility description to p5.Color._parseInputs().
Even though it’s a private function, I asked @lm-n if it still needed a describe(). His response:
doesn't matter for reference but could be helpful for contributors to see an example
Which works well enough for me! 👍
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
Locate p5.Color._parseInputs() and compare it with existing describe() implementations in p5.js, using the linked pull-request discussion for context. The work is complete when this function has an appropriate accessibility description and the relevant existing checks or tests pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- accessibility
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100