@Edent It did, yes. Some content about slow content loading and 20 characters/second average reading rate and some other stuff.
@Edent It did play a bit of havoc with my screen reader though - I suspect because as the content gradually loaded it forced the DOM to rebuild which in turn forced the accessibility tree to be rebuilt.