I proposed an alternate solution to this: build a name for the row, instead of using a live region. The pull request is here: A11Y: Give topic list rows a spoken name - Pull Request #46384 - discourse/discourse - GitHub
j and k already move focus to the row, and NVDA says “row 1”, “row 2” because the row has no name. I give it one, built from what the row shows. A row that is read as “row 3” today would be read as, for example: “New, Can’t upload images in the composer, Pinned, In Support, By alex, 4 replies, 120 views, Last activity 2 hours ago”.
Because it is the name of the focused row, it is read however I get to the row: j and k, Tab, or going back. Nothing is lost if I move fast through the list, and it should work in braille too, though I haven’t confirmed that.
New and new replies come first, so a row might start “New,” or “2 new replies,”. If a row has neither, I can move on to the next topic right away. If it does, I know it is worth reading the rest. A pinned topic’s preview, if the page shows it, comes last.
I tried it in NVDA: j and k land on each row and it reads. NVDA still needs focus mode (NVDA+Space) for j and k to reach the page, as mentioned earlier in this thread. This doesn’t change that.
If you’d want an announcement as well, or a different order, I’d like to hear it.