I was directed to come here by customer support. I had to install Windows 7 on a different hard drive just to post this! I have been a member of the "insider" program since February 14th 2015.
I have a spinal cord injury which renders my hands and arms useless. I have been disabled for 25 years. I worked with Mark Novak, at the University of Wisconsin Weisman Center, on the original Access Pack for MS-DOS and Access Pack for Windows 3.1 which is the forefather of "Ease of Access". I must use a mouthstick or voice recognition to navigate any program in any operating system. I will cut to the chase.
Windows 10 doesn't address many of the features in "ease of access". What is addressed is inconsistent. I have submitted several suggestions as to the better integration of your "ease of access" program within Windows 10 throughout it's implementation. I have placed a copy of this in the insider program, the answer desk and the Windows 10 community. I will now post it here. I usually receive a few to several individual responses with the same problem and one response from a MS rep telling me to run sfc /scannow or some such remedy wasting my time and yours. I know we are a very small portion of the users you are marketing to but we add up and you have totally missed the mark with this OS and it's peripherals in the disability community. I will address just a few of the myriad of problems I am encountering.
The worst is Microsoft prioritizing Windows Edge and then making it useless to basically all "Ease of Access" tools because of the lack of adjustability. It is very disgruntling. This includes no disabling or uninstalling and not allowing many default changes in other listed programs to get around Edge.
Sticky keys used with many keyboard shortcuts are either useless or spotty with all MS programs. i.e. Microsoft Office, Internet Explorer, EDGE etc...
Mouse Keys have changed so the pointer top speed is approximately 2/3 the speed in 8.1 and 7. The left single click (5) and double click (+) is picky where it will or won't work in Microsoft Apps.
I have tried 6 different keyboards, including a brand new Microsoft 800 on my Dell Optiplex desktop. I also have a Dell Precision M4800 laptop that I have tried the Microsoft 800 as a remote remote USB keyboard. They both have the same problems and results. Others are having the same or similar problems.
There are many more similar problems that have relegated me to using third party apps that do work with all of the ease of access tools.
Now after the latest update Mouse Keys disables itself after using it on IE 11 and attempting to use it on Edge. I must go to the accessibility app and recheck it. Any online Microsoft logon installs your password at bootup where there was none. Any assistance would be appreciated.

Apparently Microsoft just made a security decision to block any application, even a trusted screen reader, from injecting its code into any WinRT application.
This includes Windows core components like the start menu, settings app and Microsoft Edge. This also means windows store apps as well.

This greatly reduces accessibility in all these essential apps and in particular edit boxes. We are pretty much writing silently and there is no sound for when we misspelled something or when a suggestion comes up.
Microsoft is moving more and more to having all their apps and components be packaged like this, so I am scared that soon screen readers will be left with only minimal access, effectively barring blind users from competently using Windows.

There are solutions to this problem and I know NV Access has reached out to Windows about this problem, but Windows has not yet responded with a suitable alternative.

I'm not a screen reader developer, but maybe all Windows apps could be built on a back-end that exposes information screen readers need and maybe even requires proper labeling like what happens on Mac computers.
Another option is Windows have a list of screen readers and hand out access keys so they can grab the information they need. This could either happen on Windows' end or the user can choose what applications have full access to all their apps.

Regardless, this is a huge problem and I am appalled that such a major accessibility bug made it to the stable version of Windows. This really shows just how much Microsoft cares about and listens to their blind users and developers.
Again I ask Microsoft to have an official beta testing group of blind people who have a very high influence on Windows development and who can find bugs before they get released in to even the insider program. Microsoft has slowly demolished every feature that blind users love and has been actually decreasing the accessibility of windows.
Please reverse this trend!

The current command line works pretty good, but there are two major problems that showed up particularly in windows 10:
1. You need to use the review cursor to read the command line. This is OK, but not novice friendly and has always been the case.
2. When one has "speak typed characters on" or "speak typed words on" I will hear new output spelled to me rather than read normally. This is beyond aggravating!
Next, the new Bash client acts like the command line, but when using things like SSH, Nano or Vim, it acts a little strangely.
For example:
- In Nano everything is great, except when trying to read documents you open. The documents are blank. New documents are fine, but old documents are blank.
- Vim should have an option for verbosity as telling me the number of characters I am on is a little crazy. It also doesn't tell me what line I'm on when in review mode and reading the lines. Using hjkl to move around the text doesn't work either.
- SSH is what I would really love to see made amazing. It is just about there, there are just a few things that don't work very well (Note these problems are just in SSH, no where else):
1. When typing with key echo on in ssh, it has a lag. I will hear the letter half a second after I type the letter.
2. Erasing gives me no audible feedback what so ever. It is just silent when I hit backspace. I should hear the name of the character being erased.
3. Arrowing through the line gives me no audible feedback either. It should read the letters. When up arrowing to read the buffer of past typed lines I hear nothing either. I should hear the lines I typed before read to me.
4. Typing passwords gives me no feedback. I would like to hear "star" or something like that. I really like what the logon screen does now.

In windows 10, especially on the Surface devices, the ability to turn off the screen has been disabled. The old method was to press windows+p to get to projector options, then arrow up to second screen only and press enter.
There are three reasons why having a way to turn off the screen is important:
1. Privacy and safety. As a blind user, we have no idea who could be looking at our screen and if we are writing some highly personal data in a public place, then we have no way to insure someone is not looking over our shoulder and reading that data.
2. Eye fatigue. As a nearly totally blind user, my eyes start to hurt if my computer screen is the only light in the room.
3. Battery life. The screen is one of the most power intensive components on my computer and in Windows 7, I would get an extra 1-2 hours of life compared to the dimmest brightness setting.