What’s coming in Windows 10 accessibility | Windows Experience Blog(blogs.windows.com)
submitted by MostlyBlindGamer
devinprater4 points3y ago
If only Apple made this kind of effort to reach out to the community. Shoot, even Google does it with their Chrome accessibility update emails on their mailinglist. I mean, I know, Mac would have like, one small thing every year, maybe even experimental, but shoot, something would be good.
I keep hoping that Microsoft will, through trial and much effort, exceed Apple in attention to detail, and I'd just be able to get rid of my Apple stuff. An open, honest as possible, and attentive company is much better than a greedy, quiet one whose "courage" is taking features away.
MostlyBlindGamer [OP]2 points3y ago
Microsoft has been changing their attitude a lot recently and your is a good example of that.
Apple did recently come out with the Hover Text feature which I find handy.
Google doesn't seem to be very responsible when it comes to improving TalkBack.
They all have their pros and cons and we still don't have access toa single platform that works perfectly, but progress does happen. We have to keep the pressure up.
bradley222 points3y ago
I’ll always use NVDA but narrater is getting better and better, I only hope you can change the read all page thing.
MostlyBlindGamer [OP]1 points3y ago
I've noticed Microsoft people are very responsive at r/Windows10 so I think you might have some lock if you find them there and mention it.
bradley222 points3y ago
Thanks.
DariusA922 points3y ago
The thing that stops me from using Narrator is that it doesn't seem to support 32 bit SAPI5 engines on a 64 bit system. I use a 32 bit TTS engine for my language and Narrator doesn't recognize it. For English, I'm only comfortable with Eloquence and the version code factory has is too expensive for me.
Also, I think one thing that would make Narrator truely great is the ability to write add-ons for it. NVDA on its own isn't all that great, but the many add-ons that are available for it makes it a good screen reader.
MostlyBlindGamer [OP]2 points3y ago
Windows is overall a mess with the 32 vs 64 bit thing. If you're into self torture, try setting up Android Studio to work with NVDA
DariusA922 points3y ago
Exactly. Really, I like Windows, but these days it seems that Microsoft has given Windows to a bunch of high-schoolers who have learned programming from online tutorials, and told them to go wild.
Is that really such a torture? I thought about learning Java and doing some Android programming, but weren't in the mood for messing around for hours and hours with IDE, packages, errors, and what have you.
MostlyBlindGamer [OP]2 points3y ago
I think their main problem is Martinsburg backwards compatible basically all the way to DOS. That doesn't match up with today's high brochure l velocity development style.
You need to install and coordinate 32 and 64 bit versions of the JRE and Java SDK and configure a few things. It's not undoable, but it's enough of a headache that I only use it on Windows if I can get away with magnification.
On the Mac, there's only 64 bit now and VoiceOver can handle it, so it's much more of a seamless experience.
You should still give it a shot if you really want to build some apps or just contribute to your favorite open source ones.
MostlyBlindGamer [OP]2 points3y ago
The main points are more options for cursor size and color and updates to Magnifier and to Narrator.
Nothing extraordinary, I'd say, but it's always nice to get incremental updates.
Our mission is to provide everyone with access to large- scale community websites for the good of humanity. Without ads, without tracking, without greed.