Loading page
About this tool
Preview an uploaded GIF or video without autoplay, capture a still fallback locally, and review reduced-motion delivery choices.
Motion-Reduced Media Preview loads a GIF, MP4 or WebM without autoplaying it, lets you capture any frame as a still PNG fallback, and runs your intended delivery settings against the four conditions of WCAG 2.2.2 Pause, Stop, Hide: the motion starts automatically, lasts more than five seconds, runs in parallel with other content, and is not essential. Accessibility reviewers and content authors get a poster image plus a written list of findings and an exportable JSON review report. Files stay on the device: nothing is uploaded, and the report deliberately excludes the media and the file name.
Open Motion-Reduced Media Preview on AltFTool — it loads instantly in your browser.
Press "Choose a GIF, MP4, or WebM" — the file is read locally up to the 80 MB limit, with no upload and no automatic playback.
Drag Fallback frame time to the moment you want, press Capture still fallback, then Download PNG to save motion-reduced-fallback.png.
Fill the Delivery checklist against the four WCAG 2.2.2 conditions and press Export local review report for motion-reduced-media-local-review-report.json.
The media is decoded and inspected without autoplay, so you can evaluate a motion-heavy asset without being subjected to the motion first.
Scrub to a timestamp, export that frame as a PNG poster, and get the delivery findings against the same asset rather than juggling two tools.
Each result is marked high, review or note, and the summary level is action-needed, review or no-obvious-risk, so genuine 2.2.2 failures are separated from best-practice cues.
GIF, MP4 and WebM up to 80 MB. The decoded canvas must stay within 8,192 pixels on either edge and 16.8 megapixels in total, and video duration must be above zero and no more than 60 minutes.
All four conditions must hold at once: the moving content starts automatically, it lasts more than five seconds, it is presented in parallel with other content, and it is not essential. If any one of those is false, the success criterion's requirement for a pause, stop or hide mechanism does not apply, though a control may still improve the experience.
No. The exported report explicitly records that WCAG conformance was not established, no frame analysis was performed, and flash safety was not analysed. It reflects the delivery settings you described, not the live implementation, so verify the real page with keyboard and assistive technology and consult an accessibility specialist for a formal conformance claim.
No. Decoding, frame capture and the review all run in the browser, and the JSON report records mediaIncluded: false and fileNameIncluded: false. Only media metadata such as kind, MIME type, byte size, dimensions and duration, plus your selected settings and the findings, appear in the export.