Date   

Re: reducing the frequency of progress updates

 

Hi,

Actually, it is not NVDA that holds progress bar values - it says things according to what Firefox (or any app) tells it to say, more so if this is a live region (for live regions, provided that the application developer or website author is informing screen readers that live text should be announced).

Cheers,

Joseph


Re: reducing the frequency of progress updates

Brian's Mail list account
 

This same issue exists in command prompt of course, where the process finishes almost instantly but the reading goes on for an age.
I've not found any way to control either problem.
I have one web page where there are progress bars for file and total upload so the bleeping can sound most odd as can the reading. I've yet to find a way to say only read this progress bar, but not this one etc, I guess in the command prompt you can output to a text file, but not every dos based program will respect that choice either!
Brian

--
bglists@...
Sent via blueyonder.(Virgin media)
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.

----- Original Message -----
From: "Bob Cavanaugh" <cavbob1993@...>
To: <nvda@nvda.groups.io>
Sent: Monday, June 27, 2022 11:38 PM
Subject: [nvda] reducing the frequency of progress updates


Hi all,
I have changed my NVDA progress indicator from beep to speak, but am
wondering if there is a way to refine the way progress is announced.
Is there some way I can only have as many indicators announced as NVDA
can read without getting behind? For example, I just sent a file to
someone using We Transfer. As the file was uploading, NVDA would say
1% transferring, 2% transferring, 3% transferring, and on and on. If I
hit the control key at that point, it would continue to speak, but say
8% transferring, 9% transferring, etc. Is there a way for NVDA to only
give as many progress indicator outputs as it can comfortably speak?
Thanks,
Bob




Re: IMPORTANT Notice on Joseph Lee's add-ons: reducing/ending support for Windows 7, 8, 8.1 and unsupported Windows 10 feature updates effective january 2023

Brian's Mail list account
 

Thanks for the clarification. I do feel that the worries over security are over the top, but at the moment everyone seems to be taking this line of trying to stop people downloading stuff at their own risk.
I would point out that a straw poll of home users, not scientific at all, I have to say, suggests to me that many, probably about half or slightly less of them are using Windows 7 on at least one machine.

Of course there is nothing stopping them getting windows 10, but many tell me in these cash strapped days that buying new hardware merely to run Windows 11 cannot be justified, so down the line we could be seeing a similar problem with people using 10 who have no plans to go 11.
Of course even if support for 7 ends, there is really nothing to stop people still using the NVDA add ons that work and older copies of those which don't.
Brian

--
bglists@...
Sent via blueyonder.(Virgin media)
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.

----- Original Message -----
From: "Joseph Lee" <joseph.lee22590@...>
To: <nvda@nvda.groups.io>
Sent: Monday, June 27, 2022 10:04 PM
Subject: [nvda] IMPORTANT Notice on Joseph Lee's add-ons: reducing/ending support for Windows 7, 8, 8.1 and unsupported Windows 10 feature updates effective january 2023


Hello NVDA community,

Before I get into the heart of this announcement, I'm delighted to announce
that all my add-ons are compatible with NVDA 2022.2 changes. And yes, I'm
back - thank you everyone for your valuable feedback, comments, and
criticisms - I still have some residue from NVDA 2022.1 and add-ons work but
feeling a bit better after taking a break for a while.

The following notice is applicable to anyone using my add-ons (Ad-on
Updater, Windows App Essentials, future add-ons and/or add-ons awaiting new
maintainers), specifically for anyone using Windows 7, 8, 8.1, and their
server counterparts. Please do NOT take this as a statement on NVDA and
support for Windows releases (for that one, see a message from Quentin from
NV Access posted earlier this year):

Earlier this year I (Joseph Lee) announced that my add-ons will eventually
end support for Windows 7, 8, and 8.1, noting that I will provide a 60-day
notice before then. I then sent a notice in March 2022, stating that
add-ons, including ones leaving my maintenance (which there were five then)
will end support for Windows 7 and 8.x effective May 2022; I also noted that
there will be an exception, namely Add-on Updater which will support old
Windows releases as long as NVDA supports them. On paper, end of support
date was May 7, 2022 but due to various community events (namely preparing
for NVDA 2022.1), I forgot to announce that fact.

My original plan was and still is to see if anyone from the NVDA community
can take care of now unmaintained add-ons from me (Enhanced Touch Gestures,
Event Tracker, GoldWave, Resource Monitor, Sound Splitter, StationPlaylist)
with a possibility that new maintainers will release a version of these
add-ons requiring Windows 10 or later eventually (source code is ready).
However, since I haven't received messages about new maintainers (as of time
of this announcement), I am revising the plan as follows:

