In Windows Terminal (running Windows 11, build 22000.613), with either JAWS or NVDA as the screen reader, the screen reader’s command to move the review cursor to the top of the window doesn’t always work as expected. If I clear the screen, or if I’m using some terminal application over ssh that does so, move to top of window does exactly that. However, if I run a PowerShell or Linux shell command that involves a pager (e.g., “man intro” in Linux or “get-help gci -full” in PowerShell), the results are different. After pressing Space one or more times to move through consecutive screens in the pager, the screen reader’s move to top of window command takes the review cursor at least to the first “page” in the pager – if not further back in my command history. I suspect there’s a scroll-back buffer maintaining the session history and that “top of window” is being taken as the start of the scroll-back buffer. The Mac OS terminal has exactly this issue – except that, on the Mac, there’s a “move to visible beginning” command in VoiceOver which is supposed to take you to the top of what is on screen, discounting the scroll-back. Admittedly, it doesn’t always work reliably. However, in Windows Terminal, it’s interesting that going to the top of the window actually works if a screen clear operation has recently been issued – or so it appears. Is there a way to move a review cursor in Windows Terminal to the actual first line currently displayed? Note that the GNOME and MATE terminals under Linux are the most accessible implementation that I’ve found in a graphical environment. In that case, moving the review cursor in Orca to the top of the window works, but I can also use keyboard commands in the terminal (Shift-Page-UP and Shift-Page-Down) to move through the scroll-back history.