Agree. Up to now, the general understanding/implication of "automatic" has been "without user intervention/interaction"

Arguably, a user hovering over something, and moving focus somewhere, would traditionally count as a user interaction, so in that light, it would not fall under the SC... but this would be a real-world problem for users.

Unfortunately, it's likely not easy to unambiguously define the "[a] typical user would not expect" part though, and I suspect that's going to be a sticking point for a binary pass/fail SC. but it would be interesting to get other WG members' opinions here.

Note that the same would also apply to the use of "automatic" for 1.4.2 Audio Control (but arguably, NOT for the use of "automatic" in 3.2.2 On Input, 3.3.1 Error Identification, 3.3.3 Error Suggestion)

the general understanding/implication of "automatic" has been "without user intervention/interaction"

I agree with that, and that was why we added Animation from interactions, because that wasn't "automatic". Automatic generally means on-load or on a timer. I.e. without user-intervention.

If we do add a definition of automatic (either normatively, or more likely by explaining it in the understanding docs), it will need to be fairly narrow. (From experience, this is what happens when there are multiple interpretations: The narrow one is taken so as not to cause issues for people where suddenly things seem to fail where they didn't before.)

In this case it doesn't seem like (many) people would have been interpreting automatic as involving user-interaction, so it shouldn't be a problem.

Now wondering if 2.3.3 Animation from Interaction would cover the scenarios in the OP.

1. When the user moves focus to a certain button, a video starts to play.
2. When the user hovers their mouse over a certain region of the screen, a video starts to play.

2.3.3 has generally been about scroll-related animations, or hover effects on the element being hovered...but does it also cover cases where hovering or similar starts a video (elsewhere on the page)?

Also, there's possibly then still a gap where 1.4.2 Audio Control also talks about "automatically" starting audio, but there's no equivalent "Audio from Interactions". So perhaps 1.4.2 needs a slightly broader interpretation here

I'm glad that you pointed out 2.3.3 Animation from Interactions. It had escaped my attention.

Understanding 2.3.3 mentions 2.2.2: "In contrast, 2.2.2 Pause, Stop, Hide applies when the web page initiates animation.". I wonder if Understanding 2.2.2 would benefit from mentioning 2.3.3? (Currently it mentions 2.3 but not 2.3.3.)

As for what 2.3.3 covers, it seems not to cover video, because it covers only "motion animation" which is "addition of steps between conditions to create the illusion of movement or to give a sense of a smooth transition". This seems odd to me because a full-blown video is, I'm guessing, at least as harmful to the users in question as a 'motion animation'.

I don't know how to fix everything discussed here, but what would you both think of a pull request that included the items below?

• Adding to 2.2.2 a narrow definition of "automatic"
• Adding to 2.3.3 a link to 2.2.2.

Hi @dan-tripp-siteimprove,

That seems like a good next step, thank you. I'd suggest:

• Forking the repo (you suggested a PR so I'm assuming you're familiar with general git/github processes). Or if you have access, you can create a branch here, e.g. Issue2863_automatic-animation
• Editing the understanding > 20 > pause-stop-hide.html file, finding a suitable place in the Intent section to explain what automatic means in this context.
• Editing understanding > 21 > animation-from-interactions.html and adding the cross-reference to 2.2.2.
• Open the PR, and include Closes #2863 in the description.

Okay, I'll try to do that soon.

Done.

In my PR for this, in the interest of avoiding the situation "where suddenly things seem to fail where they didn't before": I made my definition of "automatic" so narrow that it's not very useful, now that I think about it. Do either of you think that we could broaden the definition of "automatic" to include pointer hover and/or scrolling the page?

I've made a counter-proposal to address this here #4012