Perhaps you’re right. What I mentioned might have been an issue that has since fade due to browser and AT updates.

Thanks for correcting me.