Effective January 2023, all of my add-ons with limited exceptions will no
longer support unsupported or soon to be unsupported Windows releases,
including Windows 7/Server 2008 R2, Windows 8/Server 2012, Windows
8.1/Server 2012 R2, and unsupported feature updates for Windows 10 and later
from the standpoint of consumers and businesses. For Windows 10, unsupported
feature updates are 1507 (build 10240), 1511 (build 10586/November Update),
1607 (build 14393/Anniversary Update), 1703 (build 15063/Creators Update),
1709 (build 16299/Fall Creators Update), 1803 (build 17134/April 2018
Update), 1809 (build 17763/October 2018 Update), 1903 (build 18362/May 2019
Update), 1909 (build 18363/November 2019 Update), 2004 (build 19041/May 2020
Update), and from December 2022 onwards, 21H1 (build 19043/May 2021 Update);
although consumer support for 20H2 (build 19042/October 2020 Update) ended
in May 2022, business support ends in May 2023, thus it is still a supported
Windows 10 feature update. The list of supported and unsupported Windows
releases can change based on Windows product lifecycle schedule. This policy
applies to current and future add-ons, and if circumstances warrant it, any
add-ons I have maintained in the past that are not being maintained by the
community as of January 2023 (see notes).

Notes:

1. The only exception will be Add-on Updater which will have reduced
functionality on unsupported Windows releases so that it can provide a
"nightlight" (minimal service for emergency and special uses) and to keep my
promise of supporting old Windows releases as long as NVDA itself supports
them. That is, even though updates for Ad-on Updater will be compatible with
unsupported releases, new features will be exclusive to supported Windows
releases; for users of older Windows releases, consider this a "feature
freeze" notice. As for what constitutes nightlight functionality, I expect
that you will be able to at least check for, download, and install add-on
updates and tell Add-on Updater to not check for some add-on updates;
details will be communicated soon. One thing is certain: unless things
change, Add-on Updater will continue to work on unsupported Windows releases
but remember that you will be on your own due to security risks associated
with downloading data from the Internet; PROCEED WITH CAUTION!
2. Windows App Essentials supports Windows 10 and 11 feature updates
that are actively supported for consumers (as of time of this writing,
Windows 10 Version 21H1, 21H2 (build 19044/November 2021 Update), Windows
Server 2022 (build 20348), Windows 11 Version 21H2 (build 22000)), with the
add-on ending support for a given feature update prior to end of consumer
support from Microsoft (for example, Windows App Essentials will end support
for Windows 10 Version 21H1 by September 2022, three months prior to
Microsoft ending support for it (December), and support for Windows 10
Version 21H2 from the add-on is scheduled to end in early 2023 prior to end
of consumer-level support in June 2023).
3. The following add-ons are no longer (actively) maintained by me as
of time of this post: Enhanced Touch Gestures, Event Tracker, GoldWave,
Resource Monitor, Sound Splitter, StationPlaylist. If no-one volunteers to
maintain them by January 2023, the unsupported Windows release policy will
apply to them as well - that is, a version of these add-ons will be released
that will not install on unsupported Windows releases.



Frequently asked questions:



Q. Does this mean NVDA itself will end support for unsupported Windows
releases?

No. NV Access noted that NVDA will support Windows 7, 8, 8.1 and other old
releases.



Q. What about add-ons such as Control Usage Assistant?

Add-ons such as Control Usage Assistant (formerly maintained by me) have new
maintainers, therefore this policy notice does not apply to them.



Q. Can I modify future add-on releases for use on unsupported Windows
releases?

Yes and no. Yes you can view and modify add-ons so they can work on
unsupported releases. At the same time, for some add-ons, supporting legacy
Windows releases will require extensive edits to the add-on source code as
legacy Windows code were removed for some add-ons in March 2022.



Q. Why is using Add-on Updater on unsupported Windows releases a potential
security risk?

At its core, Add-on Updater downloads data from the Internet. Therefore, it
might be possible that add-on hosting repositories can be compromised,
leading to distribution of malicious add-ons. The add-ons community takes
add-on security seriously, particularly when it comes to distribution
channels.



Q. Does this mean future add-ons from Joseph will not support old Windows
releases?

Yes. While the policy takes full effect in January 2023, you can assume that
new add-ons I (Joseph Lee) may publish in 2022 will require Windows 10
Version 21H1 or later.



Q. Do you have plans to release updates for unmaintained add-ons prior to
the policy taking effect in January 2023?

For Enhanced Touch Gestures, Event Tracker, GoldWave, Resource Monitor,
Sound Splitter, and StationPlaylist, I have no plans to release updates in
2022; rather, releasing updates is close to impossible as these add-ons no
longer support old Windows releases at the source code level.



