Skip to main content
WCAGrules
Quick navigation

Fixes by subject · 38 techniques

How to Fix Scripted and Dynamic Content

Content that changes after load is where automated testing stops. A scan sees one state per page, and the bug is usually in the second one.

A page that loads once and sits still is comparatively easy to get right. A page that updates a cart total, opens a modal, filters a list and validates a field as you type has to tell somebody each of those things happened. No scanner will ever check that, because a scan looks at one state per page and never opens the dialog, submits the form or triggers the error. The techniques here cover pairing mouse handlers with keyboard ones, and managing focus as content appears and disappears. They also cover making hover content dismissible and persistent, honoring the reduced-motion preference in JavaScript, and providing alternatives to dragging and path-based gestures. Two of those are narrower than their names suggest. The dragging rule does not reach anything the browser handles for you, so ordinary scrolling is outside it. And the gesture rule asks for a single pointer rather than a single tap, which means a one-finger swipe already counts.

All 38 techniques

They run in technique order, and each one carries a tag. Sufficient techniques satisfy a rule. Advisory ones help without being required. Failures document a specific way of getting it wrong. None of them is mandatory, because W3C publishes techniques as documented ways of meeting a criterion rather than the only ways, so your own approach conforms as long as it meets the criterion.

More on Scripting and dynamic content

The other 13 subjects

Knowing the technique is not the same as knowing you need it.

The free scan checks 10 pages in a real browser and maps every machine-checkable failure to the exact fix guide that clears it.

Run the free scan

Go somewhere useful

Find tools, resources and your workspace.

29 destinations