Dear Mike,
If my understanding is correct of
your message,
Please note, ever since NVDA
released as a free screen reader millions of Blind
users have got into some kind of technical or
computer literacy and use of technology.
If not still a vast majority
would not be able to access computers due to the
high cost of the commercial products.
Also, NVDA has created many job
opportunities to many Visually Impaired Persons in
several countries.
So, I urge that this should
continue as the current way it is as an open source
product and accessible to all Blind people.
People in the poor countries, and
the developing countries are mainly depending on
this screen reader. Who may be heavily using the
product, but may not be in a position or afford to
donate towards this cause.
Therefore, I kindly request to
all the developers and contributors to keep and
continue this as an open source and free product, or
at least to the people in the poor countries.
We even get the computers through
donations, under this circumstances how could we
spend hundreds or thousands of Dollars to the
commercial Screen Readers?
I live in Sri Lanka, and now even
we almost starving , under this situation cannot
think of purchasing any screen reader or anything
other than considered to be essential items.
Which some time may cost the job
of the Blind people as well, who are depending on
NVDA for their work .
So, for delay of any Add-Ons
should not deny access of a screen reader for many
Blind people.
Thank you in advance for
understanding. NVDA is a blessing to many Blind.
Ravi.
Quoting:
My own view is
that these add-ons should be updated in the Alpha
or Beta stages, not after release. Either that, or
NVDA should not keep breaking compatibility with
them.
End quote:
Amen to this.
If NVDA were a commercial
software instead of “charitable open source code”,
these practices might not be tolerated as easily.
I wish sometimes that NVDA would
“actually charge” for its software instead of hiding
behind “donations” then we could demand excellence.
It is strictly my belief that we
as a society give too much leeway to “charitable”
products.
I say these things as a “donor”
to NVDA.
No, you’re not
alone. It makes work also for the average user,
who gets their NVDA just right with add-ons, only
to find them broken in the next version.
My own view is
that these add-ons should be updated in the Alpha
or Beta stages, not after release. Either that, or
NVDA should not keep breaking compatibility with
them.
All the best
Steve
As a random interjection I find
it quite disturbing how easily add ons are losing
compatibility from one minor version to the next.
This is a trend I as a user am not a fan of. It
means more work for developers, more issues by the
end user if add ons become unsupported, or at least,
unsupported according to NVDA itself, and less time
to actually make improvements for the developers who
are already placing their doubtlessly limited and
free time into this wonderful hobby of creating
resources for NVDA to take advantage of.
I am truly curious to know what
I, as a user, am benefiting from with this so called
fragmentation. Previously add ons would work without
issue, now it’s a guessing game as to which add ons
will be disabled and stop working when I’d like to
update NVDA from, again, one minor version to the
next.
As it stands right now, I’m
running a portable version of the latest NVDA due to
the above, with my main install remaining an older
version. Am I alone in viewing this slightly
worrying trend?
Lol we got the
same answer..
Skickades från E-post för Windows
So I just got a
reply from Codefactory, to a ticket regarding
compatibility with NVDA 2022.1 that I submitted
way back in April. Below is their response:
Good morning,
We are aware that a breaking NVDA update was
released today.
We've been working on the addon, but unfortunately
our update will take a few more days to complete.
Thank you for your patience.
The Code Factory technical team.
