Any time a role change could cause the interfaces we expose for an object to change (e.g. suddenly we need to expose the IAccessibleTable interface), we should destroy the current object and create a new one (and fire the corresponding events). This is because in COM, the interfaces exposed on an object aren't allowed to change during it's lifetime.

In any case this is a very uncommon thing. Authors are unlikely to do this.

Agreed, it's uncommon but that'd be the right way to handle it - create a new object.

I wonder if we should try to reuse the id...

This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

AXObjectCacheImpl::HandleAttributeChanged should already be handling this. We've recently improved it to handle more cases.

Closing in the absence of a specific repro.