- From: Laura Carlson <laura.lee.carlson@gmail.com>
- Date: Thu, 28 Jul 2016 07:29:12 -0500
- To: Alastair Campbell <acampbell@nomensa.com>
- Cc: W3c-Wai-Gl <w3c-wai-gl@w3.org>, Jonathan Avila <jon.avila@ssbbartgroup.com>
Hi Alastair, Asking a person with first-hand experience can't hurt to inform the issue. It seems like Nat (Gregory) Tarnoff is now working for SSB BART Group [1]. I think we have a few working group members who also work there such as Jon Avila. Maybe that may be a way to reach out. But the Chairs may know the best approach. Kindest Regards, Laura [1] https://www.linkedin.com/in/nattarnoff?authType=NAME_SEARCH&authToken=Genk&locale=en_US&trk=tyah&trkInfo=clickedVertical%3Amynetwork%2CclickedEntityId%3A37142283%2CauthType%3ANAME_SEARCH%2Cidx%3A1-1-1%2CtarId%3A1469708098940%2Ctas%3AGreg%20Tarnoff On 7/28/16, Alastair Campbell <acampbell@nomensa.com> wrote: > Thanks Laura, those links (and the video especially) are really useful. > > David wrote: > “We would want to get out of the theoretical possibility of it being a > problem into real world problems that actual users are having” > > Of course, but to a large extent it is the same problem as for animation > (2.2.2) but with a different trigger. > Do we have to prove the need again? > > The new trigger I’d like to define is when: > - Animation is triggered by a user action, AND > - The animation is not typically associated with the user-action, AND > - The animation fills a large part of the screen. > > The video interview with Greg [1] is very helpful for examples, things in > the video that wouldn’t be covered under 2.2.2 were: > - Parallax scrolling, where the user-action is to scroll, but the animation > is not normally associated with scrolling. > Examples included things moving at different speeds; or rotating; or > ‘zooming in’; or coming in from the side when vertically scrolling; or > fading in. > - Mouse hover which tilts an image. A large image moves in a 3D way based on > mouse movement. > > Picking holes in the proposal: > - It is possible to prevent the animations on the user-agent side. However, > a blanket ‘off switch’ would break functionality (or readability) on sites > which assume it is available, I think there is a need for an authoring side > SC. > - There needs to be a minimum size defined because I don’t think that > typical navigation hover/focus effects on a menu are a problem. Perhaps it > could include something based on the flash threshold definition? > > Any other holes? If not, I’ll iterate the draft SC text [2] as it doesn’t > include the ‘not typically associated’ or minimum size aspects yet. > > It would be helpful to get someone with first-hand experience involved, what > would be the next step on that? > Ask Greg? (The person in the video.) If so, should I, or is there an > official method? > > Cheers, > > -Alastair > > 1] https://www.youtube.com/watch?v=QhnIZh0xwk0 > 2] 2.x.x User initiated animation: For animation triggered by a user action > (such as scrolling) there is a mechanism for the user to pause, stop or hide > the animation whilst still performing the same action. (Level AA?) > > -- Laura L. Carlson
Received on Thursday, 28 July 2016 12:29:41 UTC