'Google Chrome 141' stable release, providing more reliable and convenient web accessibility than ever before

The latest stable version of the web browser ' Google Chrome ,' version 141, has been released. To address the growing demand for improved accessibility as web apps become more complex, the new ARIA Notify API has been introduced. This API complements the existing ARIA Live Regions API, providing more reliable and convenient accessibility.

Chrome 141 | Release notes | Chrome for Developers
https://developer.chrome.com/release-notes/141?hl=ja

ARIA Notify API
Improving web accessibility is essential to ensure that web content is accessible to a wide range of people, including those with physical limitations and the elderly. For dynamically updated web applications, it is particularly important to accurately convey up-to-date information to assistive technologies such as screen readers. WAI-ARIA is a technology that addresses this issue, and ARIA Live Regions in particular are widely used as the primary means of notifying assistive technologies of dynamically updated content.

However, ARIA Live Regions have some known challenges. One of them is that they require web page changes to be associated with DOM elements, which makes notifying changes that do not conform to this assumption difficult and inefficient to implement. To address this, the new ARIA Notify API will be introduced.

The ariaNotify() method can send notifications to assistive technologies at any time, allowing for more flexible and efficient implementation. This allows developers to more easily notify assistive technologies of dynamic content updates, which is expected to improve the user experience.
[code]
document.querySelector('button').addEventListener('click', () => {
document.querySelector('button').ariaNotify('You ain't seen me, right?');
});[/code]

◆Apply width and height as presentation attributes to nested <svg> elements
Both SVG markup and CSS now support the width and height presentation attributes on nested <svg> elements. These two approaches allow for more efficient and flexible sizing of SVG images, especially in cases like responsive design.

To apply CSS properties to a nested <svg> element, your HTML would look like this:
[code]
<svg width='100px' height='100px'>
<svg style='width:50px;height:50px;'>
<circle cx='50px' cy='50px' r='40px' fill='green' />
</svg>
</svg>[/code]

On the other hand, if you don't apply any CSS properties, the HTML will look like this:
[code]
<svg width='100px' height='100px'>
<svg width='50px' height='50px'>
<circle cx='50px' cy='50px' r='40px' fill='green' />
</svg>
</svg>[/code]

◆windowAudio option of getDisplayMedia()
The getDisplayMedia() method now has a new option, windowAudio, that controls whether audio from a specific window is included in a screen capture. This allows users to share only the audio from a specific application during screen sharing, improving privacy and convenience.

The windowAudio option can have the following values depending on your web app's settings:
・exclude : Exclude audio capture completely
・system : Capture system audio
・window : Captures audio associated with a window

For example, if you are capturing the screen of a specific application in a web app and you want to share only the audio from that application, set windowAudio to 'window'. Conversely, if you do not want to share the audio from that application, set it to 'exclude'.

◆FedCM: Alternate field for account selection
In addition to 'user's full name and email address,' the account selector now supports 'phone number and username' as an identifier for distinguishing accounts. This enables ID federation using FedCM even for some ID providers that do not use email addresses or full names to identify users.

◆Other updates
・Improved display algorithm for hidden=until-found element and details element
Digital Credentials API: Adding mechanisms to mitigate the risk of unauthorized use
navigateEvent.intercept() : Added precommitHandler option to support delayed commit.
・getDisplayMedia(): Add strictOwnAudio property to control audio capture
・MediaTrackConstraints : Added specifiable values to echoCancellationMode
- IndexedDB: Added getAllRecords() method, and added direction parameter to getAll() and getAllKeys().
Speculation rules: The aggressiveness of speculative loading for 'eager' on the PC version has been adjusted to be between 'moderate' and 'immediate.'
Storage Access API: Stricter compliance with same-origin policy
Signature-based integrity: Ensuring the authenticity of a site by requiring signatures with Ed25519 key pairs and signature verification with public keys
・WebRTC : Support for Encoded Transform (V2)

◆Origin Trial
- Restrict local network access
・Proofreader API
・Extending CSP script-src (script-src-v2)
WebAssembly custom descriptors

Google Chrome 141 also includes two security bug fixes .

The next stable version, 'Google Chrome 142,' is scheduled to be released on Tuesday, October 28, 2025 local time.