fix(hud): improve recording control accessibility

[alexcsl]

Description

Improve screen reader output for the Windows recording HUD. Idle controls now expose the selected source and current microphone, webcam, and countdown state. Source results have accessible names and announce loading or an empty list. A stable live region announces recording, paused, and finalizing states while the elapsed timer remains available without being announced every second.

Motivation

Issue #938 reports that recording controls are difficult to operate with a screen reader. This is a focused improvement to the recording setup and HUD. It does not address the timeline or add global shortcuts, which already have separate work in progress.

Type of Change

• Bug Fix
• Other: Accessibility

Related Issue(s)

Refs #938

Screenshots / Video

No visual change.

Testing Guide

Automated checks passed:

• npm run typecheck
• npm run lint (one existing warning in ProjectThumbnail.tsx)
• npm run i18n:check
• npx biome format src/components/launch/LaunchWindow.tsx src/components/launch/RecordingControls.tsx src/components/launch/SourceSelector.tsx tests/ui/hud-accessibility.spec.ts tests/ui/hud-layout.spec.ts
• Four relevant Playwright HUD tests, using installed Chrome because the Playwright Chromium download timed out on this machine
• npx vitest run electron/hudOverlayWindowOptions.test.ts

The existing HUD dividers are vertically centered UI test still fails at its final Projects dashboard assertion after navigating from the HUD to the editor. Its layout assertions pass. This PR does not change dashboard navigation.

Manual Windows Narrator and native mouse pass-through checks are pending. On Windows, focus the Recordly HUD from the taskbar, tab through the source, microphone, webcam, countdown, and Record controls, then choose a source and exercise Record, Pause, Resume, and Stop. Confirm that Narrator announces state changes once and that the transparent HUD still passes mouse input through to the recorded app.

Checklist

• I have performed a self-review of my code.
• I have linked the related issue.
• I have completed a Windows Narrator and native capture check.

[coderabbitai]

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

• Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}