Auto populate a draft FPC based on WCAG responses
- Dominant language
- JavaScript
- Stars
- 128
- Forks
- 36
- PR merge metrics
- No merged PRs in 30d
Description
Because the US Access Board has WCAG 2.0 to FPC - https://www.section508.gov/content/mapping-wcag-to-fpc/
And EN 301 549 has mapped WCAG 2.1 to FPS - https://www.etsi.org/deliver/etsi_en/301500_301599/301549/03.02.01_60/en_301549v030201p.pdf
we can automatically generate basic information for the FPC & FPS tables based on the other criteria.
Having linked tables from the FPC to other sections of the OpenACR is beneficial in that it allows mitigation teams in agencies to understand what needs to be done to mitigate for specific types of disabilities.
Contributor guide
Research direction
No files, tests, or entry points are named. Start by reviewing the WCAG-to-FPC and WCAG-to-FPS mappings linked in the issue and locating the existing FPC, FPS, and WCAG response structures; done means basic FPC and FPS information is generated from responses and the tables are linked to relevant OpenACR sections.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- accessibility
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100