Location:src/app/styles/Animations.css.ts:36-56 (WobbleAnimation, GlowAnimation, CallAvatarAnimation, SendingSpinClass) vs. Animations.css.ts:58-67 (MsgAppearClass, correctly gated with '@media': {'(prefers-reduced-motion: no-preference)': {...}})
Problem
The message-send scale-in animation (MsgAppearClass) explicitly respects reduced motion, but the sibling "message sending" spinner (SendingSpinClass, an infinite 900ms rotation shown on every outgoing message via Message.tsx:146) and the incoming/active-call avatar wobble+glow (CallAvatarAnimation, used in CallEmbedProvider.tsx:168,341) are unconditional animation-iteration-count: infinite rules with no prefers-reduced-motion guard, inconsistent with the rest of the Lotus animation surface (chat backgrounds, seasonal particles, toasts, avatar decorations, mention pulse all check it).
How to trigger
Enable OS/browser "reduce motion", send a message (brief spin before it's acked) or receive an incoming call (avatar wobbles/glows continuously) — both animate despite the preference.
Suggested fix
Wrap SendingSpinClass and CallAvatarAnimation (and WobbleAnimation/GlowAnimation if used elsewhere) in the same (prefers-reduced-motion: no-preference) media guard used by MsgAppearClass, falling back to a static/opacity-only indicator.
Filed from the September 2026 client audit (branch lotus @ 4bea4895).
**Severity:** low · **Type:** a11y · **Confidence:** high
**Location:** `src/app/styles/Animations.css.ts:36-56` (`WobbleAnimation`, `GlowAnimation`, `CallAvatarAnimation`, `SendingSpinClass`) vs. `Animations.css.ts:58-67` (`MsgAppearClass`, correctly gated with `'@media': {'(prefers-reduced-motion: no-preference)': {...}}`)
### Problem
The message-send scale-in animation (`MsgAppearClass`) explicitly respects reduced motion, but the sibling "message sending" spinner (`SendingSpinClass`, an infinite 900ms rotation shown on every outgoing message via `Message.tsx:146`) and the incoming/active-call avatar wobble+glow (`CallAvatarAnimation`, used in `CallEmbedProvider.tsx:168,341`) are unconditional `animation-iteration-count: infinite` rules with no `prefers-reduced-motion` guard, inconsistent with the rest of the Lotus animation surface (chat backgrounds, seasonal particles, toasts, avatar decorations, mention pulse all check it).
### How to trigger
Enable OS/browser "reduce motion", send a message (brief spin before it's acked) or receive an incoming call (avatar wobbles/glows continuously) — both animate despite the preference.
### Suggested fix
Wrap `SendingSpinClass` and `CallAvatarAnimation` (and `WobbleAnimation`/`GlowAnimation` if used elsewhere) in the same `(prefers-reduced-motion: no-preference)` media guard used by `MsgAppearClass`, falling back to a static/opacity-only indicator.
---
_Filed from the September 2026 client audit (branch `lotus` @ 4bea4895)._
jared
added this to the Audit 2026-09 · Medium & Low milestone 2026-09-12 01:51:33 -04:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Severity: low · Type: a11y · Confidence: high
Location:
src/app/styles/Animations.css.ts:36-56(WobbleAnimation,GlowAnimation,CallAvatarAnimation,SendingSpinClass) vs.Animations.css.ts:58-67(MsgAppearClass, correctly gated with'@media': {'(prefers-reduced-motion: no-preference)': {...}})Problem
The message-send scale-in animation (
MsgAppearClass) explicitly respects reduced motion, but the sibling "message sending" spinner (SendingSpinClass, an infinite 900ms rotation shown on every outgoing message viaMessage.tsx:146) and the incoming/active-call avatar wobble+glow (CallAvatarAnimation, used inCallEmbedProvider.tsx:168,341) are unconditionalanimation-iteration-count: infiniterules with noprefers-reduced-motionguard, inconsistent with the rest of the Lotus animation surface (chat backgrounds, seasonal particles, toasts, avatar decorations, mention pulse all check it).How to trigger
Enable OS/browser "reduce motion", send a message (brief spin before it's acked) or receive an incoming call (avatar wobbles/glows continuously) — both animate despite the preference.
Suggested fix
Wrap
SendingSpinClassandCallAvatarAnimation(andWobbleAnimation/GlowAnimationif used elsewhere) in the same(prefers-reduced-motion: no-preference)media guard used byMsgAppearClass, falling back to a static/opacity-only indicator.Filed from the September 2026 client audit (branch
lotus@4bea4895).