- From: James Craig via GitHub <sysbot+gh@w3.org>
- Date: Thu, 21 Dec 2023 17:57:34 +0000
- To: public-css-archive@w3.org
Further clarifying, I don't think we should have accessibility-specific Web Platform API whose nomenclature leads designers and developers toward a single solution (in this case "shapes") when that particular solution is not necessarily required. Consider [this anecdote from Jony Ive](https://youtu.be/FLUn7xCuQxo) regarding the word “box” in a children's design contest. “If we were thinking of lunch box we’d be careful about not having the word box already give you a bunch of ideas that could be quite narrow, because you think of a box as being square, a cube, and so we’re quite careful with the words we use because those can sort of determine the path you go down.” Similarly, for the vestibular-related media query, we called it, and the setting it was based on: "prefers-reduced-motion" not "stop animations" (which Windows used for a while), because entirely stopped animations aren't necessary for vestibular accommodation, and because an entire lack of animation can often reduce usability. Apple animation variants for "reduce motion" often include dissolve animations without the [type of motion known to trigger vestibular discomfort](https://webkit.org/blog/7551/responsive-design-for-motion/). -- GitHub Notification of comment by cookiecrook Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7406#issuecomment-1866716502 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 21 December 2023 17:57:36 UTC