Q. Wait, the just announced policy sounds similar to the feature update
support policy for Windows App Essentials add-on.

In some ways, yes. The difference is that Windows App Essentials support
Windows 10 and later whereas other add-ons support old Windows releases such
as Windows 7.



Q. Why January 2023?

This is when support for Windows 7 and 8.1 will end for most users (extended
security updates for Windows 7, extended support for Windows 8.1; Windows 8
is end of life as of January 2016).



Q. Does this policy apply to Windows Server releases?

Yes. While some Windows 10 releases have a server counterpart, they (2016,
2019, 2022) are still supported by Microsoft.



Q. What if I'm using Windows 10 Enterprise long-term servicing
branch/channel (LTSB/LTSC) releases?

Since this edition is meant for mission-critical devices, I and my add-ons
do not support this scenario. Windows App Essentials add-on itself does not
support this configuration either.



The key takeaway is this: if you can, please upgrade to supported Windows
releases as soon as possible. Feel free to contact me if you have additional
questions or comments.

Cheers,

Joseph


Re: reducing the frequency of progress updates

Luke Davis
 

On Jun 27, Tyler Spivey via groups.io wrote:

This would be accurate if it was a real progress bar. I suspect it's a live region.
Ah, good catch. I clearly wasn't thinking.

Luke


Re: reducing the frequency of progress updates

Bob Cavanaugh
 

I use Firefox, so that may be the difference. The other instance I
notice this in Firefox is when downloading a file. Now that Firefox
opens the downloads panel, it says downloading the filename, progress,
and time remaining. Currently, NVDA seems to update the progress every
tenth of a megabyte, but if I hit control, it jumps forward quite a
bit. It seems like in both instances, NVDA holds the progress
indicator in its speech buffer, and announces it as often as it can. I
wonder if there's a way we can get it to not do that, and only
announce progress as close to live as it can?

On 6/27/22, Tyler Spivey via groups.io <tspivey@...> wrote:
This would be accurate if it was a real progress bar. I suspect it's a
live region.
The default percentage for speak is 10%, and it doesn't say transferring
at the end.

However, I couldn't reproduce this. I went to WeTransfer and selected a
file, but uploading gave me no automatic progress bar in Chrome.


On 6/27/2022 4:31 PM, Luke Davis wrote:
Bob Cavanaugh wrote:

Is there a way for NVDA to only give as many progress indicator
outputs as it can comfortably speak?
NVDA doesn't know what it can comfortably speak, because it doesn't know
how long the progress bar is.

I think one of two things could be done.

1. If we were to make progress bar announcements interruptible, NVDA
could cancel the speech of the current percentage, and replace it with a
new percentage when the bar is recalculated.  However, in the situation
you described, I think what you would end up with is a bunch of
partially started speech fragments that never complete. It may never be
able to finish speaking a full digit, just a bunch of stuttering
gibberish until the bar either bogs down, or completes.

Is that an acceptable outcome? I suspect not.

2. Alternatively, NVDA could try to monitor the speed at which the bar
is progressing, and assume that in the future, it will continue at that
rate. It would then have to adapt its granularity to the speed of the
bar. In other words, if it's taking fifteen minutes, then announcing
single percentages would be fine. But if it's taking 15 seconds, only
announcing 20%, 50%, and maybe 80%, would be sufficient.

That would require rather a bit of computational guesswork, and coverage
for cases where the bar suddenly changed speed as they often do, but I
can imagine how to pull it off. I couldn't find anyone asking for this
on GitHub.

If one of those is what you want, I suggest you put in a feature request.

3. Well okay there is one more thing: one of NVDA's undocumented
settings can help you here, if you don't mind ini file twiddling. Take a
look at Brian Gaff's comment in the below.
Https://github.com/nvaccess/nvda/issues/5031

Luke










Re: reducing the frequency of progress updates

Tyler Spivey
 

This would be accurate if it was a real progress bar. I suspect it's a live region.
The default percentage for speak is 10%, and it doesn't say transferring at the end.

However, I couldn't reproduce this. I went to WeTransfer and selected a file, but uploading gave me no automatic progress bar in Chrome.

On 6/27/2022 4:31 PM, Luke Davis wrote:
Bob Cavanaugh wrote:

