65 thoughts on “If Freedom Scientific had spent less time whining …

  1. 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.

  2. 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!

  3. 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.

  4. 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.

  5. 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?

  6. 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.

  7. 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.


  • User Avatar?
  • User AvatarBarb M
  • User AvatarSalih Kunduz
  • User AvatarJakob Rosin
  • User AvatarKevin Reeves
  • User AvatarJack Swagger
  • User AvatarHeavy Metal Chainsaw
  • User AvatarWoodstock
  • User AvatarLeonid Prazdnik
  • User AvatarKieran L ??
  • User AvatarChris Smart
  • User AvatarEdnun Pourtahmasbi
  • User AvatarKatherine Moss
  • User AvatarSteve Clark
  • User AvatarBrandon Cross
  • User AvatarRuthie Rayne
  • User AvatarAmanda J. Rush


  • User AvatarJoseph King
  • User AvatarENTHooliginsAustin
  • User AvatarShane Lowe

Leave a Reply

Your email address will not be published.

This site uses Akismet to reduce spam. Learn how your comment data is processed.