App-wide transitions and hover animations never respect prefers-reduced-motion

[chonilius]

Across the app, hover/theme transitions are applied unconditionally with no
prefers-reduced-motion guard anywhere in src/app/globals.css or the Tailwind
utility classes used throughout the components:

/* globals.css */
body {
  transition: background-color 0.2s ease, color 0.2s ease;
}

// BountyCard.tsx
className="... transition-all ... hover:-translate-y-0.5 hover:shadow-md ..."

// Navbar.tsx's "Dashboards" dropdown
className="... transition-all group-hover:visible group-hover:opacity-100"

None of these are wrapped in, or overridden by, a @media (prefers-reduced-motion: reduce)
block. A visitor who has explicitly set their OS/browser preference to reduce motion
(a real, common accessibility accommodation for vestibular disorders and motion
sensitivity) still gets every hover-lift animation on every bounty card, every theme
transition, and every dropdown fade, exactly as if no such preference were set —
globals.css never queries it at all.

Suggested fix: add a @media (prefers-reduced-motion: reduce) block in globals.css
that disables/shortens transitions and transforms globally (e.g. forcing
transition-duration: 0.01ms !important on *), so users who've opted out of motion at
the OS level actually get a reduced-motion experience.

[Mubest29]

@Mubest29 has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hello Maintainer, I’ve carefully looked over the issue and understand what needs to be done. I’m confident I can handle it successfully. Please consider assigning it to me.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Mubest29 to this issue.

[Big-Dammy001]

@Big-Dammy001 has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hello Maintainer, I’ve carefully reviewed the issue description, requirements, and acceptance criteria. I have a clear understanding of the expected outcome and believe I can implement a clean, reliable solution while following the project’s existing conventions. I’m ready to take ownership of the task, test the changes thoroughly, and submit a quality pull request. Kindly consider assigning it to me.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Big-Dammy001 to this issue.

[Levi-Ojukwu]

@Levi-Ojukwu has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hello maintainer, I can handle this issue.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Levi-Ojukwu to this issue.

[drips-wave]

Congratulations, @Levi-Ojukwu! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

🧑‍💻 @Levi-Ojukwu: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