Is there a way for NVDA to only give as many progress indicator outputs as it can comfortably speak?
NVDA doesn't know what it can comfortably speak, because it doesn't know how long the progress bar is.
I think one of two things could be done.
1. If we were to make progress bar announcements interruptible, NVDA could cancel the speech of the current percentage, and replace it with a new percentage when the bar is recalculated.  However, in the situation you described, I think what you would end up with is a bunch of partially started speech fragments that never complete. It may never be able to finish speaking a full digit, just a bunch of stuttering gibberish until the bar either bogs down, or completes.
Is that an acceptable outcome? I suspect not.
2. Alternatively, NVDA could try to monitor the speed at which the bar is progressing, and assume that in the future, it will continue at that rate. It would then have to adapt its granularity to the speed of the bar. In other words, if it's taking fifteen minutes, then announcing single percentages would be fine. But if it's taking 15 seconds, only announcing 20%, 50%, and maybe 80%, would be sufficient.
That would require rather a bit of computational guesswork, and coverage for cases where the bar suddenly changed speed as they often do, but I can imagine how to pull it off. I couldn't find anyone asking for this on GitHub.
If one of those is what you want, I suggest you put in a feature request.
3. Well okay there is one more thing: one of NVDA's undocumented settings can help you here, if you don't mind ini file twiddling. Take a look at Brian Gaff's comment in the below.
Https://github.com/nvaccess/nvda/issues/5031
Luke


Re: reducing the frequency of progress updates

Luke Davis
 

Bob Cavanaugh wrote:

Is there a way for NVDA to only give as many progress indicator outputs as it can comfortably speak?
NVDA doesn't know what it can comfortably speak, because it doesn't know how long the progress bar is.

I think one of two things could be done.

1. If we were to make progress bar announcements interruptible, NVDA could cancel the speech of the current percentage, and replace it with a new percentage when the bar is recalculated. However, in the situation you described, I think what you would end up with is a bunch of partially started speech fragments that never complete. It may never be able to finish speaking a full digit, just a bunch of stuttering gibberish until the bar either bogs down, or completes.

Is that an acceptable outcome? I suspect not.

2. Alternatively, NVDA could try to monitor the speed at which the bar is progressing, and assume that in the future, it will continue at that rate. It would then have to adapt its granularity to the speed of the bar. In other words, if it's taking fifteen minutes, then announcing single percentages would be fine. But if it's taking 15 seconds, only announcing 20%, 50%, and maybe 80%, would be sufficient.

That would require rather a bit of computational guesswork, and coverage for cases where the bar suddenly changed speed as they often do, but I can imagine how to pull it off. I couldn't find anyone asking for this on GitHub.

If one of those is what you want, I suggest you put in a feature request.

3. Well okay there is one more thing: one of NVDA's undocumented settings can help you here, if you don't mind ini file twiddling. Take a look at Brian Gaff's comment in the below.
Https://github.com/nvaccess/nvda/issues/5031

Luke


reducing the frequency of progress updates

Bob Cavanaugh
 

Hi all,
I have changed my NVDA progress indicator from beep to speak, but am
wondering if there is a way to refine the way progress is announced.
Is there some way I can only have as many indicators announced as NVDA
can read without getting behind? For example, I just sent a file to
someone using We Transfer. As the file was uploading, NVDA would say
1% transferring, 2% transferring, 3% transferring, and on and on. If I
hit the control key at that point, it would continue to speak, but say
8% transferring, 9% transferring, etc. Is there a way for NVDA to only
give as many progress indicator outputs as it can comfortably speak?
Thanks,
Bob


Re: TesseractOCR add-on

Rui Fontes
 

Yes, that is the major reason to change to 32-bit...


Best regards,

Rui Fontes
NVDA portuguese team


Às 21:59 de 27/06/2022, mk360 escreveu:

Hi,

The change To Tesseract 5.1 32 b implies that it will work in 32 bits systems?

Regards,

mk.

El 27/06/2022 a las 16:04, Rui Fontes escribió:
Hello!


The new version already have it!

https://github.com/ruifontes/tesseractOCR/releases/download/2022.06.27/tesseractOCR-2022.06.27.nvda-addon

Changes:

- Updated Tesseract from version 5.0 Alpha (64-bit) to 5.1 (32-bit);
- Added several more recognition languages;
- Introduced the option to select a second language to be used in OCR of documents with multiple languages and a button to forget it;
- Introduced a new document type, "With auto-orientation", that allows the OCR engine to rotate the image as necessary;
- Introduced beeps to signal the add-on is working;
- Corrected code to avoid the non population of the download languages combobox;
- Corrected a problem with controlTypes roles preventing compatibility with NVDA 2020.4;
- Added russian translation.

Best regards,

Rui Fontes
NVDA portuguese team



Às 14:11 de 01/06/2022, Kakarla Nageswaraiah escreveu:
Hello,
I didn't find Telugu language.
Will they add in future?
Thanks and regards.


