Whatever you say about Microsoft and the amount of overlapping technologies they have, their documentation is best in class. There's a barely supported, legacy

Whatever you say about Microsoft and the amount of overlapping technologies they have, their documentation is best in class. There's a barely supported, legacy API from Windows 2000 that is still used by some legacy screen readers to actually access whatever is on the screen. It's meticulously documented and the documentation seems maintained and up to date. Apple is the exact opposite, the API that screen readers use to communicate with web browsers isn't even mentioned anywhere. If you ever need to learn about it, the usual answer is "go Read the Safari source code and figure things out from there." It's gotten so bad that the documentation for Dotnet bindings of some Swift methods has apparently gotten better than the documentation of those methods themselves.