If Freedom Scientific had spent less time whining …
Comments
65 responses to “If Freedom Scientific had spent less time whining …”
-
I’m waiting for the states to stop paying for Jaws, so they can finally either restructure or go under. #JustSayin
-
FS is dying a slow death… I say good riddance.
-
Not going to happen. There are too many employers who don’t allow open source software on their systems. Plus, there’s still the feds who pay for and use it.
-
Yeah I’m not going to miss them either. Have feet, will dance on grave.
-
Amen to that.
-
Don’t get me wrong. When they go under, I will be the first to dance on their grave and hand out smors cooked over the healthy forest fire. But states won’t quit buying.
-
I know, but it’s nice to dream.
-
They’ll go down *in spite of* state money. They’ll probably end up being the Blackberry of screen readers.
-
And in reality, that would be more satisfying.
-
What makes you think they’ll go down in spite of state money? Is the consolidation in the industry perhaps what makes you think this will happen?
-
For me, it’s in part that in their pride they got rid of the better screen reader. And also where this thread started, that them not working with companies like Mozilla like NVDA is has caused the need for their users to use Firefox ESR.
-
If you’re going to burn them, at least try to take the video driver as a souvenir 😛
-
Do you know what will eventually make them go down? Besides people switching to NVDA?
-
Microsoft closing security holes, and built-in screen readers.
-
Yeah, that’ll do it. Narrator is catching up fast to the third party ones.
-
It’s run by ego-ridden twat males. If NVDA worked with my transcription software I’d probably not ever renew my SMA ever ever ever. As it is, I hate giving it to them every year. If I could afford both I’d turn it around and donate it to them; though I confess that if NVDA ever charged, I’d view it as money better spent than giving it to Freedom. Meanwhile, the new firefox is supposed to work with 2018, and it’s still incredibly slow making it necessary to run ESR. It’s stupid!
-
And if they’d payed attention, Java’s Accessibility API would be supported. *sighs* 2,000 € and it doesn’t support the accessibility API of one of the most popular cross platform programming languages.
-
I hear you on needing to use Jaws for work. A lot of people are in that position. Also I hear you on Freedom Scientific being run by egotistical little twots.
-
Yeah. That’s tragic, to say the least.
-
Then again: Apple: Swift isn’t even (comfortably) usable on anything else but OS x. Python? The accessibility API package is only available on Linux. I feel like puking nonstop.#AccessibilityForDevelopers is really, REALLY poor, from my point of view.
-
None of this is wrong.
-
Sometimes I wonder what I could’ve acomplished since 2016 if one of these languages would’ve been a bit more accessible for me as developer…
But when I’m done with my final graduation I can finally start to use NVDA. Hopefully at least Java will work then. -
Also will soon have a mac course to start develop apps in xcode. And I’ll try to get Linux, Orca, BRLTTY. Just a lot to learn, but I can make it. 😉
-
I just try to tell myself that it’s advantageous because I get a deduction on my taxes. 😀
-
I use Jaws only when absolutely necessary. And by “Absolutely necessary”, I mean I’d better not be able to use at least object nav to get around and manipulate the screen. Because if I can use object nav, I’m not using Jaws.
-
Someone needs to add native Remote Desktop and Citrix support to NVDA. NVDA Remote can’t be used through my employer’s proxy, I’m betting.
-
How about, if they stopped throwing the NVDA community as a collective under the bus and take their lead. Accessibility is a right, not a privilege. A sighted person can walk up to a computer and use it. Why should we have to shell out thousands to use our computers?
-
We don’t want Freedom Scientific leading the NVDA community. They are, as expected, pretty anti-open-source.
-
That’s my point. I’m saying that if FS wants to stay in the market, they’re going to have to change there attitudes… quick!
-
NVDA still can’t support SecureCRT, Jamie did add limited support for me once long ago, but it was heavily dependent on a particular version of a dll they were using which changed with every major release of SecureCRT, so it broke in fairly short order. Its essential to my job, so, no NVDA for me, Plus, I hate Object Nav with a passion. I’m hesitant to entirely blame FS either, Mozilla do have a history of “my way or the highway” when it comes to accessibility support, for a long time Firefox wasn’t accessible with VoiceOver on the Mac because Mozilla wanted Apple to adopt their accessibility methodology instead of playing nice with Apple’s already well established guidelines. Blame exists on both sides.
-
that presumes a screen reader user needs to use Firefox though. For example, I’m not required to use FF for anything.
-
BEcause there’s that thing they call Google Chrome. Firefox users know what works and what doesn’t, though. On a business machine that could be slightly problematic if you have only ff and jaws on the machine, and it’s locked down tightly.
-
These changes came to Edge, they’re now in Firefox, and they’re coming to Chrome. So FS is going to have to be willing to come to the table instead of spending time grandstanding when they have no way of winning.
-
They can’t expect for progress to be haulted so they can maintain a legacy code base.
Leave a Reply