On 6/1/22, Ravindran V.S. <ravivssl@...> wrote:
Hi Rui,
I have tried this add-on and still could not succeed with the OCR with it.
If this list permits, here, if not would like to have a chat off line about
the usage of this OCR Add-on please.
Let me know your convenience.
Thanks,
Ravi. ..

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Pranav Lal
Sent: Tuesday, May 31, 2022 10:22 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] TesseractOCR add-on

Hi Rui,

I hear you and thanks for the comparison.

Pranav



















IMPORTANT Notice on Joseph Lee's add-ons: reducing/ending support for Windows 7, 8, 8.1 and unsupported Windows 10 feature updates effective january 2023

 

Hello NVDA community,

Before I get into the heart of this announcement, I’m delighted to announce that all my add-ons are compatible with NVDA 2022.2 changes. And yes, I’m back – thank you everyone for your valuable feedback, comments, and criticisms – I still have some residue from NVDA 2022.1 and add-ons work but feeling a bit better after taking a break for a while.

The following notice is applicable to anyone using my add-ons (Ad-on Updater, Windows App Essentials, future add-ons and/or add-ons awaiting new maintainers), specifically for anyone using Windows 7, 8, 8.1, and their server counterparts. Please do NOT take this as a statement on NVDA and support for Windows releases (for that one, see a message from Quentin from NV Access posted earlier this year):

Earlier this year I (Joseph Lee) announced that my add-ons will eventually end support for Windows 7, 8, and 8.1, noting that I will provide a 60-day notice before then. I then sent a notice in March 2022, stating that add-ons, including ones leaving my maintenance (which there were five then) will end support for Windows 7 and 8.x effective May 2022; I also noted that there will be an exception, namely Add-on Updater which will support old Windows releases as long as NVDA supports them. On paper, end of support date was May 7, 2022 but due to various community events (namely preparing for NVDA 2022.1), I forgot to announce that fact.

My original plan was and still is to see if anyone from the NVDA community can take care of now unmaintained add-ons from me (Enhanced Touch Gestures, Event Tracker, GoldWave, Resource Monitor, Sound Splitter, StationPlaylist) with a possibility that new maintainers will release a version of these add-ons requiring Windows 10 or later eventually (source code is ready). However, since I haven’t received messages about new maintainers (as of time of this announcement), I am revising the plan as follows:

Effective January 2023, all of my add-ons with limited exceptions will no longer support unsupported or soon to be unsupported Windows releases, including Windows 7/Server 2008 R2, Windows 8/Server 2012, Windows 8.1/Server 2012 R2, and unsupported feature updates for Windows 10 and later from the standpoint of consumers and businesses. For Windows 10, unsupported feature updates are 1507 (build 10240), 1511 (build 10586/November Update), 1607 (build 14393/Anniversary Update), 1703 (build 15063/Creators Update), 1709 (build 16299/Fall Creators Update), 1803 (build 17134/April 2018 Update), 1809 (build 17763/October 2018 Update), 1903 (build 18362/May 2019 Update), 1909 (build 18363/November 2019 Update), 2004 (build 19041/May 2020 Update), and from December 2022 onwards, 21H1 (build 19043/May 2021 Update); although consumer support for 20H2 (build 19042/October 2020 Update) ended in May 2022, business support ends in May 2023, thus it is still a supported Windows 10 feature update. The list of supported and unsupported Windows releases can change based on Windows product lifecycle schedule. This policy applies to current and future add-ons, and if circumstances warrant it, any add-ons I have maintained in the past that are not being maintained by the community as of January 2023 (see notes).

Notes:

  1. The only exception will be Add-on Updater which will have reduced functionality on unsupported Windows releases so that it can provide a “nightlight” (minimal service for emergency and special uses) and to keep my promise of supporting old Windows releases as long as NVDA itself supports them. That is, even though updates for Ad-on Updater will be compatible with unsupported releases, new features will be exclusive to supported Windows releases; for users of older Windows releases, consider this a “feature freeze” notice. As for what constitutes nightlight functionality, I expect that you will be able to at least check for, download, and install add-on updates and tell Add-on Updater to not check for some add-on updates; details will be communicated soon. One thing is certain: unless things change, Add-on Updater will continue to work on unsupported Windows releases but remember that you will be on your own due to security risks associated with downloading data from the Internet; PROCEED WITH CAUTION!
  2. Windows App Essentials supports Windows 10 and 11 feature updates that are actively supported for consumers (as of time of this writing, Windows 10 Version 21H1, 21H2 (build 19044/November 2021 Update), Windows Server 2022 (build 20348), Windows 11 Version 21H2 (build 22000)), with the add-on ending support for a given feature update prior to end of consumer support from Microsoft (for example, Windows App Essentials will end support for Windows 10 Version 21H1 by September 2022, three months prior to Microsoft ending support for it (December), and support for Windows 10 Version 21H2 from the add-on is scheduled to end in early 2023 prior to end of consumer-level support in June 2023).
  3. The following add-ons are no longer (actively) maintained by me as of time of this post: Enhanced Touch Gestures, Event Tracker, GoldWave, Resource Monitor, Sound Splitter, StationPlaylist. If no-one volunteers to maintain them by January 2023, the unsupported Windows release policy will apply to them as well – that is, a version of these add-ons will be released that will not install on unsupported Windows releases.

 

