Common controls are all accessible.
On-screen keyboard is shitty: every key must be activated before use. So typing is probably very slow.
In system tray area it could read every icon (level of network signal, battery, clocks...), but I could not find a way to open Action Centre.
Application switcher is bad, I could not find a way to use it properly. Button for closing apps works, but it's announced as generic button without text.
Accessible standard apps: Alarms, Data Sense, Internet explorer, Maps, Messaging, People hub, Phone dialer, Photo hub, Store.
Inaccessible standard apps: Battery Saver, Calculator, Calendar, Office, OneNote, SkyDrive, Skype, Storage Sense.
Standard apps where many buttons are unnamed, but blind usage is probably possible: Camera, FM Radio, Games hub, Xbox Music.
Emulator contains old versions of everything, so real phone could be different.
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.
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. :-)