Should aria-details changes cause an accessibility event?

[chrishtr]

Currently the html-aam spec says no, but that seems like an omission, because otherwise screen reader users won't be able to observe such changes.

[lucasradaelli]

Adding a bit more context: I encountered this while testing the interest for chrome implementation. When a popover is shown, after focusing an element for the specified delay, screen readers are not announcing that the element now has details. If one presses alt tab and then return to the browser window, the screen reader will announce the element + has details, because the new focus event forces the screen reader to read that element again. The aria-described-by relationship, when created, forces the element's description, and this gets read by the screen reader. I believe aria-details should also have the same behavior.

[scottaohara]

i think this would be a good idea - though core aam would likely be the place to specify in the state and property change events section, similar to aria-describedby

i'm going to transfer this issue to the core aam repo.