Web-Facing Change PSA: Don't use aria-details for anchor positioning

[Mason Freed]

Contact emails

mas...@chromium.org

Specification

https://github.com/w3c/html-aam/issues/545

Summary

See the discussion in this issue for more context:

- https://github.com/w3c/html-aam/issues/545

The code to create aria-details relationships for non-popover use cases of anchor positioning was likely a mistake. Since popovers and other semantic relationships *do* create aria-details, and the remaining use cases are likely non-semantic, there is a desire *not* to create these relationships in the non-semantic cases. Since most common use cases use popovers, this change should hopefully not be too noticeable to users.

Blink component

Blink>Accessibility

Web Feature ID

No information provided

Risks

Interoperability and Compatibility

No information provided

Gecko: No signal

WebKit: No signal

Web developers: No signals

Other signals:

WebView application risks

Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?

No information provided

Debuggability

No information provided

Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, ChromeOS, Android, and Android WebView)?

No

Is this feature fully tested by web-platform-tests?

No

Tracking bug

https://crbug.com/461544937

Estimated milestones

Shipping on desktop	144
DevTrial on desktop	144
Shipping on Android	144
DevTrial on Android	144
Shipping on WebView	144

Link to entry on the Chrome Platform Status

https://chromestatus.com/feature/5068815373303808

This intent message was generated by Chrome Platform Status.