Accessibility

1. Our commitment

Motion is what we make, so we take its side effects seriously. We aim to make the AnimatedWebs site and the tools we run meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. We treat accessibility problems that people report as bugs and fix them as part of normal work.

2. What is built in today

• Reduced motion on the site: when your device or browser asks for reduced motion (prefers-reduced-motion), the site shortens or removes its CSS animations and transitions, skips the entrance animations, turns off smooth scrolling in favor of direct jumps, starts the 3D hero in its reduced mode, and our fox mascot jumps to a spot instead of walking.
• Reduced motion in templates: the large majority of our live template demos include prefers-reduced-motion handling, and many include a control to pause motion. Our guides explain the pattern so the templates you build keep it.
• Video backgrounds: video background tiles only play while they are on screen, and do not start at all when reduced motion is on.
• Mascot: the fox mascot can be hidden for good from its own menu. Your choice is remembered in your browser.
• Keyboard and screen readers: the dashboard has a skip link, and the cookie notice is a labeled region. Purely decorative elements, such as the large wordmark in the footer and background effects, are hidden from assistive technology.
• Zoom and small screens: pages are responsive and are meant to work when you zoom text or use a phone.

3. Known limitations

We have not had a full third-party accessibility audit. We would rather say so than claim a conformance we have not proven. The gaps we know about:

• The public pages do not all have a skip link yet. Only the dashboard does.
• Not every one of our hundreds of template demos has a pause control, and a few have no reduced-motion handling yet. Demos are previews of templates, and each one is checked separately.
• Some visual effects (WebGL scenes, canvas animation, scroll-driven film) are visual by nature and have no equivalent for a screen reader beyond the page text around them.
• Parts of the design and brand tools, such as canvas editing and drag interactions, are harder to use with a keyboard or screen reader than the rest of the site.
• AI-generated output from our tools is not checked for accessibility before you receive it. Test it before you publish it.
• Some contrast ratios on decorative or secondary text may fall below AA. We are fixing them as we find them.

4. Templates you build

A template is a starting point. When you publish a site made from one, you are responsible for its accessibility, including your own text, images (alt text), colors and any motion you add. We recommend keeping reduced-motion handling, a visible pause control for any moving content longer than five seconds, and testing with a keyboard and a screen reader. See the Disclaimer.

5. Report a problem

If something on AnimatedWebs is hard or impossible for you to use, tell us. Use the contact form or write to hello@animatedwebs.com. Please include the page address, what you were trying to do, the device, browser and any assistive technology you use. We read every report. We aim to reply within 5 business days and will tell you what we plan to do. If you need the information in another form, we will try to provide it.