Load a WordPress site with one of those animated heroes and turn on a screen reader, and it spells the headline out: S, P, R, I, N, G. The sr-only fallback is there, the aria-hidden attributes are correct, and it still reads badly in most screen reader and browser combinations people use. That failure, and the way out of it, is why I kept reading a recent piece on modern CSS animations.
Mariana Beldi’s toolkit post on CSS-Tricks walks through split text, clip-path reveals, scroll-driven animation, 3D scenes and custom cursors, all without JavaScript libraries. I agree with her that motion should be designed before it’s coded. My interest is narrower: which of these survive a real WordPress install, with its page builder, plugin CSS and theme updates.
What modern CSS animations replace on a WordPress site
It’s rare for me to inherit a site that doesn’t load an animation library. AOS here, GSAP ScrollTrigger there, sometimes both. All of them compete with jQuery and the WooCommerce frontend bundle for main-thread time. Scroll-driven animation replaces that dependency: the browser ties an animation’s progress to scroll position on the compositor, with no scroll listener. The parallax pattern in the post is one keyframe plus a –offset custom property per layer.
The split text trap
The source is unusually honest about split text: it cites Adrian Roselli’s testing of GSAP’s SplitText across eight screen reader and browser combinations, where the split text announced correctly in only two. The sr-only plus aria-hidden markup is the standard fix and still not a guarantee. So my rule is simple: if the words carry information, a product name, a price, a checkout heading, I don’t split them. For decorative display text, the letter-spacing trick is safer. It collapses characters with negative values and animates back to zero without touching the DOM, and I’ve written about running that on a WordPress site.
Shipping scroll timelines in a theme
Support has caught up: scroll() and view() work in Chrome 115 and up, Edge, Safari 26 and Firefox 159, which covers the browsers most client traffic uses. Two details will bite you. The animation shorthand resets animation-timeline to auto, so the timeline declaration has to come after the shorthand. And WordPress adds no reduced-motion handling for you, so if you ship motion you ship the media query too. On a cover block it looks like this:
@supports (animation-timeline: view()) {
.wp-block-cover__image-background {
animation: bbioon-rise linear both;
animation-timeline: view(); /* must follow the shorthand */
}
}
@keyframes bbioon-rise {
from { transform: translateY(5vh); opacity: 0.3; }
to { transform: translateY(0); opacity: 1; }
}
@media (prefers-reduced-motion: reduce) {
.wp-block-cover__image-background { animation: none; }
}Wrap it in @supports as shown and old browsers get the static image. The MDN guide on scroll-driven animations also covers named timelines, which matter once several blocks share one scroller. For staggered children, sibling-index() will replace the hand-numbered --i properties the CSS-Tricks demos use; I’ve written about that swap.
Where I’d stop
The 3D scenes I’d keep off product pages. Layers of preserve-3d children over lazy-loaded images look great in a CodePen and often stutter on a mid-range phone with a store’s scripts loaded (I’m not sure how the CSS voxel engines hold up on low-end Android). Custom cursors are fun on a gallery and a liability near an add-to-cart button, and since Firefox caps them at 32×32px while Chrome allows up to 128×128px, 32 is the only consistent size. The cheap win is the clip-path reveal: animate a cover image or an SVG group from circle(0%) to circle(100%), with animation-fill-mode: both so the element doesn’t flash before the animation starts. Respect reduced-motion preferences here too. If you’d like help porting a GSAP-dependent theme onto native animation, or auditing a hero that reads letter by letter, that’s work I take on.