Built-in reverification dialog lacks an accessible name (aria-dialog-name)

Open Beginner friendly
#10,548 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@ItsShivam05 is already working on this.

Since Nov 14, 2026.

  • #10827 by @ItsShivam05 — open

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
75/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
react, typescript

Research direction

Start with packages/ui/src/elements/Modal.tsx, the cited source for the standard modal. Trace how it renders the visible localized heading and the dialog container, then check whether the dialog's accessible name is associated with that heading. Done when axe no longer reports aria-dialog-name on the built-in reverification challenge.

Written by the indexing model from the issue text.

Description

Description

The built-in reverification modal opens with role="dialog" and aria-modal="true" but no accessible name. A real second-factor reverification challenge reports axe aria-dialog-name (serious) on .cl-modalContent.

Reproduction
  1. Sign in to a React application using ClerkProvider and the standard Clerk sign-in UI, with authenticator MFA enrolled.
  2. Let the actual second-factor age exceed five minutes, then use useReverification for a requirement with level: 'second_factor' and afterMinutes: 5.
  3. Run axe while the built-in reverification challenge is open, before entering the code.

Expected: the dialog has an accessible name, preferably associated with its visible localized heading. Actual: the modal container has neither aria-label nor aria-labelledby; the scan fails. This is not an application-owned dialog.

This was reproduced in an application integration; a standalone public reproduction repository is not attached. The relevant source is Modal.tsx at Clerk UI 1.42.0. Could the standard modal connect its accessible name to the rendered heading? We did not find a supported appearance or reverification option that supplies this semantic label.

Environment
  • @clerk/react 6.18.3; the live browser reports ClerkJS 6.41.0 and Clerk UI 1.42.0 through the public Clerk.version and Clerk.uiVersion fields. ClerkJS 6.42.0 was the initial source-review tag, not the observed hosted runtime.
  • React 19, Linux, Chromium driven by Playwright 1.64.0
  • Real development-instance session and actual elapsed factor age, not mocked provider responses

No account identifiers, credentials or verification codes are included. Exact-rule and broader reverification/accessibility searches found no existing issue. No Clerk support contact was made as part of this report.

Dominant language
TypeScript
Stars
1.8k
Forks
492
Avg merge
1d 8h
Merged PRs (30d)
374

Getting set up

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 clerk/javascript

All issues in clerk/javascript

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.