Dreamweaver Live View and Browser DOM Accessibility Tree Synchronization

Adobe Dreamweaver utilizes a split-view interface to synchronize visual rendering in Live View with the underlying HTML source. While the Properties panel allows for the manual assignment of ARIA landmarks and alt text, the Live View engine operates as a simulation of browser behavior rather than a direct mirror of a specific browser's accessibility tree.

When implementing complex accessibility structures using external frameworks like Bootstrap, there is a potential discrepancy between how the internal rendering engine interprets accessibility attributes and how a production browser DOM processes them for screen readers.

Does the Live View engine maintain a 1:1 parity with modern browser accessibility tree interpretations for ARIA-enabled components? What is the documented behavior for validating accessibility omissions within the Properties panel versus the Live View simulation?