Accessibility scanner action flags GitHub's own /pages/auth infrastructure page (Actions)
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- typescript
- Domain
- accessibility, ci-cd
Research direction
Start with the attached gh-a11y-scanner.yml and the workflow logs to trace how /pages/auth is discovered, scanned, and reported. Check the scanner's URL-scope or exclusion configuration and reproduce the false positive if possible. Done means the GitHub infrastructure page is handled without user-created fixes, either through scanner behavior or documented configuration.
Written by the indexing model from the issue text.
Description
When running the scanner action on a private GitHub Pages site, the scanner flags an axe page-has-heading-one violation on the URL /pages/auth. This page is GitHub's own built-in authentication page (the login gate for private GitHub Pages sites), not a page a user can author or control.
The scanned element contains attributes like data-turbo-loaded, data-color-mode, data-a11y-animated-images, and js-focus-visible, which confirm it is GitHub's own UI, not user content. We cannot fix this violation because we do not own the page.
In our case, this triggered 30 duplicate pull requests in our repository (as we ran on a list of URLs), all attempting to create a pages/auth.html file that has no effect on the actual scanned page.
Request:
Please either
- (1) fix the accessibility violation on GitHub's own /pages/auth page, or
- (2) update the github/accessibility-scanner action to exclude GitHub-infrastructure URLs from its scan scope by default, or
- document how to configure URL exclusions for these pages
The private repo with CoPilot's attempts to fix the issue:
https://github.com/mcdonalds-corp-new/ally/pull/84
URL of the workflow run:
https://github.com/mcdonalds-corp-new/ally/actions/runs/24263521708/job/70852992850
Error message:
Set issue Accessibility issue: Heading levels should only increase by one on /pages/auth (mcdonalds-corp-new/ally#25) state to closed Set issue Accessibility issue: Page should contain a level-one heading on /pages/auth (mcdonalds-corp-new/ally#26) state to closed
Workflow file and workflow run log attached.
- Dominant language
- TypeScript
- Stars
- 374
- Forks
- 42
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 10
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.
More from github/accessibility-scanner
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
github/accessibility-scanner#264 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 48/100
github/accessibility-scanner#260 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 50/100
github/accessibility-scanner#259 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 58/100
github/accessibility-scanner#245 ·
-
Sitemap Support Open
Difficulty 5/5 Over a week Newbie friendliness 35/100
github/accessibility-scanner#244 ·
All issues in github/accessibility-scanner
Similar issues
-
Browser Waiting for: Product Owner
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
getsentry/sentry-javascript#24577 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
agilepathway/label-checker#640 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
copse-dev/agent-pane#2953 ·
-
agentic-workflows
Difficulty 1/5 Under an hour Newbie friendliness 85/100
githubnext/rig#534 ·
-
automation missing-model model-sync provider:pioneer
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
anomalyco/models.dev#7701 ·