Voice control is still pretty new. As I said in a thread I posted a few days ago, I'm really enjoying the Google Home. I think the biggest thing going for it is the design decision not to include a screen. Siri on IOS, or the assistant on Android phones, often just fall back on using the screen to display complex information. The Google Home doesn't have that luxury, so developers have had to think much more carefully about the best way to deliver spoken information. This is going to be a huge win for blind folks overall. Up until now, even when sighted developers have made apps accessible, they've never really thought about the best way to deliver information through voice. It's a completely different UI, with different advantages and disadvantages.

The biggest thing I want the Google Home to do is keep working on how to deliver more complex information by voice. For example, when I type some questions into google search, it will return a table of information. When I ask Google Home the exact same question, she just can't answer. The developers need to do more thinking about how best to distill the information from that table into spoken output.

Similarly, I want the Google Home to get better and better at more complex questions. The other day, for example, I wanted to know what two rivers intersected in a particular town. Google Home could tell me about the town from Wikipedia, could give me the population, but just couldn't pull out the information I wanted. So I had to go to my computer, pull up the Wikipedia article, and do a search for the word river. Google had this information, both from Google Maps, and from Wikipedia. I think it's just a matter of time before it can answer more complicated questions like this. And when it can, that's going to be a huge savings. No more searching through long articles to get the information I need; just ask the question, and get a quick, short, spoken answer. For the first time, this will give us something similar to a sighted person's ability to skim a website for information.

The last thing that would be nice is a "pause" or "slow down" feature. After getting the Google Home to give me the address to a business, I'd like to be able to say something like "OK Google, I want to note that address down." When a human gives you an address, phone number, etc, they naturally pause, and give you a minute to write each part down, and confirm you've got it. Google Home still just spits the address out in a long string. When she knows I'm taking notes, she could say something like "OK, that's 21 Main Street," and then start listening for me to say things like "OK, Yes, Uh-huh" or whatever before continuing with the city, then the zip code, etc. She could also respond to "How do you spell that?" for streets, cities, etc. This would make dealing with her a bit more like dealing with a real human, who understands the context of what you're doing with the information, and that the context matters in how fast they should give you the info, if they should spell unfamiliar names, etc.

I like voiceover on iOS and Mac. I really can't think of any features that screenreaders really need

The ability to understand accents. I've met some people trying to use Siri with thick accents, and Siri has no clue what they say.

[deleted]