# JetBrains IDEs Introduce Audio Cues for Development Workflow New sound signals improve accessibility and productivity by providing non-visual feedback for IDE events. - **Source:** [The JetBrains Blog](https://brifing.si/source/782eebd1-7be8-49cc-b27c-e552516691b2) - **Published:** 2026-11-03 - **Topic:** [Software & Engineering](https://brifing.si/c/engineering) - **Original article:** - **On Brifing:** https://brifing.si/s/3f3b361a-35b8-4296-8141-a7dcc3719b57 ## Audio Cues for Development JetBrains IDEs 2026.3 introduces sound cues to provide audio feedback for critical development events. These signals notify users when builds finish, tests fail, or breakpoints are triggered. Designed to assist developers who multitask or use screen readers, these cues allow for monitoring background processes without needing to constantly check the status area. ## Monitoring Long Running Tasks Developers can now track long-running tasks like builds or tests through distinct audio signals. The system provides unique sounds for success, warnings, and errors, ensuring awareness of progress. This feature reduces the need for manual status checks, allowing engineers to maintain focus on other windows or tasks while the IDE processes work. ## Editor Line Mark Signals Sound cues extend to editor line marks, providing audio indicators when the caret reaches specific code elements. When screen reader support is active, the IDE plays distinct sounds for errors, warnings, breakpoints, version-control changes, and folded code. This functionality bridges the gap between visual code markers and auditory information for better navigation. ## Dedicated AI Operation Sounds The 2026.3 release includes specific audio cues for AI agent operations. These distinct sounds indicate when an agent completes work, encounters an error, requires user input, or manages dictation. These signals are separate from general IDE cues, ensuring developers can easily differentiate between standard background tasks and AI-driven agent activities. ## Centralized Accessibility Settings All sound configurations are consolidated within the new Accessibility page under Appearance & Behavior settings. This hub integrates screen reader support, zoom, contrast scrollbars, and color adjustments for vision deficiency. Users can preview each sound before enabling it, ensuring the selected audio feedback aligns perfectly with their specific personal workflow and preferences. ## Configuration and Customization Sound cues are enabled by default for screen reader users but remain opt-in for others. Developers can toggle specific cues on or off to avoid notification fatigue. Furthermore, users can assign sounds to individual notification groups, allowing for granular control over which IDE events trigger an audio alert during active coding sessions. ## Notes for macOS Users VoiceOver users on macOS should be aware of audio ducking, which may lower IDE sound volume during speech. To ensure clarity, users must disable audio ducking within their Mac system settings. This adjustment prevents the operating system from suppressing IDE signals, ensuring that all audio cues remain audible and effective during development. ## Commitment to Inclusive Design These sound cues represent an ongoing commitment to accessibility rather than a singular feature release. By addressing requests from the community, JetBrains aims to make IDEs more inclusive for visually impaired developers. Feedback is actively encouraged through YouTrack or direct email to help refine these accessibility tools for future software iterations. ## Sources covering this story - https://blog.jetbrains.com/platform/2026/11/accessibility-sound-cues-in-jetbrains-ides/ — --- _Summary written by Brifing from the original reporting. Copyright in the original article belongs to its publisher; read the full piece at the link above._