Built-in reverification dialog lacks an accessible name (aria-dialog-name)
Maintainers usually reply within 1 day
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
- Domain
- accessibility, authentication
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
- Sign in to a React application using
ClerkProviderand the standard Clerk sign-in UI, with authenticator MFA enrolled. - Let the actual second-factor age exceed five minutes, then use
useReverificationfor a requirement withlevel: 'second_factor'andafterMinutes: 5. - 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/react6.18.3; the live browser reports ClerkJS 6.41.0 and Clerk UI 1.42.0 through the publicClerk.versionandClerk.uiVersionfields. 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
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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 clerk/javascript
-
<SignIn />: the reset password code step renders an empty, focusable back button with no accessible namePossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
clerk/javascript#10708 ·
Maintainers usually reply within 1 day
-
MFA enrollment QR SVG lacks an accessible name (svg-img-alt)Possibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
clerk/javascript#10547 ·
Maintainers usually reply within 1 day
-
<SignIn />: first "Use email" click switches back to phone when `initialValues.phoneNumber` is setPossibly taken @twicestruck claimed this 22 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
clerk/javascript#10487 ·
Maintainers usually reply within 1 day
-
useLoadedIsomorphicClerk misses "ready" when a ClerkProvider remounts after clerk-js has loaded — <ClerkLoading> never resolvesMay be free again A pull request for this issue was closed without being merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
clerk/javascript#10462 ·
Maintainers usually reply within 1 day
-
ClerkAPIError drops meta.lockout_expires_in_seconds from user_locked errorsMay be free again A pull request for this issue was closed without being merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
clerk/javascript#10026 · 2 comments ·
Maintainers usually reply within 1 day
All issues in clerk/javascript
Similar issues
-
`@angular/[email protected]` depends on vulnerable Vite 7.3.7 - GHSA-p4f5-76q4-ffq7 (Critical RCE)Openarea: @angular/build
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
angular/angular-cli#34764 ·
Maintainers usually reply within 1 day
-
status/need-triage
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
google-gemini/gemini-cli#30384 · 1 comment ·
Maintainers usually reply within 1 day
-
P2
Difficulty 1/5 Under an hour Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
bug ready-for-human
Difficulty 2/5 1-3 hours Newbie friendliness 60/100
LucasSantana-Dev/Lucky#3150 ·
Maintainers usually reply within 1 day
-
enhancement good first issue priority: low size: XS
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day