Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

On first run - got an error on opening an issue

Open
#44 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
typescript
Domain
accessibility, api

Research direction

Start with the first-run issue-filing path and the GitHub Issues API request represented by the reported create-an-issue URL. Reproduce the failure and trace why filing returns Not Found; done means the scanner can create an issue successfully instead of reporting the HttpError.

Written by the indexing model from the issue text.

Description

Seems that the scanner found some a11y issues, but it fails, to my understanding, trying to create an issue.
I don't understand why it refers to the docs website.

The error I see:
Failed on filing: [object Object] HttpError: Not Found - https://docs.github.com/rest/issues/issues#create-an-issue

Image
Dominant language
TypeScript
Stars
374
Forks
42
Avg merge
1d 9h
Merged PRs (30d)
10

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from github/accessibility-scanner

All issues in github/accessibility-scanner

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.