github / github/accessibility-scanner
The scanner is creating pages that are not ADA compliant
- Dominant language
- TypeScript
- Stars
- 369
- Forks
- 40
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 10
Description
I ran the scanner on a new project today. It fixed one of my html files and also added three html error pages. I merged those PRs. (It also tried to add a test script, js and package.json it appears to have used to validate it’s fixes, but I did not merge those.) I reran the scanner to verify the fixes, and it found compliance issues with the three error pages copilot created in the previous scan.
For example the left side of this screenshot is the original html the scanner created, the right is the issue found when I ran the scanner again:
Contributor guide
Research direction
Start by reproducing the scanner run that creates the three HTML error pages, then inspect those generated pages alongside the accessibility issue shown in the screenshot. The unmerged test script, JavaScript file, and package.json may indicate how the previous fixes were validated. Done means the generated error pages pass a subsequent scanner run without reporting the same compliance issues.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html, typescript
- Domain
- accessibility, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100