several days spend on my Mac, my thoughts.

So glad you like your Mac. This is my second one and I'm very happy with it. VoiceOver does an excellent job, and I think it has only gotten better through the years. I don't have much if any Terminal experience so can't comment. But I'm definitely staying with Apple products at least for the foreseeable future. I have used some Microsoft apps on my iPhone though, and they seem to be pretty good.

Regarding Terminal, this is only fun if you use a braille display. Unfortunately, there does not exist any option in order to queue the speech output sent to VoiceOver.

Hey there hope your sunday is going well. I have bought a new macbook air and I am Loving it. It is (as you said) very snappy. Apple products are my go-to because I just love apple.

3. macOS is unix like os, so we can use bash and similar.

Sure, sure.

But Safari and other processes still freeze up constantly while VoiceOver is running, and ARIA modal dialogs are completely inaccessible with the VoiceOver cursor in any browser, because Apple haven't quite gotten around to fixing it. When that happens, and especially at a critical point like while submitting a payment form on an online shop for blindness products, I begin to think that I'm in some sort of weird abusive relationship with an OS which keeps me by virtue of being "UNIX-like". And I begin to think seriously about Windows again, now with WSL ...

At the risk of repeating myself from another thread, I love macOS, the platform. I hate VoiceOver, the increasingly mediocre screen reader, which lets macOS down, and is itself let down by Apple's priorities, and bugs. Yes, philosophically I'm very much in tune with a mainstream screen reader and the choice to use an integrated platform which just so happens to have a technically astute, stable, underdog, developer-focussed OS, that provides an unrivalled experience for sysadmin-type work in a UNIX shell. Practically (or is that pragmatically?), I suspect macOS's more obvious virtues are increasingly a poor defence for its more fundamental problems. It ought to be a concern to us that we blind paradoxically expend energy and effort and bring a kind of nuts-and-bolts ethos to use a product that is supposed to be, and is generally considered to be, very easy to use by many sighted people. It would be the ultimate irony if, having conceded the necessity of functional accessibility, I went back to Windows and used my Macs exclusively as servers, but somehow I can see that actually happening. Even within the general Apple ecosystem there are strange paradoxes, for instance iTunes for Windows is actually more functional than the equivalent macOS apps, even though the experience of using them is pretty dreadful, but especially with Windows screen readers. It ends up being very much a case of picking the lesser evil.

But, yeah. Enjoy. :)

Regarding the modal dialogs, do you have an example page where this occurs? I've never had problems with so-called web dialogs, if you mean this kind of dialogs.

See this WebKit bug. It depends on how the dialog is implemented but basically if aria-modal is true (and div role is not dialog, which appears to cancel that effect, strangely) then you can expect breakage. Now that more dialogs are using this aria role (presumably a consequence of toolkits including it) it's having greater effects.