You prefer reduced motion.

Canary. The box above only exists with prefers-reduced-motion: reduce and its text has low contrast on purpose. If the scan reports color-contrast on #reduced-motion-canary, the preference reached the browser.
No preference: no issue.
Reduce: color-contrast on #reduced-motion-canary.

Every case below gets prefers-reduced-motion wrong. Some of them change what is rendered depending on the setting, so scan this page with prefers-reduced-motion: no-preference and with prefers-reduced-motion: reduce and compare the results. Others ignore the setting completely; automated tools can't see those, but they are here for manual review.

1. Animations that ignore the preference

Loading forever, and this text keeps bouncing. Neither animation has a prefers-reduced-motion override.

No preference and reduce: the content moves in both cases. No automated rule catches this; it is a manual check (WCAG 2.2.2 Pause, Stop, Hide and 2.3.3 Animation from Interactions).

2. Inverted media query

This text only wobbles for people who asked for reduced motion. The animation was written inside @media (prefers-reduced-motion: reduce) instead of no-preference.

No preference: static.
Reduce: animated. No automated rule catches this; it is a manual check.

3. Content that only exists when motion is allowed

Breaking news: this scrolling ticker is very hard to read.
Old school scrolling text with the obsolete marquee element.

No preference: color-contrast on the ticker and marquee on the marquee element.
Reduce: no axe issues — the block is display: none. The HTML validator reports the obsolete marquee element either way, because it doesn't depend on media queries.

4. Content that only exists when reduced motion is requested

The developers replaced the ticker with a static banner for people who prefer reduced motion, and forgot to check it.

Static version of the news banner, shown because you prefer reduced motion.

No preference: no issues — the block is display: none.
Reduce: color-contrast on the note, image-alt on the goldfish, link-name and image-alt on the icon link.

5. JavaScript that ignores the preference

This carousel advances every three seconds with a sliding transition. It never checks matchMedia("(prefers-reduced-motion: reduce)") and has no pause button.

scrolls with behavior: "smooth", and the whole site sets scroll-behavior: smooth on html without a reduced motion override.

No preference and reduce: the carousel and the smooth scrolling run in both cases. No automated rule catches this; it is a manual check (WCAG 2.2.2 Pause, Stop, Hide).