On one hand, I'm glad that screen readers can do something with this new API out of the box. On the other, long-standing bugs exhibited by using live regions are still present with this new API, such as #NVDA not interrupting a normal-priority message when a high-priority one comes in. #accessibility

That particular interruption bug would be an NVDA bug, right?Not a browser/API issue.

@fireborn Yes.

@fireborn does this new notify API also only still work, like ARIA, when the document is in focus?

@cachondo I think it's using the same machinery under the hood, so I would imagine that is still true. I can add a delayed announcement example to test. @fireborn

@fireborn begs the question, when is a notification not a notification?
if I'm waiting for a background process to do something on the web, should my screen reader announce that even if I'm in a different tab or focused on a different app altogether?

@cachondo I think that should probably be your choice. Unfortunately the concept of consent hasn't made it into Windows screen readers yet. @fireborn