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

Support configurable login form selectors for non-standard label names

Open
#202 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
55/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
typescript
Domain
accessibility, authentication

Research direction

Start at the auth action where getByLabel(/user ?name/i) and getByLabel(/password/i) locate login fields, then inspect how optional inputs are defined. Support configurable username_selector and password_selector values plus the proposed input-type fallbacks, and verify that non-standard or label-free forms are detected and scanned authenticated.

Written by the indexing model from the issue text.

Description

Problem

The auth action finds login fields using getByLabel(/user ?name/i) and getByLabel(/password/i). This misses common login forms:

  • Email-based login: "Email", "E-Mail" don't match /user ?name/i
  • Non-English apps: "Benutzername", "Mot de passe" don't match
  • No visible labels: Forms using only placeholder attributes

When no match is found, the login form is not detected and the scanner proceeds unauthenticated.

Suggested fix

  1. Fall back to input types when label matching fails: input[type="password"] for the password field, and the closest preceding input[type="text"] or input[type="email"] for the username field.
  2. Make selectors configurable via optional inputs like username_selector and password_selector, so users can specify their own labels, placeholders, or CSS selectors for non-standard forms.
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.