A product announcement should feel alive when hundreds of people celebrate it. In a hybrid Microsoft Teams meeting, however, a room can fall almost silent while likes, hearts, and applause race across the screen. Anyone who cannot see those brief animations is left outside a moment the meeting was meant to share.

Teams Reactions need an audio equivalent. A quiet, brief swish could make the energy in a meeting perceptible without competing with the presenter. An optional screen-reader command could provide more detail when a user wants it. Together, these changes would create a more inclusive and engaging experience for everyone.

The current Teams Reactions experience

Microsoft describes Teams Reactions as a way to express feedback in real time. Its current live reactions documentation lists Like, Love, Applause, Laugh, and Surprise. These reactions appear momentarily over the video/avatar and, when content is being shared, floats up from the bottom of the screen for a few seconds.

Those visual effects are brief by design, but the experience depends on seeing them. A participant who is blind, has low vision, is looking away from the display, is concentrating on shared material, or is seated where the room screen is difficult to see can miss the response entirely.

A celebration no one could hear

I once attended a major company product announcement in Teams. When the new product was revealed, the company president paused to let everyone celebrate. Hundreds of employees were attending from home offices and locations around the world, while only a few of us were together in one office.

Reactions began appearing across the screen, but the room was almost silent. The pause that should have conveyed excitement felt anticlimactic. The enthusiasm was present, but Teams communicated it through a channel that not everyone could perceive.

That moment was an accessibility failure, but it was also a broader experience failure. A presenter should be able to sense that a remote audience is responding. People in conference rooms should feel connected to colleagues elsewhere. Participants should not need to watch every part of the meeting window to know that the group is celebrating, agreeing, or showing support.

Add a subtle audio cue for incoming reactions

When reactions appear, Teams should play a short, restrained swish or swoosh. The cue should indicate that audience response is occurring without reading every reaction aloud or masking speech.

A well-designed cue could provide useful variation:

  • Slight differences in tone or texture could distinguish broad reaction types without turning each reaction into a disruptive alert.
  • Left and right balance could suggest the general direction of the reacting participant's video or avatar when the device supports stereo audio.
  • A denser or slightly fuller sound could represent a larger burst of reactions.
  • Multiple reactions arriving together should blend well.

Direction must remain an enhancement. The cue should still be meaningful through one speaker, a mono headset, a mobile device, or a conference room system. People who have hearing differences in one ear should receive the same essential indication that reactions are occurring.

The default sound should sit below meeting speech. A starting design target might be approximately 20 percent of the perceived level of the presenter, followed by usability testing with people who use screen readers, hearing devices, headsets, mobile devices, and room systems. Teams should reduce or pause the cue when it would mask quiet speech. The goal is background awareness.

Give each participant control

Incoming reaction sounds should be a personal meeting preference. A user should be able to:

  • turn the sound on or off;
  • keep a preferred setting across meetings;
  • choose a low, medium, or custom level;
  • enable a simpler cue with no stereo positioning;.

An organizer or presenter should not be able to override another participant's accessibility preference. If reactions are available in the meeting, a participant who has chosen to hear them should continue to hear them. If an administrator or organizer disables reactions for the meeting itself, there are no reaction events to represent, but that meeting-level control should not silently change the user's saved audio preference for future meetings.

Microsoft already documents separate organizer and administrator controls for whether reactions are allowed. The proposed setting is different: it controls how each participant perceives reactions that are already permitted.

Add an on-demand screen-reader summary

The sound cue would provide immediate awareness, while a screen-reader shortcut could supply detail without automatic speech interrupting the meeting. Teams should add a command named Announce recent reactions (screen reader).

When invoked, the command should summarize reactions from a short rolling period, such as the previous 20 seconds. A concise response might be “12 applause, 8 love, and 3 like reactions.” If there were no reactions, the screen reader should announce “No reactions.”

The command should use the appropriate accessibility API so the user's screen reader provides the announcement. It should not move focus, open the People pane, alter the meeting layout, or require captions or transcription.

Tune the experience for each device

The complete experience may be best introduced on Teams desktop, where stereo output, persistent accessibility preferences, and customizable keyboard shortcuts are most practical. It should also be designed for other meeting contexts:

  • Mobile: Use a shorter cue suited to phone speakers and headsets, respect device audio and accessibility settings, and provide an accessible action for reviewing recent reactions.
  • Microsoft Teams Rooms: Mix reaction audio conservatively for shared speakers so that an in-room audience can perceive the response from remote participants. Microsoft documents that Teams Rooms can send live reactions, making incoming reaction awareness a natural part of the room experience.
  • Mono and assistive listening setups: Preserve the presence and intensity information without relying on stereo direction.

Cross-device consistency matters more than making every device sound identical. Each participant should understand the cue immediately and retain control appropriate to the device being used.

For the Microsoft product team, here is a User story

This User story is ready to copy and paste into product planning or SSDLC tooling.