Frequently asked questions:

 

Q. Does this mean NVDA itself will end support for unsupported Windows releases?

No. NV Access noted that NVDA will support Windows 7, 8, 8.1 and other old releases.

 

Q. What about add-ons such as Control Usage Assistant?

Add-ons such as Control Usage Assistant (formerly maintained by me) have new maintainers, therefore this policy notice does not apply to them.

 

Q. Can I modify future add-on releases for use on unsupported Windows releases?

Yes and no. Yes you can view and modify add-ons so they can work on unsupported releases. At the same time, for some add-ons, supporting legacy Windows releases will require extensive edits to the add-on source code as legacy Windows code were removed for some add-ons in March 2022.

 

Q. Why is using Add-on Updater on unsupported Windows releases a potential security risk?

At its core, Add-on Updater downloads data from the Internet. Therefore, it might be possible that add-on hosting repositories can be compromised, leading to distribution of malicious add-ons. The add-ons community takes add-on security seriously, particularly when it comes to distribution channels.

 

Q. Does this mean future add-ons from Joseph will not support old Windows releases?

Yes. While the policy takes full effect in January 2023, you can assume that new add-ons I (Joseph Lee) may publish in 2022 will require Windows 10 Version 21H1 or later.

 

Q. Do you have plans to release updates for unmaintained add-ons prior to the policy taking effect in January 2023?

For Enhanced Touch Gestures, Event Tracker, GoldWave, Resource Monitor, Sound Splitter, and StationPlaylist, I have no plans to release updates in 2022; rather, releasing updates is close to impossible as these add-ons no longer support old Windows releases at the source code level.

 

Q. Wait, the just announced policy sounds similar to the feature update support policy for Windows App Essentials add-on.

In some ways, yes. The difference is that Windows App Essentials support Windows 10 and later whereas other add-ons support old Windows releases such as Windows 7.

 

Q. Why January 2023?

This is when support for Windows 7 and 8.1 will end for most users (extended security updates for Windows 7, extended support for Windows 8.1; Windows 8 is end of life as of January 2016).

 

Q. Does this policy apply to Windows Server releases?

Yes. While some Windows 10 releases have a server counterpart, they (2016, 2019, 2022) are still supported by Microsoft.

 

Q. What if I’m using Windows 10 Enterprise long-term servicing branch/channel (LTSB/LTSC) releases?

Since this edition is meant for mission-critical devices, I and my add-ons do not support this scenario. Windows App Essentials add-on itself does not support this configuration either.

 

The key takeaway is this: if you can, please upgrade to supported Windows releases as soon as possible. Feel free to contact me if you have additional questions or comments.

Cheers,

Joseph


Re: TesseractOCR add-on

mk360
 

Hi,

The change To Tesseract 5.1 32 b implies that it will work in 32 bits systems?

Regards,

mk.

El 27/06/2022 a las 16:04, Rui Fontes escribió:
Hello!


The new version already have it!

https://github.com/ruifontes/tesseractOCR/releases/download/2022.06.27/tesseractOCR-2022.06.27.nvda-addon

Changes:

- Updated Tesseract from version 5.0 Alpha (64-bit) to 5.1 (32-bit);
- Added several more recognition languages;
- Introduced the option to select a second language to be used in OCR of documents with multiple languages and a button to forget it;
- Introduced a new document type, "With auto-orientation", that allows the OCR engine to rotate the image as necessary;
- Introduced beeps to signal the add-on is working;
- Corrected code to avoid the non population of the download languages combobox;
- Corrected a problem with controlTypes roles preventing compatibility with NVDA 2020.4;
- Added russian translation.

Best regards,

Rui Fontes
NVDA portuguese team



Às 14:11 de 01/06/2022, Kakarla Nageswaraiah escreveu:
Hello,
I didn't find Telugu language.
Will they add in future?
Thanks and regards.


