Does reduce-motion help address 2.2.2 Pause, Stop, Hide, or does 2.2.2 require an onscreen mechanism?

[jamieherrera]

2.2.2 includes in the normative text,

....there is a mechanism for the user to pause, stop, or hide it...

mechanism is defined in WCAG for 2.2.2 (and for other SC) as

process or technique for achieving a result
Note 1
The mechanism may be explicitly provided in the content, or may be relied upon to be provided by either the platform or by user agents, including assistive technologies.
Note 2
The mechanism needs to meet all success criteria for the conformance level claimed.

So... if a mechanism can be provided at the platform level, could prefers-reduced-motion address some select scenarios for 2.2.2 as well as for 2.3.3 Animation from Interactions?

[patrickhlauke]

Related https://github.com/w3c/wcag/issues?q=is%3Aissue%20state%3Aopen%20prefers-reduced-motion - this has been discussed a few times before. I believe current thinking is that yes, it's a valid mechanism

[patrickhlauke]

x-link #4318

[detlevhfischer]

The mechanism needs to meet all success criteria for the conformance level claimed.

Just for the record, the switch to activate "Reduce motion" in iOS accessibility settings does not meet 1.4.11 Not-text contrast (that is, without that other switch, "Increase Contrast", being activated that itself does not meet 1.4.11), so strictly speaking in that environment the mechanism would not meet all SCs on the level claimed.

[mraccess77]

Just for the record, the switch to activate "Reduce motion" in iOS accessibility settings does not meet 1.4.11 Not-text contrast (that is, without that other switch, "Increase Contrast", being activated that itself does not meet 1.4.11), so strictly speaking in that environment the mechanism would not meet all SCs on the level claimed.

There is another setting in iOS to show on/off labels. So, can a setting for a setting be used?