Research implementing a11y scans for itdashboard
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 15
- Forks
- 9
- PR merge metrics
- No merged PRs in 30d
Description
Specifcally:
* how many HTML tags have missing attribute text (e.g., missing/empty links and buttons, missing form input labels, missing document language
* how many color contrast issues were found on a website homepage out of compliance with the Section 508 standards set by the U.S. Access Board, which requires agencies to conform to WCAG 2.0’s Level A and Level AA Success Criteria and Conformance Requirements.
* how many website images and other non-text content, including user interface elements, are missing a text description.
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 turning the listed accessibility metrics into explicit scan requirements, including missing text or labels, document language, color contrast, and non-text descriptions. Use the stated Section 508 and WCAG 2.0 Level A/AA criteria as the compliance reference; done means the repository has a documented implementation approach and measurable outputs for each requested check.
Written by the indexing model from the issue text.
Assessment
- Domain
- accessibility
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100