As a Microsoft Teams participant who cannot see or continuously monitor momentary visual reactions, I want a subtle, user-controlled audio cue when reactions occur and an on-demand screen-reader command that summarizes recent reactions, so I can perceive audience engagement without moving focus, interrupting the presenter, or relying on the meeting display.

Acceptance criteria

  1. Incoming reactions have an audio equivalent. When one or more reactions appear, Teams plays a brief, nonverbal cue for users who have enabled reaction sounds.
  2. Speech remains clear. The default cue is mixed below meeting speech, with approximately 20 percent of the presenter's perceived level used as an initial research target rather than a fixed volume requirement.
  3. Reaction bursts are controlled. A burst of reactions produces a combined cue whose density can increase without playing a separate overlapping sound for every reaction.
  4. Variation is understandable. Subtle variations may convey broad reaction types, volume, or direction.
  5. Mono output is supported. The cue communicates that reactions are occurring through mono speakers, one-sided listening, assistive listening equipment, and devices without spatial audio.
  6. The preference belongs to the participant. Each user can turn incoming reaction sounds on or off and retain that preference across meetings.
  7. The user can keep the feature enabled. A presenter or organizer cannot suppress an individual participant's incoming reaction cue while reactions remain available in the meeting.
  8. Meeting policy remains distinct. If an administrator or organizer disables reactions for the meeting, no cue plays because no reactions can be sent. The user's saved audio preference remains unchanged for later meetings.
  9. The level is adjustable. Users can select an available cue level or customize it without changing the main meeting volume.
  10. Recent reactions can be queried. A screen-reader user can invoke Announce recent reactions (screen reader) to hear an aggregated summary of reactions from the previous 20 seconds.
  11. An empty result is explicit. If no reactions occurred during the rolling period, the screen reader announces a concise message and the command never fails silently.
  12. Keyboard focus is preserved. Invoking the command does not move focus, open a pane, change the meeting layout, or alter a draft message.
  13. The screen reader provides the detail. Teams exposes the summary through the appropriate accessibility API rather than speaking it with a separate Teams-generated voice when a screen reader is active.
  14. Privacy controls are respected. Aggregated counts remain available, while any participant names follow the meeting's identity and attendee-name settings.
  15. The feature is discoverable. The command appears in the Keyboard shortcuts window, and reaction sound preferences have clear labels in Teams settings.
  16. Desktop, mobile, and room experiences are tuned and tested. Each supported client provides equivalent awareness with audio behavior appropriate to its speakers, controls, and shared or personal use.
  17. The cue is usable with assistive technology. Testing includes JAWS, NVDA, Narrator, hearing devices, mono audio, and common headset configurations.

How to test the proposed experience

This test plan describes a future implementation, not functionality currently documented in Teams.

Test 1: Hear a single reaction without losing speech

  1. Join a Teams meeting with reaction sounds enabled.
  2. Ask one participant to speak at a normal level.
  3. Ask another participant to send one Like reaction while the first participant continues speaking.

Expected result: A brief cue is audible, and the speaker remains easy to understand.

Test 2: Hear a burst of audience response

  1. Share a presentation in a meeting with at least ten participants.
  2. Ask the group to send reactions within a few seconds.

Expected result: Teams produces a controlled, fuller cue that conveys increased activity without playing a distracting sequence of individual alerts.

Test 3: Use mono audio

  1. Set the test device to mono audio or use a single-channel output.
  2. Send reactions from participants whose tiles appear in different parts of the meeting view.

Expected result: Every reaction cue remains perceptible, and no essential information is lost when left and right positioning is unavailable.

Test 4: Announce recent reactions with a screen reader

  1. Start JAWS, NVDA, or Narrator.
  2. Ask several participants to send different reactions.
  3. Press the assigned Announce recent reactions shortcut within 20 seconds.

Expected result: The screen reader announces a concise summary by reaction type without moving keyboard focus.

Test 5: Report no recent reactions

  1. Wait until no reactions have occurred for more than 20 seconds.
  2. Press the assigned shortcut.

Expected result: The screen reader announces “No reactions in the last 20 seconds.”

Test 6: Preserve the participant's preference

  1. Enable reaction sounds and leave the meeting.
  2. Join another meeting in which reactions are allowed.
  3. Have another participant send a reaction.

Expected result: The saved preference remains enabled. The organizer or presenter cannot turn it off for that participant.

Test 7: Validate mobile and Teams Rooms behavior

Repeat the single-reaction, reaction-burst, and speech-clarity tests on supported mobile devices and Microsoft Teams Rooms systems.

Expected result: The cue remains noticeable but restrained on small speakers, headsets, and shared room audio. Device-specific tuning does not change the meaning of the cue.

The desired experience

The change can be small and still have a meaningful effect: reactions appear, a quiet swish carries the response into the audio experience, and anyone who wants detail can request a recent summary. Presenters hear the room's energy. Remote and in-room participants share the same moment. People who cannot see the animation are no longer excluded from it.