Back to standards :)

Hey,
So partly because of me testing Tahoe, and just because I noticed the experience even on the web is much smoother, I am back to the good old standard grouping behaviour of VoiceOver on Mac.
On the web, yes we have the same thing that incentivized me to switch from jaws to nvda, aka each landmark is viewed as a single html element as we brows, but I discovered that I didn't read or understand fully VoiceOver user guide about web browsing. My primary and most reliable way has always been vo and arrow keys, and vo cmd letters to navigate by elements. I've just got to get used to use vo shift left/right arrow keys when necessary, and now I no longer have any weird problem with teams in the chats or any other modern web app thanks to this, outside web notification centre is not broken this way on both sequoia and tahoe, I don't have to deal with weird horrible activity switching bugs just for most of 1st/3rd party apple apps like garageband, iwork suite, preview and etc...
In tahoe scrolling has been patched, and since I discovered how to bypass javascript copy blockign 2-3 days ago for my very specific use case, well, and with the patches brought by sequoia to text in iwork, and the potential improvements I'm already seeing with tahoe and spotlight in general, the mac hasn't never been that comfortable for me to use!
And thanks god that emacs and latex exist. Ironically the accessibility gaps of macos have actually forced me to properly learn most linux tools I was just overhearing about here and there, which is a good thing for everyone. And with Matt Campbell doing great stuff thanks to the EU with Newton project, linux desktop which means hopefully asahi linux as well, is suddenly becoming very interesting, and so is my mac.
And who knows, maybe one day things will be good enough for me to not only just have a minimum functional and accessible metal linux desktop, on my macbook but maybe a proper windows 11 virtualized in linux so even on my m2 pro I can run wsl and bypass the arbitrary software limitation of the nested virtualization capabilities only being exposed to >m3 chips while m2 is able to do it on the hardware side? I read somewhere that the team of asahi was actually able to do that.
Sorry for going off on a tangent :) Thanks to that probably one single nerd who will be reading and understanding that, and potentially for correcting me, because I am not that nerd (yet) to stop taking daily shower and have somewhat of a social life. Although I tried stormux --> archlinux so even that is questionable...