Accessibility - Exposing ReduceMotion

[dw2kim]

Use case

For iOS, the MediaQuery.of(context).disableAnimations does not detect whether it is Reduce Motion on or off currently.

Thus, it would be very beneficial to expose the AccessibilityFeatures.reduceMotion to MediaQueryData so that the users can check the flag, Or, alternatively, we should make the disableAnimations flag to reflect the reduceMotion flag for iOS.

Proposal

Solution 1:

• Expose the AccessibilityFeatures.reduceMotion to MediaQueryData

Solution 2:

• Modify the MediaQueryData.disableAnimations flag to reflect on iOS's ReduceMotion flag.

[jonahwilliams]

Reduce motion and disable animations are not equivalent.

[dw2kim]

@jonahwilliams Thanks for clarifying! Is there any way to detect the Reduce Motion from the app? Or, is there a reason why reduceMotion is not exposed to MediaQueryData?

[jonahwilliams]

reduce motion is exposed through the window's AccessibilityFeatures. We decided to stop putting everything on media query after a point.

[dw2kim]

@jonahwilliams I see. I think the reduceMotion is only flag that is missing in the media query for the Accessibility.

Would it be okay to open PR just to expose this reduceMotion flag?
Or, is there a better way to access this flag from the App?

[jonahwilliams]

I think @HansMuller had some idea on this. I believe we should make a new inherited widget that only exposes the accessibility features, and prefer those over the existing ones on media query.

[HansMuller]

This a good suggestion for improving Flutter's a11y support. Factoring reduceMotion into the widget implementations would take a considerable effort.

CC @chunhtai

[kennethj]

Any updates on this?

[chunhtai]

There is no progress done on this issue. Since there is already a way to get the reduce motion setting, this is a low priority issue. We welcome any contribution though.