WordPress 7.2 Beta 5 Fixes Focus and Motion

Primary topic Mobile Publishing and Monetization

WordPress 7.2 Beta 5 arrived on November 10, 2026, with two accessibility fixes for its new default theme, Ipsum. Page crossfades now follow the visitor’s reduced-motion preference, and several button focus rings move inward. If you are evaluating Ipsum, test these changes now on a staging copy. Keep your stable WordPress release on production. Beta 5 is for testing and development. If you use another theme, test its own focus and motion behavior.

Why the page fade needed a theme fix

In Beta 4, the theme enabled cross-document transitions even with reduced motion requested. The browser’s ability to animate the navigation did not itself make Ipsum honor that preference. Beta 5 gates the opt-in with a media query:

@media (
    prefers-reduced-motion:
    no-preference
) {
    @view-transition {
        navigation: auto;
    }
}

This is the condition introduced by the motion fix. The crossfade remains available when the visitor has no reduced-motion preference. When reduced motion is requested, Ipsum no longer enables it through this rule. Independent transition rules in a child theme or plugin still need their own check.

For an eligible cross-document transition, both documents must opt in and share the same origin, with no cross-origin redirect in between. Click a link within the page for your test. Typing a destination into the address bar or following an external booking link does not exercise the same route.

Run the same navigation with both preferences

Start with stock Ipsum on Beta 5 in Chrome or Edge, the browsers used in the patch’s test instructions. Use your index page and a linked post. You only need Beta 4 if you are investigating the original regression.

1. Leave the device’s motion preference at its default. Load the index, click the post link and check that a crossfade appears.
2. Enable reduced motion in the operating system. Reload the index, then click the same post link. Expect ordinary navigation without the crossfade; the post must still open.
3. Switch to one non-default Ipsum colorway and repeat both passes. Then repeat the route on a phone using its accessibility setting and your audience’s browser.

Keep the URLs and browser fixed while changing the preference. A fade in the first pass supplies the positive control: without it, two unanimated navigations cannot establish whether the preference gate worked. The table above gives the next action for each result. Judge the animation separately from how long the destination takes to load.

What changed in button focus

The bundled Ipsum update removes the Button block’s 4px focus-offset overrides, including its Outline variation. They can inherit the shared -4px offset already used by the theme’s button element styles. Those shared styles specify a 1px dotted outline using currentColor, the element’s text color. Moving that line inward changes which background sits behind it.

A November 2 contributor test shows the mechanism: on 7.2-beta3-src, an intermediate patch changed Fill, Outline and Post Comment from 4px to -4px; Search stayed at -4px. Chromium and Firefox at 1200 × 800 showed the near-white ring more clearly against the dark focused button than against the light page. The contributor estimated roughly 6.4:1 contrast for that test.

The final patch also makes Outline’s focused colors match its hover colors. That earlier contrast estimate therefore cannot certify every Beta 5 button or palette. Use it as a worked example of why placement matters: for a pale ring on a pale page, bringing the ring onto a dark button can solve the visibility problem. Your decision still rests on the colors of the control you ship.

Test actual controls, including Outline

On a test post, add Fill and Outline Button blocks, a Search block and an open comment form. Tab through all four controls. Check the ring as focus arrives and while it stays there; visible keyboard focus must remain visible. Use a real keyboard action rather than a mouse hover or tap.

Repeat with your site’s palette, including a button in a narrow card or callout, then check high-contrast mode. On a phone or tablet, use a connected keyboard for the keyboard-focus check. For each control, record its computed outline color and offset alongside what you can actually see. A correct negative offset cannot rescue a ring that blends into its focused background.

If a check fails, isolate the override

Compare the failing route with an uncustomized Ipsum copy on the same build. If only your customized site fails, inspect child-theme CSS, saved styles and plugin styling before changing the whole palette. For a persistent fade, look for another @view-transition rule; for a missing ring, inspect the winning focus declarations. Keep the PHP version fixed while comparing the theme.

Test the public-facing page separately from the signed-in editor. Start with the index and single-post templates, then cover page, archive and 404 templates where their backgrounds or controls differ. The Ipsum testing plan also calls for style variations, patterns and desktop, tablet and mobile layouts.

For a reproducible stock-theme failure, include WordPress and theme versions, plugins, browser, OS and motion setting. Supply both navigation URLs, or the block style and palette, plus steps and a capture. The interaction-testing guide explains why the sequence that produces the state matters. Use the Alpha/Beta/RC forum for help. The official reporting guide directs reproducible core bugs to Trac and editor bugs to Gutenberg’s issue tracker. To join organized testing, use the test team and its #core-test Slack channel.

Choose a test build for Ipsum

For a stock check, open the release page’s Playground. For your site, use staging. Download the Beta 5 ZIP, or install and activate WordPress Beta Tester with Bleeding edge and Beta/RC Only. To pin an existing disposable installation, run wp core update --version=7.2-beta5.

Other Beta 5 work covers application-password creation emails, admin-toolbar keyboard navigation, Visual History accessibility, Notes reaction permissions, MP3 uploads and Git-worktree automatic updates. Ipsum also gains block-style, pattern and stylesheet refinements; the theme sync lists those changes. The release notes link core tickets and Gutenberg changes since November 3, and report known core PHP 8.6 issues resolved ahead of its scheduled November 19 release. Verify plugin and theme PHP compatibility separately.

The planned milestones are RC1 on November 17, RC2 on November 24, RC3 on December 1, a dry run on December 7 and final release on December 8, 2026. Save your failing and passing routes now. Rerun them on the release candidate and final build with your content and plugins; adopt Ipsum when those checks pass alongside your normal upgrade checks. If one fails, keep your current theme while you resolve it.