When a dialogue box opens, Narrator only reads the first control that gains focus. While it's possible to use the Narrator cursor to read the text in the dialogue, I would like an option to specify whether Narrator automatically reads the contents of these dialogues when they appear. Along the same lines, I'd also like to see automatic reading of notifications when they are received. Currently, I hear a little **** sound when something new pops up. I have to go into the action center and manually view the alert. It would be nice to be told what the notification was right away. If it wasn't important, I could just silence pseech with control and keep going.

Windows 10 Movies & TV supports SRT files. This is nice, but it's not really enough.
I know there's no end of anime folks asking for subtitle support in MKV files, so you can ask them what formats are prevalent there.
In the MP4 container, there's space for multiple "sbtl:tx3g" streams (aka "mov_text") to carry subtitles / captions, either to provide access for people who are deaf or hard of hearing, or to support multiple languages. You already support multiple audio streams, you already support subtitles in external SRT files, subtitles in alternate streams should be a small addition to support. Also, ideally, support MP4 sbtl:tx3g subtitles in Windows Media Player.

The following problems in relation to Azure Portal accessibility have been encountered when using this UI with Jaws for windows 18 and NVDA 2016. Both Internet Explorer, Firefox and Chrome were also tested.

1. the link to add subnets is not properly labeled.
2. It is no longer possible to select the location.
3. When pressinbg E, instead of looking for the last edit field Jaws telling me I'm not in a table.
4. Drop downs are not accessible. The lookup window isn't accessible.
5. Adding a site to site connection on the virtual network gateway. Unable to select a local network gateway. The blade appears blank.
Adding a site to site connection on the virtual network gateway. Unable to select a local network gateway. The blade appears blank.

I recently purchased an Xbox console. Here are my thoughts on the experiences so far and I think an underlying theme of where accessibility breaks and needs to improve. I am really passionate about making this a good console for users, so opening dialog up about this is critical. That's why I was super excited when I purchased my console a few weeks ago, a moment where I was confident that at least I'm getting some out-of-box accessibility solutions and a company dedicated to their mission.

First, the biggest issue with Narrator, as it stands, is this controller-keyboard compromise I mention in the subject line. When I first opened the console and set it up, I used windows + enter on the keyboard to start up Narrator. I wish I would have tried the controller, but alas, I didn't. Still, I switched quickly to using it because I remembered how the navigation works with each stick / scrolling with the trigger buttons, so I thought it would work easier.
Boy was I wrong. The problem is that the navigation done by this d-pad on the controller is different than your standard tab and shift-tab action. I believe there were dialogs, like the wi-fi selection, where I could not use the controller but had to rely on the keyboard. In any web content, such as when you're creating a live gamertag for the first time and are asked questions, navigation with the stick is not possible. I had to switch to the keyboard because I also wanted to type quicker, and noticed this.
Then we get to the main Xbox interface. When you tab and shift-tab in there, Narrator will sputter and just can't handle itself. Alt+tabbing works, and I know there are shortcuts on the keyboard for multitasking. I have used these before and of course Narrator includes a set of its own commands for things like speech rate changing. Again, changing speech rate is not possible from the controller as of now.
Any kind of text content, such as static text on a label in a dialog, cannot be read or explored with the controller alone.
Why should those who are users of the screen reader rely so much on this disjointed interaction model between keyboard and controller? Should we be required to use a keyboard just because a screen reader is in need of more commands which would be harder to map to a 5-10 function input device? (Note: I didn't count this, but logically thinking...) For which commands should keyboard interaction be retained? For example, I would not expect to change verbosity levels on the controller or have special table reading commands. Putting performance issues aside with Narrator (and why some UWP apps like Pandora crash after Narrator is running but not before,) this is a huge issue which, in my opinion, plagues accessibility forward.
The closed-nature of the Xbox insider program means getting access to this seems difficult at the moment, but I'd love dialog from anyone at Microsoft, and especially the community of those using this product, on what their thoughts are. I'm thrilled that Microsoft has a chance to be innovative in this space, being essentially the first console to provide a full-level screen reader experience. I am 100% in no doubt that the engineers and teams there are aware of this problem to some degree, so perhaps having more insight on the experience from a user could bring greater clarity (and urgency) to that situation. :)

With respect-
Tomi

A reputable company Microsoft, I apologize in advance for not being an exact translation (if he is), so I really do not know much English. I have just a few moments ago I saw your creation HoloLens, and I was deeply impressed by this device. And I would like to tell you about a text concept of absolute immersion in virtual reality devices.
It is a capsule full immersion, in which a person falls into a trance or dream, using neural helmet that reads brain signals and converts to a digital signal, creating a virtual reality of total immersion, in which a man can fully move, though his body is asleep. Yes, I know that such a device is on the verge of science fiction, but judge for yourself that just ten years ago, over those who thought about glasses virtual reality, were considered mad and eccentric. But augmented reality as HoloLens already developed, presenting a digital interface that syncs with elements of reality. So, such a capsule not only gives access to the full immersion, but it does so the same will allow people with disabilities to feel like full control over the capsule. But apart from this reading technology and processing signals of neurons allow sozdovat implants of the new generation! Such prostheses are head and shoulders above its predecessor in all respects.
I'm already used to think a lot of technology, starting with the usual microSD adapter on the Universal Serial Bus and wireless headphones, and ending with virtual and augmented reality. Then I thought that the imagination of a little boy no one will Iteresno, and I was afraid of being ridiculed. And all of what I once fantasized already created proxy. And HoloLens becomes the last straw bowl because I missed a chance to leave a mark. And being a dreamer and a theorist, I have neither the knowledge nor the experience in this field. I am writing this letter in the hope that my ideas once they see the light.