MFA enrollment QR SVG lacks an accessible name (svg-img-alt)

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

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

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
  1. Render the standard ClerkProvider and SignIn components in a React application.
  2. Require MFA for sign-in and sign in with an account that must complete the setup-mfa session task.
  3. 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/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 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

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.