Without a phone in hand, information seems kind of sparse. The Narrator in desktop Windows doesn't seem all that impressive (wouldn't want to kill the 3rd-pary screen reader market, I guess).
From a development point of view, devs still need to add accessibility labels to their apps and use the other accessibility APIs available. I have no idea how easy or hard that is on Windows Phone. iOS is easy enough that a dev would have to be borderline negligent not to type a few descriptive labels while they're doing the UI. Android, not too bad but not as much infrastructure as iOS (I'll admit to being a much weaker Android than iOS dev, so maybe I've missed something) for gestures and the like.
Point being, even if the WinPhone accessibility APIs are fully fleshed out, 3rd party apps still need to support it, and I haven't seen a big push from Microsoft to do so. Contrast to iOS where devs get the accessibility spiel at WWDC, and Apple seems to push it elsewhere. Android, meh, seems kind of tacked on IMO, though I guess it works well enough (fully-sighted user here, so I'm not the most qualified to say, and I'd be interested to know how the Nexus 7 works out for you).
Sometime in the next week I should get a chance to play with a friend's phone that I'm sure he'll have upgraded to 8.1. Again, I'm fully-sighted but have been the "accessibility guy" across several companies (including an accessibility lead at MSFT), so I at least know what to look for. I'll ping you if I have anything to report.
Appreciate any info you get when you get a chance to play with their phone. The Nexus 7 is a bit below where the iPhone 3GS was when it was released. I’m not sure how much of that is me having a harder time with larger screen devices though, I find an iPad much more difficult to use then my iPhone. I’m probably going to get a used Nexus 4 dirt cheap and will actually try using it as my primary phone for a while. I should really see if the newest version of Android Studio is still completely inaccessible. One nice thing about Android is that it is quite easy to program for when blind using the Eclipse based tools.
Wow, I just tried the latest build of Android Studio (0.5.something) out of idle curiosity. Even on Mac OS X, which from my POV has great accessibility at the OS level, you just get big containers without any visibility to the items inside. As a sighted user, this annoys me as well because that (usually) means there are no keyboard shortcuts to work within those containers. Contrast to Xcode, where there's a shortcut for everything and VoiceOver seems to be much more informative.
For all my complaints about Eclipse, you're right, it seems to be much better for accessibility than Android Studio. Too bad sometime down the road Google is going to switch to Android Studio (granted, Android Studio is worlds better in a lot of other respects). Though at the rate they're going, it should be a while. :-)
From a development point of view, devs still need to add accessibility labels to their apps and use the other accessibility APIs available. I have no idea how easy or hard that is on Windows Phone. iOS is easy enough that a dev would have to be borderline negligent not to type a few descriptive labels while they're doing the UI. Android, not too bad but not as much infrastructure as iOS (I'll admit to being a much weaker Android than iOS dev, so maybe I've missed something) for gestures and the like.
Point being, even if the WinPhone accessibility APIs are fully fleshed out, 3rd party apps still need to support it, and I haven't seen a big push from Microsoft to do so. Contrast to iOS where devs get the accessibility spiel at WWDC, and Apple seems to push it elsewhere. Android, meh, seems kind of tacked on IMO, though I guess it works well enough (fully-sighted user here, so I'm not the most qualified to say, and I'd be interested to know how the Nexus 7 works out for you).
Sometime in the next week I should get a chance to play with a friend's phone that I'm sure he'll have upgraded to 8.1. Again, I'm fully-sighted but have been the "accessibility guy" across several companies (including an accessibility lead at MSFT), so I at least know what to look for. I'll ping you if I have anything to report.