@hi_mayank Thanks. The toast div is on the page to begin with and, in my testing, screen readers read out updates correctly when they’re morphed into place (if you don’t use morph, you need a container, as you’ re replacing the whole element and, again in my own testing, I see that Chrome’s engine handles even these well but Firefox doesn’t.)