You're completely right about platform-native accessibility APIs. To be honest, AccessKit itself doesn't support lazy accessibility trees for virtualized scrol

You're completely right about platform-native accessibility APIs. To be honest, AccessKit itself doesn't support lazy accessibility trees for virtualized scrolling, at least not yet. It can avoid constructing the accessibility tree completely if the platform accessibility API isn't queried at all, but there isn't yet a way to only partially construct an accessibility tree while indicating that there's more available on demand. So to some extent, I guess AccessKit brings this web performance problem to native.