On 6/1/22, Ravindran V.S. <ravivssl@...> wrote:
Hi Rui,
I have tried this add-on and still could not succeed with the OCR with it.
If this list permits, here, if not would like to have a chat off line about
the usage of this OCR Add-on please.
Let me know your convenience.
Thanks,
Ravi. ..

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Pranav Lal
Sent: Tuesday, May 31, 2022 10:22 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] TesseractOCR add-on

Hi Rui,

I hear you and thanks for the comparison.

Pranav
















Re: TesseractOCR add-on

Rui Fontes
 

Hello!


The new version already have it!

https://github.com/ruifontes/tesseractOCR/releases/download/2022.06.27/tesseractOCR-2022.06.27.nvda-addon

Changes:

- Updated Tesseract from version 5.0 Alpha (64-bit) to 5.1 (32-bit);
- Added several more recognition languages;
- Introduced the option to select a second language to be used in OCR of documents with multiple languages and a button to forget it;
- Introduced a new document type, "With auto-orientation", that allows the OCR engine to rotate the image as necessary;
- Introduced beeps to signal the add-on is working;
- Corrected code to avoid the non population of the download languages combobox;
- Corrected a problem with controlTypes roles preventing compatibility with NVDA 2020.4;
- Added russian translation.

Best regards,

Rui Fontes
NVDA portuguese team



Às 14:11 de 01/06/2022, Kakarla Nageswaraiah escreveu:

Hello,
I didn't find Telugu language.
Will they add in future?
Thanks and regards.


On 6/1/22, Ravindran V.S. <ravivssl@...> wrote:
Hi Rui,
I have tried this add-on and still could not succeed with the OCR with it.
If this list permits, here, if not would like to have a chat off line about
the usage of this OCR Add-on please.
Let me know your convenience.
Thanks,
Ravi. ..

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Pranav Lal
Sent: Tuesday, May 31, 2022 10:22 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] TesseractOCR add-on

Hi Rui,

I hear you and thanks for the comparison.

Pranav














Re: NVDA Malfunctions In Read-Only Text Boxes In Google Chrome When In Focus Mode

 

The issue opened by Mr. Robinette was closed with this note, "This seems like intended behaviour for Chromium. Consider opening an issue against Chromium."

That's the long and the short of it.  Any screen reader can only work with what is exposed to it to work with.  This specific situation appears to stem from what Chromium-based browsers allow the screen reader access to.

It does make me wonder, though, why NVAccess would not actually follow-up with opening such an issue.  I know from my years "in the coding biz" that issues opened by entities tend to get a lot more, and more immediate, attention than those opened by end users.  A pecking order exists.
--

Brian - Windows 10, 64-Bit, Version 21H2, Build 19044  

The real art of conversation is not only to say the right thing in the right place but to leave unsaid the wrong thing at the tempting moment.

        ~ Dorothy Nevill


Re: sluggishness.

Sarah k Alawami
 

1. what version of nvda. Latest doesn't help.
2. what version of windows. You didn't say
3. what are your computer's specks? You didn't say
4. what steps did you take to troubleshoot? You didn't say.

We need to know all of this before we answer questions, this way we can
eliminate stuff, or you can.


----
I hereby vow to follow the admins creed. Work smarter not harder. If I can
get the user to do what they need to do themselves, then I have done my job.

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Faithville via
groups.io
Sent: Monday, June 27, 2022 6:48 AM
To: nvda@nvda.groups.io
Subject: [nvda] sluggishness.

I have been noticing that nvda, the latest version is very sluggish, on my
computer, has anyone noticed this and what can be done to fix this?


Re: NVDA Malfunctions In Read-Only Text Boxes In Google Chrome When In Focus Mode

Brian's Mail list account
 

This sounds like what occurs in thenavigation modes in nvda, but at a more keyboard intensive level. This might mean an add on might be able to get a short cut to do such a thing.
Brian

--
bglists@...
Sent via blueyonder.(Virgin media)
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.

----- Original Message -----
From: "Steve Nutt" <steve@...>
To: <nvda@nvda.groups.io>
Sent: Sunday, June 26, 2022 6:23 PM
Subject: Re: [nvda] NVDA Malfunctions In Read-Only Text Boxes In Google Chrome When In Focus Mode


Hello Jean,



JAWS behaves differently in that regard. It will let you move to a read only edit box by pressing E then enter to enter focus mode. You can then use cursor keys to read the read only edit box, you can even perform a control A and Control C, and it will copy only the contents of the read only edit box.



I think NVDA should allow this.



All the best


Steve



From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gene
Sent: 28 May 2022 15:41
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA Malfunctions In Read-Only Text Boxes In Google Chrome When In Focus Mode



I'm not sure what you are working with. It appears to be some sort of source code. When I go to the page, I hear something like welcome to and then the name of an editor.

