♿️(frontend) Announce mic/camera state to screen readers on shortcut toggle

[Ovgodd]

Purpose

No SR feedback when toggling mic/camera via keyboard shortcut.

issue : #875

Proposal

Announce mic/camera state to screen readers on shortcut toggle.

• SR announces "Microphone turned on/off" on Ctrl+D
• SR announces "Camera turned on/off" on Ctrl+E
• Improves a11y for keyboard + screen reader users

[lebaudantoine]

@coderabbitai full review

[coderabbitai]

✅ Actions performed

Full review triggered.

[coderabbitai]

Walkthrough

This pull request adds screen reader announcements for microphone and camera device state changes triggered via keyboard shortcuts. The implementation imports a screen reader utility in the ToggleDevice component to announce state changes, and adds localized strings in English, German, French, and Dutch for "turned on" and "turned off" messages for both camera and microphone devices. A changelog entry documents the feature addition.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly describes the main change: adding screen reader announcements for mic/camera state on keyboard shortcut toggle.
Description check	✅ Passed	The description is directly related to the changeset, explaining the accessibility issue and the solution with specific details about what was implemented.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

Tip

Try Coding Plans. Let us write the prompt for your AI agent so you can ship faster (with fewer bugs).
Share your feedback on Discord.

---

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 and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In
`@src/frontend/src/features/rooms/livekit/components/controls/Device/ToggleDevice.tsx`:
- Around line 95-102: The handler currently derives the announced state from
!enabled after awaiting toggle(), which can be wrong if toggle fails or races;
change the handler to compute nextState = !enabled before calling toggle, call
await toggle(nextState) (pass the intended state into toggle), and only call
announce(...) after the awaited toggle resolves successfully (handle
errors/no-ops by not announcing). Update references in this handler to use
nextState when building the i18n key (t) and keep announce(..., 'assertive')
only on successful completion.

---

ℹ️ Review info

Configuration used: Repository UI

Review profile: ASSERTIVE

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 2c7b4be and 452e523.

📒 Files selected for processing (6)

• CHANGELOG.md
• src/frontend/src/features/rooms/livekit/components/controls/Device/ToggleDevice.tsx
• src/frontend/src/locales/de/rooms.json
• src/frontend/src/locales/en/rooms.json
• src/frontend/src/locales/fr/rooms.json
• src/frontend/src/locales/nl/rooms.json

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud