@nprofile1q... Sweet. You may also see a pending comment from Pat. Because, you know, we all have thoughts.

@nprofile1q...

@nprofile1q... Largely it’s about filling gaps with live regions, which can make for more robust experiences. The explainer presents use cases: https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/Accessibility/AriaNotify/explainer.md

@nprofile1q... I totally missed this but James caught it (which, you know, *I* like being the one to catch these):
https://dragonscave.space/@jscholes/116767607990174913

I assume you just flipped during transcription:
https://w3c.github.io/aria/#aria-atomic

@nprofile1q... Oh poop, I missed that!

@nprofile1q... I would support WCAG 2.3. And not just because it stands a better chance of being out before 2031.

@nprofile1q... Indeed, I was in that issue earlier today using it as a cudgel in a, um, er, *chat*.

He’s right, the ease of use makes it very dangerous. I often find teams who don’t understand users, screen readers, live regions, etc. feel *everything* needs to be a live region. Current quirky behavior sometimes helps hold back the flood.

But `ariaNotify()` risks making a cacophony of terrible experiences for users if authors continue to be so cavalier.

So yes, let’s all be cool about this.

Be. Cool.