There's more to performance than meets the eye

What does performant look like when you can't see the screen? The browser does more with the DOM than render content. It presents an accessibility tree that's queried using platform accessibility APIs. Different browser processing models mean Assistive Technologies are changing the way they obtain accessibility information, but is that having an impact on performance, and what happens when we introduce a JavaScript accessibility API into the mix?