Read and apply this announcement

Updated ·

Understand what the announcement establishes

The Chrome 154 beta announcement published on 2 September 2026 describes link and tab modes for scroll-marker-group. In link mode each marker participates in Tab navigation; tab mode uses arrow-key navigation between markers. These behaviours require different accessibility checks.

Prepare an appropriate check

For a carousel, test the selected mode by keyboard, focus visibility and screen-reader content. Provide usable navigation when the feature is unavailable. A beta announcement establishes neither broad compatibility nor success of your entire journey.

Adapt these proposed methods to your context; they do not describe tests performed for a client.

Historical context: this article describes the beta announced on 2 September 2026. Chrome 154 has since reached Stable; check current compatibility for each feature before using it.

Chrome 154 Beta brings new CSS modes, reactive iFrames and security checks for background fetch.

Chrome 154 entered beta on September 2, 2026. The version brings together CSS, JavaScript and Web API evolutions, including scroll-marker-group modes, reactive dimension iFrames and new security rules around Background fetch.

What the ad actually changes

Like any beta, this version is used to prepare and test, not to assume general compatibility. Some features improve accessibility or reduce the necessary JavaScript, while OCs and local network changes may reveal previously tolerated dependencies.

Key points to remember

  • Scroll-Marker-Group Links and Tabs modes specify accessibility behavior.
  • Reactive iFrames can adapt their size to content under certain conditions.
  • Background Fetch applies CORS and access constraints to the local area network.

Consequences for sites and digital teams

Component developers, installable applications, and local integrations should launch their regression tests. CSS new features are interesting, but must remain protected by support detection and a fallback solution as long as the version is in beta.

What to check before acting

  1. Test the keyboard and screen readers of the components concerned.
  2. Check background fetch, websocket and local access in a pilot environment.
  3. Consult the compatibility data before going into production.

Our reading

Chrome 154 pursues two trends: more native capabilities for the interface and a tightening of network borders. Teams following the beta save time to correct, without prematurely imposing these functions on visitors.

official source

This article is based on the announcement published by Chrome for Developers. The source page remains the reference for availability conditions and subsequent changes.