l3montree-dev / l3montree-dev/devguard
Radix UI DialogContent accessibility warning
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 161
- Forks
- 43
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 37
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
- Run the app in dev mode
- 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)
- 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
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.
Research direction
Start with the three locations named in the issue: src/components/ui/command.tsx, src/components/guides/WebhookSetupTicketIntegrationDialog.tsx, and src/components/RiskScannerDialog.tsx. Inspect each DialogContent and run the app in dev mode, opening all three dialogs while watching the browser console. Done means each dialog has a meaningful screen-reader description and the Radix UI warning no longer appears.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react, typescript
- Domain
- accessibility, frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 76/100