OpenCut-app / OpenCut-app/OpenCut
Command dialog title and description are rendered outside DialogContent
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 89.8k
- Forks
- 8.9k
- PR merge metrics
- No merged PRs in 30d
Description
Summary
The command dialog renders its sr-only DialogTitle and DialogDescription as siblings before DialogContent. Since the popup content is rendered through DialogContent, keeping the accessible title and description inside DialogContent should allow the dialog popup to associate with both values correctly.
I prepared a minimal patch in a public fork:
https://github.com/pidouga-dev/OpenCut/tree/codex/command-dialog-description
Commit:
https://github.com/pidouga-dev/OpenCut/commit/a8c65c94bcc477855485462001f722bf7c4dc57b
Patch
The change moves the existing sr-only DialogHeader into DialogContent without changing the title/description copy or visible UI.
Verification
- bun --filter @opencut/web build
- bun --filter @opencut/web test (currently fails during startup because the Cloudflare Vite plugin rejects the existing ssr resolve.external configuration)
Note: I could not open a PR because GitHub shows that this repository limits pull request creation to collaborators.
Contributor guide
No contributing guide indexed for this repository
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 command dialog implementation and inspect the public fork commit a8c65c94bcc477855485462001f722bf7c4dc57b. Run bun --filter @opencut/web build, then verify that the existing screen-reader title and description are associated with the popup without changing visible UI. The web test command is also provided, but currently fails during startup because of the Cloudflare Vite plugin configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- bun, typescript
- Domain
- accessibility, frontend
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 78/100