l3montree-dev/devguard

Radix UI DialogContent accessibility warning

Open

#2,084 opened on May 28, 2026

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Go (32 forks)auto 404
component/devguard-webgood first issue

Repository metrics

Stars
 (144 stars)
PR merge metrics
 (PR metrics pending)

Description

Description Three dialogs are missing an accessible description, causing Radix UI to emit a console warning and leaving screen reader users without context when a dialog opens. Radix UI's DialogContent requires either a child or an explicit aria-describedby={undefined} opt-out — none of the three affected components provide either.

Steps to reproduce

  1. Run the app in dev mode
  2. Open any of the three affected dialogs:
    • Command palette (CommandDialog in src/components/ui/command.tsx:29)
    • Webhook setup dialog (WebhookSetupTicketIntegrationDialog in src/components/guides/WebhookSetupTicketIntegrationDialog.tsx:35)
    • Risk scanner dialog (RiskScannerDialog in src/components/RiskScannerDialog.tsx:517)
  3. Open the browser console

Expected Behavior No console warnings. Screen readers announce a meaningful description when focus enters the dialog.

Actual Behavior Console warning appears:

Warning: Missing `Description` or `aria-describedby={undefined}` for {DialogContent}.

Screen readers receive no description when these dialogs open.

Contributor guide

Research direction
Locate the three dialogs mentioned (CommandDialog, WebhookSetupTicketIntegrationDialog, RiskScannerDialog) and add a <DialogDescription> child with an appropriate description, or opt out by passing aria describedby={undefined} to DialogContent.
Tech stack
reacttypescript
Domain
frontend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
ReactAccessibility basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
80