However, it appears to me that NVDA is working as expected. A read only edit field is read only, you can't write in it. Focus mode doesn't let you move in a web page unless you are in a field that allows movement, such as an edit field that allows you to write when in focus mode. When in structures like combo boxes, you can move as well or in a list of radio buttons. But the structure on the actual web page must allow you to move and I would think that by definition, a read only edit field wouldn't. There is no cursor provided in the underlying page for a read only field, I would think.

Gene

On 5/28/2022 9:27 AM, Luke Robinett wrote:

Hi Gene. If you check out the issue page I linked to, I provide steps for how to reproduce the issue. Let me know if that works for you. Thanks!





On May 27, 2022, at 5:01 PM, Gene <mailto:gsasner@...> <gsasner@...> wrote:

 Can you provide a link to a page with a read only edit field? I don't recall sites that have them. I probably just read the content and don't pay attention much if the field says read only. I would ordinarily read text where I am not writing in browse mode.

I just tried the Google search field and I had no problem but that isn't a read only edit field.

Gene

On 5/27/2022 6:44 PM, Luke Robinett wrote:

In Google Chrome running on Windows 10 Home Edition, NVDA only announces the first character of whatever text is present when in focus mode and using the arrow keys to navigate by character inside read-only text boxes. For example, if the text box contains the word “Hello,” pressing the left or right arrow keys just results in NVDA saying “H.”



Similar behavior occurs in Microsoft Edge except NVDA says the word “blank” instead of the first character in the text box. This suggests it may be a broader issue with Chromium browsers. In Firefox, NVDA functions normally in read-only text boxes.



I’ve also opened a GitHub ticket for this issue which can be found here:

https://github.com/nvaccess/nvda/issues/13745



I searched existing closed and open issues prior to opening a new one and didn’t find a previous report of this issue. Please refer to my bug report for more details and background.



Thanks,

Luke


Re: sluggishness.

Gene
 

Have you compared performance with the last version or a previous version?  You can run it as a portable version.  there are all sorts of things that may cause sluggishness and we don't know if this is an NVDA problem. 

Is the computer sluggish with Narrator?  Sometimes, something happens by coincidence and has nothing to do what what may seem to be the problem.  For example, you may install or upgrade NVDA and then find the computer is sluggish.  This needs to be checked in ways  I've suggested earlier, comparing performance with Narrator and/or with an earlier version of NVDA.

Gene

On 6/27/2022 8:47 AM, Faithville via groups.io wrote:

I have been noticing that nvda, the latest version is very sluggish, on my computer, has anyone noticed this and what can be done to fix this?







Re: sluggishness.

 

The first things you need to try are The Most Basic Troubleshooting Steps for Suspected NVDA Issues
--

Brian - Windows 10, 64-Bit, Version 21H2, Build 19044  

The real art of conversation is not only to say the right thing in the right place but to leave unsaid the wrong thing at the tempting moment.

        ~ Dorothy Nevill


sluggishness.

Faithville
 

I have been noticing that nvda, the latest version is very sluggish, on my computer, has anyone noticed this and what can be done to fix this?


Re: Skipping the advertisements in web browsers.

 

How funny.
Something we all should've pounced on the moment anti-ad extensions/Brave became available.
This whole "skipping ads" thing is Definitely Not an NVDA issue.
This is browser and html/script code needing to be marked up correctly to even allow you to skip the ad in the first place.
I feel a Mt. Vesuvius on this issue, lol...

Jason Bratcher


Re: Skipping the advertisements in web browsers.

Gene
 

On thinking about this further and looking at two pages, very brief forms that you use to log in to a site may have a log in button instead of a submit button.  I think the button on such very short forms usually says login.  Searching for log may work if submit doesn't work and you may see that on some kinds of pages, searching for log may be more likely to get you to the button. 

But my question still remains.  Why do you come across forms enough that this is an issue?  If you skip the navigation links at the tops of pages and move by heading or use skip blocks of links, you shouldn't run across such forms regularly. 

There are times  when you will want to look at navigation links, but on familiar pages, this is often not necessary.

Gene

On 6/26/2022 10:36 AM, Gene wrote:

If so, when you are at a form, searching for the word submit should place you on it and thus at the end of the form.  Screen-reader search on web sites is one of the most valuable and underused screen-reader features.

Gene

On 6/26/2022 10:22 AM, Jason Bratcher wrote:
And some forms don't have a physical Submit button coded in html on the page.
Just the word "Submit" that's marked up to be clickable.
I've seen that on countless forms.
Bad practice in my book.

Jason Bratcher








4301 - 4320 of 101097