In something like this, Edge is definitely not scraping the rendered content from the front end interface, it’s accessing the underlying Chrome files that store

In something like this, Edge is definitely not scraping the rendered content from the front end interface, it’s accessing the underlying Chrome files that store session history, tabs, urls, etc. and then opening the same sites in its own tabs. I will admit that I’m not an expert on how accessibility feature work, but having a strong understanding of computers I highly doubt its using its own separate rendering engine to access urls directly.