I wish we had a #WebPerf metric for when the Accessibility Tree is ready. Something to measure! https://marcysutton.com/accessibility-and-performance/ … #a11y
-
-
Replying to @marcysutton
looked into this a little bit. "ready" is hard to define, but I think you're interested in size of the a11y tree increasing.
1 reply 1 retweet 1 like -
Replying to @paul_irish @marcysutton
turns out, it generally matches up with visual progress, and both stay fairly in sync with the layout tree..
3 replies 0 retweets 4 likes -
Replying to @paul_irish
: does this match up with the interactiveness metric we're discussing? /cc
@marcysutton1 reply 0 retweets 3 likes -
Replying to @slightlylate @marcysutton
assuming that interaction with ATs is just as dependent on the main thread (that's a yes), then yeah absolutely.
2 replies 0 retweets 3 likes -
Replying to @paul_irish @slightlylate
ooh, I’d love to hear more. A slow loading DOM impacts everyone, but some people can see pixels earlier.
1 reply 0 retweets 1 like -
Replying to @marcysutton
: I'm pretty convinced (and have been discussing with
@paul_irish et. al.) how "seeing pixels" really doesn't "count".1 reply 0 retweets 1 like
: like, you might get some "bump" for acknowledging (via first paint) that things will be ready soon
-
-
Replying to @slightlylate @marcysutton
: ...but interactivity is the only goal that matters to users.
1 reply 1 retweet 7 likes -
and accessibility tree is but one of the many interactivity "ready" factors.
0 replies 0 retweets 3 likes
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.