MFA enrollment QR SVG lacks an accessible name (svg-img-alt)
Maintainers usually reply within 1 day
A pull request for this has already been merged.
- #2 by @reseachrandomv — merged
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 84/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- react, typescript
- Domain
- accessibility, frontend
Research direction
Start with packages/ui/src/common/QRCode.tsx and inspect how QRCodeSVG is rendered and how the enrollment UI localizes its text. Check the built-in setup-mfa enrollment screen with axe; the work is done when the QR SVG has a localized accessible name and the svg-img-alt violation is gone.
Written by the indexing model from the issue text.
Description
Description
The built-in pending setup-mfa authenticator flow renders its QR code as an SVG image without an accessible name. A real Chromium sign-in against a development instance reports axe svg-img-alt (serious) on svg[height="200"].
Reproduction
- Render the standard
ClerkProviderandSignIncomponents in a React application. - Require MFA for sign-in and sign in with an account that must complete the
setup-mfasession task. - Open the built-in authenticator enrollment screen and run axe on the displayed QR code.
Expected: the SVG image has an accessible name describing its purpose, localized with the rest of the enrollment UI. Actual: no accessible name is supplied, so the scan fails. No application DOM modification is involved.
This was reproduced in an application integration; a standalone public reproduction repository is not attached. The component source independently identifies the omission: QRCode.tsx at Clerk UI 1.42.0 passes the value and size to QRCodeSVG without a title or accessible-label property. Could the built-in component supply a localized accessible name?
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 password sign-in and pending MFA, not mocked provider responses
No account identifiers, credentials, QR contents or enrollment secrets are included. Exact-rule and broader QR/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
-
Built-in reverification dialog lacks an accessible name (aria-dialog-name)Possibly taken @ItsShivam05 claimed this 5 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
clerk/javascript#10548 ·
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