Open Bug 1650704 Opened 4 years ago Updated 4 years ago

reduced-motion loading icon looks out of place with current Windows styling

Categories

(Firefox :: Theme, enhancement, P5)

Unspecified
Windows
enhancement

Tracking

()

Tracking Status
firefox80 --- affected

People

(Reporter: yoasif, Unassigned)

References

Details

(Keywords: blocked-ux)

Attachments

(1 file)

Attached image gMJth.gif

The hourglass introduced in bug 1431237 is out of place in current versions of Windows. It would be better to use the standard Windows spinning dots (like in Microsoft Edge), especially given that some level of animation seems to be contemplated (bug 1650028).

Depends on: 1431237
See Also: → 1650028

The whole point of it is to be static! It's visible only for people who explicitly asked for reduced motion experience.

Yeah, the animation shown in comment 0 doesn't look reduced-motion friendly at all.

Severity: -- → S4
Keywords: blocked-ux
Priority: -- → P5

It is curious to me why Microsoft doesn't seem to care about this, given the other work they have done around accessibility.

In any case, my suggestion is not to use the exact animation (that is just an example anyway), but to study Edge to understand whether it is doing something that is better than the Photon animation in this use case and fits in better than the hourglass.

With regards to the point of it being static, Apple says:

Keep indeterminate progress indicators moving so people know something is happening. People associate a stationary indicator with a stalled process or a frozen app. If a process has stalled for some reason, provide users with feedback that helps them understand the problem and what they can do about it.

and bug 1650028 already contemplates animation.

I am curious as to whether the Photon animation is the problem, because this spinning dots animation is used in Windows and cannot be disabled as far as I can tell. Of course, they could be doing it wrong, but I don't know that.

My understanding of prefers-reduced-motion and its explanation at https://www.w3.org/WAI/WCAG21/Understanding/animation-from-interactions.html is that the difference in interpretation might be one of degree. From an accessibility standpoint, the idea is to avoid inducing nausea or debilitating eye strain, not to necessarily eliminate all motion. Accordingly, the priority is on whole-screen motion or jitter, rather than animation in smaller areas like icons. Each implementor has to make their own judgement call on how much is too much.

You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: