Enhancement: Help ANDI be better at seeing dynamic content changes and updating

[mraccess77]

Many pages have dynamic content such as menus. When you click on the menu ANDI doesn't recognize the new focusable items. The user might need to switch modules and hope the menu doesn't close to get ANDI to see the new content. Clicking the "refresh ANDI' button often closes the new content on the page. It might be useful for ANDI to create some DOM mutation observers and automatically see these changes.

https://developer.mozilla.org/en-US/docs/Web/API/MutationObserver

[SSAgov]

This is definitely an idea that has been on the back burner since inception. Unfortunately, Mutation Observers are not available on pages running IE compatibility modes (IE7) which many government agencies still need to account for and test. We hope to one day incorporate this type of behavior into ANDI. For now, users have the ability to use ANDI’s refresh button (alt + =) to rescan the page. However, as mentioned in your comment, some applications create menus and dynamic content in such a way that the content is not able to remain revealed when focus is withdrawn, therefore ANDI doesn’t “see” it. When circumstances such as these arise, testers will have to revert to traditional accessibility analysis techniques (testing with a screen reader, code inspection).

[DKeele23]

can you get the book entry to process?