Simplify the UI for most editors
- Dominant language
- JavaScript
- Stars
- 128
- Forks
- 36
- PR merge metrics
- No merged PRs in 30d
Description
Most editors aren't going to need to fill in all of the fields for all of Section 508. We should be finding ways to depreciate those examples which aren't needed.
On the About page we could ask folks to check boxes for all of the elements that comply. This would include the tables/chapters as well as the sections within Tables 1 & 2 (Web, Electronic Docs, Software, Authoring Tool).
We should also have some guidance somewhere about when these are needed. After reading the document from NASA, I wasn't clear that the FPC was needed.
Contributor guide
Research direction
Start with the About page and review how Section 508 examples, tables, chapters, and FPC guidance are currently presented. Define which fields most editors need, how checkbox selections should cover Tables 1 and 2, and where guidance about when the FPC is required should appear; done means the proposed UI and guidance are clear and usable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- accessibility, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100