fix: respect prefers-reduced-motion in Framer Motion animations - #349
Merged
Dev-Zully merged 9 commits intoAug 26, 2026
Merged
Conversation
|
@iredis Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Overview
This PR audits all Framer Motion usage in the frontend and makes the animation system respect the global
prefers-reduced-motionsetting. A sharedMotionConfigprovider withreducedMotion="user"is added to both Next.js page roots so transform/layout animations are automatically suppressed for users who request reduced motion. Remaining opacity/shimmer animations in skeletons and data visualizations are guarded withuseReducedMotion()so they render a static, accessible fallback instead of animating.Related Issue
Closes #FE-026
Changes
🎛️ Central Reduced-Motion Configuration
[ADD]
pages/_app.tsxMotionConfig reducedMotion="user"around the app tree.prefers-reduced-motionby default.[ADD]
Perigee/web/pages/_app.tsxMotionConfigwrapper for the Perigee web dashboard.♿ Component Animation Audit
[MODIFY]
Perigee/web/components/CallGraphVisualizer.tsx[MODIFY]
Perigee/web/components/Resultviewer.tsxuseReducedMotion().[MODIFY]
Perigee/web/components/GasUsageChart.tsx[MODIFY]
Perigee/web/components/ResourceHeatmap.tsx[MODIFY]
Perigee/web/components/StrategyPhaseSkeleton.tsxuseReducedMotion()is true.[MODIFY]
Perigee/web/components/ResultViewerSkeleton.tsx[MODIFY]
Perigee/web/components/Skeleton.tsxSkeletoncomponent now checksuseReducedMotion()before applying pulse/shine keyframes.Verification Results
useReducedMotion()check consistentlyMotionConfigprovider withreducedMotion="user"_app.tsxroots for Framer Motion v12+Closes #233