Accessibility scanner action flags GitHub's own /pages/auth infrastructure page (Actions)

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.

[gh-a11y-scanner.yml](https://github.com/user-attachments/files/27214881/gh-a11y-scanner.yml)

[logs_64167249977.zip](https://github.com/user-attachments/files/27214893/logs_64167249977.zip)

Commencez par le fichier gh-a11y-scanner.yml joint et les logs du workflow afin de suivre la manière dont /pages/auth est découvert, analysé et signalé. Vérifiez la configuration de portée des URL ou d’exclusion du scanner et reproduisez le false positive si possible. Le travail est terminé lorsque la page d’infrastructure GitHub est prise en charge sans fixes créés par l’utilisateur, soit par le comportement du scanner, soit par une configuration documentée.

Rédigé par le modèle d'indexation à partir du texte de l'issue.