A Timing and Motion Audit Steadies an Interface That Will Not Hold Still

What We Keep Finding

Time is an accessibility dimension. A session that expires mid-form throws away a slow, careful, assisted entry. A carousel that advances on its own snatches a sentence mid-read from anyone using magnification, because at 400% they can see about four words at a time and the rest of the slide is off screen.

Motion is where this gets misfiled most, and the misfiling runs in the expensive direction. Motion your page starts by itself has to be pausable, stoppable, or hideable, and that is a Level A obligation nobody is exempt from. Motion the user triggers, which includes parallax responding to their own scrolling, is a different rule at Level AAA, which most sites are not being asked to meet. So an autoplaying background video is a real failure and a parallax header usually is not, and mixing them up either scares a client into rebuilding something fine or lets a real Level A failure through. We say which one each finding is.

Sound is a third rule again and it is the one everyone reaches past. The pause-stop-hide rule is written about moving, blinking, scrolling and auto-updating information, and audio is none of those. Audio playing by itself for more than three seconds has its own rule, and that rule gives you a route the motion one does not. A control that changes the volume independently of the system volume satisfies it, so you do not necessarily need a pause button at all.

Here is the stake that makes this cluster different from every other page in this group. Three of the four rules that apply to everything on a page, including content nobody relies on, live in this territory. Autoplaying audio, self-starting motion, and flashing. Fail one of those and the page does not conform at any level, however good the rest of it is, and it does not matter that the offending thing arrived in a third-party ad slot.

None of it is reachable by a machine, and that is not an opinion. The whole guideline covering flashing and animation has no automated conformance rule at all, from anybody. Our own scan looks at one moment of one page state, and a carousel advancing, a session expiring, and a flash sequence are all things that happen over time.