- From: Repsher, Stephen J <stephen.j.repsher@boeing.com>
- Date: Wed, 16 Aug 2017 15:55:48 +0000
- To: Alastair Campbell <acampbell@nomensa.com>, David MacDonald <david@can-adapt.com>
- CC: WCAG <w3c-wai-gl@w3.org>
- Message-ID: <5839f3de06a94ba5ab99b6a417ab74cc@XCH15-08-08.nw.nos.boeing.com>
What sticks out for me in that article is the trigger of “peripheral motion”. Since there’s no real way for a developer to always keep motion out of the periphery, that means any motion can be a trigger. Now that you explained it this way: > It does reduce the scope from all animation as it excludes: Colour changes, blurring (without movement), blinking and value-updates (e.g. changing one word to another). That’s all I can think of off hand, there are probably others. I like just eliminating animation to avoid the CSS equation, and just call it motion (even in the SC handle). Adding those exclusion examples as a note under the normative SC is probably a good idea for clarity too. Yes, I can live with it – just trying to help. Steve From: Alastair Campbell [mailto:acampbell@nomensa.com] Sent: Wednesday, August 16, 2017 11:29 AM To: Repsher, Stephen J <stephen.j.repsher@boeing.com>; David MacDonald <david@can-adapt.com> Cc: WCAG <w3c-wai-gl@w3.org> Subject: Re: Where we stand on Animations SC #18 > That’s a good point, I shouldn’t have used that as an example. We want to ignore the size/timing aspects we had in the term ‘significant’ when at AAA. [Steve] So scrolling marquees should be in or out of scope? In, mostly for simplicity rather than thinking a text-marque would be a trigger. Differentiating a small text-marque from a larger carousel is getting back into ‘significant’ territory and too much complexity. > [Steve] I wasn’t trying to draw a distinction between “motion” and “movement” since they are synonyms, just that animation implies motion so “motion animation” doesn’t create a subset in my mind. It does reduce the scope from all animation as it excludes: Colour changes, blurring (without movement), blinking and value-updates (e.g. changing one word to another). That’s all I can think of off hand, there are probably others. [Steve] Yep, I agree. Skimming the GitHub thread, it sounds like there’s only evidence to always exclude color or blinking as not a problem, and to include parallax as nearly always a problem, correct? I think just make a choice to create the subset by being inclusive or exclusive, and at AAA probably the latter? If you read through the (excellent) article here: https://webkit.org/blog/7551/responsive-design-for-motion/ You’ll see that including all of those variations on motion will get very wordy. If you try to exclude certain things that will get somewhat wordy with at least 4 things to exclude. Can you live with ‘motion’? The simple version doesn’t need to mention animation, but the title would include that for clarity: “Animation from interactions: For non-essential motion triggered by a user action, there is a mechanism to prevent the motion and still perform the action. Level AAA” Cheers, -Alastair
Received on Wednesday, 16 August 2017 15:56:18 UTC