Date   

Re: tracking down NVDA triggers

tim
 

I have to go with John on this one.
If you have any third party virus or malware hunters. Then you can have screen notifications pop up and go . With those any screen reader acts the same way.
So I would look for notifications and maintenance software that came with the laptop. All have some type for updating drivers.

On Oct 1, 2019, at 1:33 PM, Joseph Lee <joseph.lee22590@...> wrote:

Hi,
I’m thinking not – as in debugging steps didn’t take place from what I can tell.
To Giles, can you try running NVDA in debug mode, and as soon as you hear NVDA repeat an info you don’t want to hear, send a log (press NVDA+F1 to open the log and copoy and paste everything as an email) to me and Quentin so we can diagnose what’s up? I’m requesting logs in private because it may contain sensitive information. Be sure to CC info@... with the precise description of the problem when sending the log to us.
Cheers,
Joseph
 
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Brian Vogel
Sent: Tuesday, October 1, 2019 10:29 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] tracking down NVDA triggers
 
On Tue, Oct 1, 2019 at 01:23 PM, Joseph Lee wrote:
Only after trying to figure out what’s up with NVDA should we look into SFC.
Joseph, given what was offered in the original message, I am willing to presume that NVDA debugging, including a possible uninstall/reinstall, has already taken place.  Perhaps it hasn't, but then I'd hope that might be tried as a step.

I stand by my advice, which does not include doing a completely clean reinstall unless all other methods fail.  Doing an SFC and DISM as "good housekeeping" hurts absolutely nothing, and can also serve as a diagnostic step.

There are multiple ways to come at any problem, and I am not about to allow my advice to be grossly mischaracterized.   It's a fairly simple matter to do some significant "Windows 10 Health Checks" to see if something could be wrong.  It has been my experience that when uncharacteristic behaviors such as those described are occurring it's generally not the application program that's at fault.
 
-- 
Brian - Windows 10 Pro, 64-Bit, Version 1903, Build 18362  
The color of truth is grey.
           ~ André Gide

 

 



Re: Announcement: changes coming to NVDA 2019.3 compatibility announcements page based on latest community feedback

Afik Souffir <afik.souffir@...>
 

hello Joseph and all!
Joseph, thank you for this info.


-------------------------------------------

cordialement,
Afik Souffir
Israel


2019-10-01 21:05 UTC+03:00, Joseph Lee <joseph.lee22590@gmail.com>:

Hi NVDA users,



As you may know, there exists a website on community add-ons page that
lists
add-ons considered compatible with upcoming NVDA 2019.3/Python 3:

https://addons.nvda-project.org/addons/nvdapy3.en.html



Over the last few days, NVDA developers and add-on authors had a discussion
regarding what is considered "compatible". Currently, add-ons with source
code compatibility are considered compatible with NVDA 2019.3/Python 3, and
some authors expressed concerns about compatibility range statements
provided by add-ons via their manifests. Specifically, while some add-ons
were source code compatible, they haven't been updated in a long time and
thus do not either come with compatibility statements or assume old NVDA
releases. The overall conclusion from our discussion is that, while source
code compatibility is a good indicator, this information isn't friendly to
users, and users would look at compatibility range specified by add-ons as
an indicator of whether add-ons are compatible with future NVDA releases.



Based on this, the following change will be made to the above website:



Any add-on that is deemed source code compatible yet do not show manifest
updates will be marked as "incompatible" for purposes of record keeping. In
other words, although an add-on may pass checks based on source code, if it
cannot be installed on latest NVDA stable releases (or for that matter, if
it fails to install on NVDA 2019.3 in any form) due to outdated
compatibility range statements in the manifest, it will be marked as
"incompatible". Exceptions include add-ons marked as "planned" or "work in
progress" - authors are planning to get add-ons ready for NVDA 2019.3 or
work is under way to support NVDA 2019.3 technologies, respectively.



This change will take effect on October 2, 2019. As a result, the following
will happen (some will have to wait for a while to be implemented):



1. The community will be asked to contact authors of add-ons that are
failing compatibility check (source code is ready but cannot be installed
on
NVDA 2019.3). I advise waiting until 2019.3 beta 1 comes out before
initiating this.
2. In the future, when add-ons are going through review process for
registration on community add-ons website, manifest information
(specifically, compatibility statements) will be checked. Details will be
announced when it is time to implement this change (hopefully before end of
this year).
3. For every add-on listed on community add-ons website, compatibility
range statement will be encouraged. This will become mandatory after
details
of compatibility check review (see above) is finalized, hopefully by
January
1, 2020.



Thank you.

Cheers,

Joseph





Re: So what will happen to my favorite add-ons in the future: September 2019 update

kelby carlson
 

Will the Eloquence synthesizer ad-ons be compatible with NVDA 2019.3?

On 9/18/19, Joseph Lee <joseph.lee22590@gmail.com> wrote:
Hi NVDA users,



At least I'm back in action (slightly reduced workload, but working on NVDA
coding here and there) and some news to share with you regarding what will
happen to your favorite add-ons in the future.



First, a bit of a background for people who don't know what I'm talking
about:



This past summer (winter for some), I and other NVDA developers worked on
preparing NVDA for the future. Specifically, with the impending end of life
of Python 2 (the original language NVDA is coded in), the developers felt
it
is time to shift gears and move onto a more modern way of providing equal
access to technology: Python 3. In addition to some exciting enhancements,
it brought many changes under the hood that will make NVDA a viable option
for all of you in the long term, including some performance enhancements,
smooth internationalization, and much more.



One of the questions we received in recent weeks has been about your
favorite add-ons and the upcoming NVDA 2019.3, the first version to be
powered by Python 3. Although there were initial bumps, I'm delighted to
announce that majority of add-ons that you know and love will work with
NVDA
2019.3. Take a look at the following items:



* 63 percent of add-ons hosted on community add-ons website
(addons.nvda-project.org) are compatible with NVDA 2019.3.
* Several authors have indicated plans to introduce Python 3 support
to their add-ons soon, and others are working hard on porting their add-ons
to make them future-proof.
* Notable add-on developers, including makers of Vocalizer series and
DictationBridge, have committed to releasing Python 3 compatible versions
of
their add-ons in the future. In case of Vocalizer series, an alpha version
of old Vocalizer Direct (2.x) is being tested, and a public beta of Python
3
compatible DictationBridge is scheduled to be released shortly after NVDA
2019.3 beta 1 is released.



The add-ons community expects more add-ons to join the ranks of
future-proof
add-ons as NVDA 2019.3 release approaches. Until then.

Cheers,

Joseph




--
Kelby Carlson


Virtual Viewer

kelby carlson
 

Is there anything like the virtual viewer in JAWS that NVDA has? It
would be amazing to be able to easily bring up a list of footnotes in
Word.

--
Kelby Carlson


Announcement: changes coming to NVDA 2019.3 compatibility announcements page based on latest community feedback

 

Hi NVDA users,

 

As you may know, there exists a website on community add-ons page that lists add-ons considered compatible with upcoming NVDA 2019.3/Python 3:

https://addons.nvda-project.org/addons/nvdapy3.en.html

 

Over the last few days, NVDA developers and add-on authors had a discussion regarding what is considered “compatible”. Currently, add-ons with source code compatibility are considered compatible with NVDA 2019.3/Python 3, and some authors expressed concerns about compatibility range statements provided by add-ons via their manifests. Specifically, while some add-ons were source code compatible, they haven’t been updated in a long time and thus do not either come with compatibility statements or assume old NVDA releases. The overall conclusion from our discussion is that, while source code compatibility is a good indicator, this information isn’t friendly to users, and users would look at compatibility range specified by add-ons as an indicator of whether add-ons are compatible with future NVDA releases.

 

Based on this, the following change will be made to the above website:

 

Any add-on that is deemed source code compatible yet do not show manifest updates will be marked as “incompatible” for purposes of record keeping. In other words, although an add-on may pass checks based on source code, if it cannot be installed on latest NVDA stable releases (or for that matter, if it fails to install on NVDA 2019.3 in any form) due to outdated compatibility range statements in the manifest, it will be marked as “incompatible”. Exceptions include add-ons marked as “planned” or “work in progress” – authors are planning to get add-ons ready for NVDA 2019.3 or work is under way to support NVDA 2019.3 technologies, respectively.

 

This change will take effect on October 2, 2019. As a result, the following will happen (some will have to wait for a while to be implemented):

 

  1. The community will be asked to contact authors of add-ons that are failing compatibility check (source code is ready but cannot be installed on NVDA 2019.3). I advise waiting until 2019.3 beta 1 comes out before initiating this.
  2. In the future, when add-ons are going through review process for registration on community add-ons website, manifest information (specifically, compatibility statements) will be checked. Details will be announced when it is time to implement this change (hopefully before end of this year).
  3. For every add-on listed on community add-ons website, compatibility range statement will be encouraged. This will become mandatory after details of compatibility check review (see above) is finalized, hopefully by January 1, 2020.

 

Thank you.

Cheers,

Joseph


Re: Zoom with nvda

Samuel Villa <Saleena81@...>
 

Hey.

This may be off topic, but on the Freedom Scientific YouTube channel, there is an instructional video on how to use Zoom with JAWS.

Let me know if this was helpful.


Re: tracking down NVDA triggers

 

Hi,

I’m thinking not – as in debugging steps didn’t take place from what I can tell.

To Giles, can you try running NVDA in debug mode, and as soon as you hear NVDA repeat an info you don’t want to hear, send a log (press NVDA+F1 to open the log and copoy and paste everything as an email) to me and Quentin so we can diagnose what’s up? I’m requesting logs in private because it may contain sensitive information. Be sure to CC info@... with the precise description of the problem when sending the log to us.

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Brian Vogel
Sent: Tuesday, October 1, 2019 10:29 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] tracking down NVDA triggers

 

On Tue, Oct 1, 2019 at 01:23 PM, Joseph Lee wrote:

Only after trying to figure out what’s up with NVDA should we look into SFC.

Joseph, given what was offered in the original message, I am willing to presume that NVDA debugging, including a possible uninstall/reinstall, has already taken place.  Perhaps it hasn't, but then I'd hope that might be tried as a step.

I stand by my advice, which does not include doing a completely clean reinstall unless all other methods fail.  Doing an SFC and DISM as "good housekeeping" hurts absolutely nothing, and can also serve as a diagnostic step.

There are multiple ways to come at any problem, and I am not about to allow my advice to be grossly mischaracterized.   It's a fairly simple matter to do some significant "Windows 10 Health Checks" to see if something could be wrong.  It has been my experience that when uncharacteristic behaviors such as those described are occurring it's generally not the application program that's at fault.
 
--

Brian - Windows 10 Pro, 64-Bit, Version 1903, Build 18362  

The color of truth is grey.

           ~ André Gide

 

 


Re: tracking down NVDA triggers

 

On Tue, Oct 1, 2019 at 01:23 PM, Joseph Lee wrote:
Only after trying to figure out what’s up with NVDA should we look into SFC.
Joseph, given what was offered in the original message, I am willing to presume that NVDA debugging, including a possible uninstall/reinstall, has already taken place.  Perhaps it hasn't, but then I'd hope that might be tried as a step.

I stand by my advice, which does not include doing a completely clean reinstall unless all other methods fail.  Doing an SFC and DISM as "good housekeeping" hurts absolutely nothing, and can also serve as a diagnostic step.

There are multiple ways to come at any problem, and I am not about to allow my advice to be grossly mischaracterized.   It's a fairly simple matter to do some significant "Windows 10 Health Checks" to see if something could be wrong.  It has been my experience that when uncharacteristic behaviors such as those described are occurring it's generally not the application program that's at fault.
 
--

Brian - Windows 10 Pro, 64-Bit, Version 1903, Build 18362  

The color of truth is grey.

           ~ André Gide

 

 


Re: tracking down NVDA triggers

 

Hi Brian,

Actually, for this one, I think John’s advice is a bit better – I myself have experienced it on my ThinkPad, and it appears to be an event-related problem. To truly find out what’s up, you need to run NVDA in debug mode (restart NVDA with debug logging enabled) and capture the log output (it’ll print all sorts of things). Only after trying to figure out what’s up with NVDA should we look into SFC.

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Brian Vogel
Sent: Tuesday, October 1, 2019 10:16 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] tracking down NVDA triggers

 

On Tue, Oct 1, 2019 at 12:33 PM, John Isige wrote:

I'm sorry, but WTF? Some dude's getting a program's title read to him
periodically, and the conclusion is, yeah dude you might want to more or
less reinstall Windows.

No, it isn't.   I cannot help if you cannot be bothered to read, and comprehend, the advice given.  You might want to think about that before spouting off garbage like this again.
 
--

Brian - Windows 10 Pro, 64-Bit, Version 1903, Build 18362  

The color of truth is grey.

           ~ André Gide

 

 


Re: tracking down NVDA triggers

 

On Tue, Oct 1, 2019 at 12:33 PM, John Isige wrote:
I'm sorry, but WTF? Some dude's getting a program's title read to him
periodically, and the conclusion is, yeah dude you might want to more or
less reinstall Windows.
No, it isn't.   I cannot help if you cannot be bothered to read, and comprehend, the advice given.  You might want to think about that before spouting off garbage like this again.
 
--

Brian - Windows 10 Pro, 64-Bit, Version 1903, Build 18362  

The color of truth is grey.

           ~ André Gide

 

 


Add-on Updater 19.10.1 and Windows 10 App Essentials 19.10, an important notice on Version 1809 support from WinTenApps #addonrelease

 

Hi all,

 

Add-on Updater 19.10.1 and Windows 10 App Essentials 19.10 are now available. Add-on Updater can now check for updated versions of Beep Keyboard and Synth Ring Settings Selector from David CM (newly declared stable), and Windows 10 App Essentials adds support for various 20H1 features, most notably the new Cortana user interface and modern Chinese, Japanese, and Korean IME.

 

IMPORTANT: if you are using Windows 10 App Essentials on Windows 10 October 2018 Update (Version 1809), please keep the following in mind:

 

Support for Version 1809 from Windows 10 App Essentials is coming to a close soon. The sunset date is set for January 2020. People using development releases will see this come sooner – as soon as NVDA 2019.3 stable version is released, development channel will drop support for Version 1809. Don’t worry, it won’t affect stable channel users for a while longer.

 

Cheers,

Joseph


Re: In-Process 1st October

molly the blind tech lover
 

Hi.

This is a wonderful in process

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Quentin Christensen
Sent: Tuesday, October 1, 2019 1:20 AM
To: nvda@nvda.groups.io
Subject: [nvda] In-Process 1st October

 

Hi everyone,

This week in In-process, a great milestone for NVDA, a new beta, a shout-out to our friends at Intopia and heaps more!

https://www.nvaccess.org/post/in-process-1st-october/

 

--

Quentin Christensen
Training and Support Manager

 


Re: tracking down NVDA triggers

John Isige
 

I'm sorry, but WTF? Some dude's getting a program's title read to him
periodically, and the conclusion is, yeah dude you might want to more or
less reinstall Windows. That's like, option number one? I also notice
there's no explanation whatsoever as to how we're supposedly concluding
this is a Windows issue worthy of some sort of reinstallation. I'm
sorry, this just seems irresponsible, even with things like the Windows
10 reset where you can reinstall but preserve files and data.


I don't know the answer, about how to chase it down from the logs, but
it seems to me a much more readily apparent answer is that another
program is running in the background and stealing focus, or making NVDA
think focus has changed. I don't see how it automatically means that
Windows itself has been corrupted in any way whatsoever.


Suppose for instance, there's a download manager running in the
background, and it flashes its window or such to get your attention. It
seems entirely possible to me that such a benign event could be
temporarily stealing NVDA's focus. I've had this occur before, often it
will repeatedly read the first item on the desktop, both with NVDA and
under NVDA remote. So far as I know, both of my machines are good in
terms of Windows, I'm not noticing any other issues whatsoever. It
happens so infrequently that I've never worried about it.

On 10/1/2019 9:17, Brian Vogel wrote:
Giles,

            There is likely some corruption in your Windows 10
installation itself that needs to be remedied.  The probability of
this being an NVDA-based issue is very small indeed, particularly if
you've already tried uninstalling NVDA and reinstalling it.


My standard advice, in virtually all cases, (and presuming any
potential infection has already been addressed, first) is trying the
following, in the order specified.  If the issue is fixed by option
one then there's no need to go further.  Stop whenever your issue is
fixed:

1. */Using SFC (System File Checker) and DISM (Deployment Imaging
Servicing and Management) to Repair Windows 8 & 10/*
<https://drive.google.com/uc?export=download&id=0B98uELZbPFnOc2l4M0Y1V3pkcGM>


2. */Doing a Windows 10 Repair Install or Feature Update Using the
Windows 10 ISO file/*
<https://drive.google.com/uc?export=download&id=1RZiHlLVtXewYBgoSvJNm9_08hj1tALPK>


3. Doing a completely clean reinstall (options *a* & *b* are
downloadable PDF files):

           a) */Completely Clean Win10 (Re)install Using MCT to
Download Win10 ISO File/*
<https://drive.google.com/uc?export=download&id=1hHoEnSz2YWHyztOO3ZjXtV2y4gQASoMR>

           b) */Completely Clean Win10 (Re)install Using MCT to Create
a Bootable USB Drive/*
<https://drive.google.com/uc?export=download&id=1cvsT64KAwz5ZJmiPfBQlUDBOoskb9dDO>

           c) */How to do a CLEAN Installation of Windows 10/*
<https://forums.tomshardware.com/faq/how-to-do-a-clean-installation-of-windows-10.3170366/>(/Tom’s
Hardware Forums/, with screen shots)

I */_never_/* choose the “/thermonuclear option/,” the completely
clean reinstall, until it's clear that this is the only viable option.
I hate having to go through all the work of reconfiguring a machine
from scratch if that can reasonably and safely be avoided.

__


--

Brian *-*Windows 10 Pro, 64-Bit, Version 1903, Build 18362

*The color of truth is grey.*

           ~ André Gide


Re: Zoom with nvda

Sarah k Alawami
 

I also use it for my youtube streams as well. It's just better than team talk. Both have their place, but zoom is just easy peezy to set up.

Sarah Alawami, owner of TFFP. . For more info go to our website. This is also our libsyn page as well.
For stuff we sell, mac training materials and  tutorials go here.
and for hosting options go here
to subscribe to the feed click here

Our telegram channel is also a good place for an announce only in regard to podcasts, contests, etc.

Our discord is where you will know when we go live on youtube, twitch and mixer. Thanks Restream staff.

Finally, to become a patron and help support the podcast go here

On 1 Oct 2019, at 6:05, Ralf Kefferpuetz wrote:

Hello,

I fully agree, Zoom is very accessible. I use it in my company daily many times since it  replaced webEx and Skype for Business for our conference calls. Even the presentation pane can be focussed easily and the content of it can be read with NVDAs OCR (NVDA-r).

 

Cheers,

  Ralf

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of George Kerscher
Sent: Dienstag, 1. Oktober 2019 13:35
To: nvda@nvda.groups.io
Subject: Re: [nvda] Zoom with nvda

 

Hi,

 

I read their training materials and it worked well for me. Also, their tech support is excellent, and they have been trained about screen readers. I am not saying that they know keystrokes and all that, but they do have a clue about screen readers. Try their training materials first. Oh, and I love Zoom.

 

Best

George

 

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Governor staten
Sent: Monday, September 30, 2019 8:44 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Zoom with nvda

 

About the time limit thing, you read correctly. Alt+a mutes and unnmutes audio, alt+v turns on and off your video. NVDA WILL READ ALERTS TO YOU. Alerts are when you turn on/off video, audio, or when someone joins the meeting.

 

If you are in the home tab, you will see a search field. Tab past that, and you will see a drop down button. When you down-arrow, you will eventually get to settings. Most everything explains itself as far as settings go. There is a tab under settings that gives you all keyboard shortcuts you could ever want. You can change them if you wish to. I hope this helps you a bit.

 

 

 


 

On 9/30/2019 6:18 PM, hurrikennyandopo ... wrote:

Hi guys

 

Does any one know of a tutorial for us to learn how to use this program?

There seems to be videos aimed more at the sighted.

 

I was browsing there website at https://zoom.us

It looks as though you can do one on one for free but if in a group only up to 40 minutes for free if I read it right.

 

Has any one used it or have notes on it to use it.

 

I have been asked to use it they sent me a link and it is all setup to go into a room etc and had a look around the app I think you would call it.

 

But I was also looking at it from the other side you setting up a room or inviting some one into the room etc if you get what I mean but not going into all the other features it has.

 

 

Any help would be great I guess also down the track to try it out from the other side the basic's of using it with some one.

 

 

Gene nz

 

--

Check out my website for NVDA tutorials and other blindness related materials at http://www.accessibilitycentral.net

To find out which library networks in New Zealand have a copy of the NVDA screen reader on them and there library locations please go to http://www.accessibilitycentral.net/nz%20libraries%20with%20nvda.html
To find a NVDA certified expert near you, please visit the following link https://certification.nvaccess.org/. The certification page contains the official list of NVDA certified individuals from around the world, who have sat and successfully passed the NVDA expert exam.



Re: Jaws is now doing better with thunderbird than nvda

Sarah k Alawami
 

Be aware though when you do ths and you check the first box you might get stuck in that dialogue, at least I do so I have to navigate with back tab or shift tab as the ret of you call it. And then I can go through the dialogue in reverse. We'll see if what I did fixes the issues I'm having.

Sarah Alawami, owner of TFFP. . For more info go to our website. This is also our libsyn page as well.
For stuff we sell, mac training materials and  tutorials go here.
and for hosting options go here
to subscribe to the feed click here

Our telegram channel is also a good place for an announce only in regard to podcasts, contests, etc.

Our discord is where you will know when we go live on youtube, twitch and mixer. Thanks Restream staff.

Finally, to become a patron and help support the podcast go here

On 1 Oct 2019, at 0:24, mattias wrote:

press alt+t for tools

and press s for account settings

find your account and press right arrow

here you should find some categories

find something with synchronization

press tab

i dont remember what the checkbox are named

On 2019-09-30 11:15, zahra wrote:

thanks so much for your great guidance.
how can i access settings of my account?
i remember that i only entered my name and email address and selected
emap that thunderbird does not stores emails on my computer, but it
seems that i was not successful and i thought that its the faulte of
thunderbird that download emails and waistes my internet charge and
hard disk space without my permission or knowledge!

On 9/30/19, mattias mjonsson1986@... wrote:

think you have to do the setting when you setup the account

in account settings of the account

syncronization settings there is a checkbox

keep messages in all folders on this computer

On 2019-09-30 09:14, zahra wrote:

i did not recieve answer to my question.
how should i set thunderbird that never stores any emails to my computer?
and just works like web interface of my gmail?!

On 9/30/19, Kevin Cussick via Groups.Io
<the.big.white.shepherd@...> wrote:

I am not getting this but I don't doubt that it is happening for some,
anyway if jaws works for you but I can't see how it would be better.
but anyway if it works fare enough.

On 28/09/2019 23:34, Robert Kingett wrote:

I never understood why people are getting this lag? I don't get it. If
you delete your trash regularly, change the settings so that absolutely
nothing is saved on the machine, and delete emails rather than keeping
junk mail, there is no lag what so ever with NVDA. I don't get it, and
I
don't understand why so many are having this issue.


Re: tracking down NVDA triggers

 

Giles,

            There is likely some corruption in your Windows 10 installation itself that needs to be remedied.  The probability of this being an NVDA-based issue is very small indeed, particularly if you've already tried uninstalling NVDA and reinstalling it.


My standard advice, in virtually all cases, (and presuming any potential infection has already been addressed, first) is trying the following, in the order specified.  If the issue is fixed by option one then there's no need to go further.  Stop whenever your issue is fixed:


1. 
Using SFC (System File Checker) and DISM (Deployment Imaging Servicing and Management) to Repair Windows 8 & 10 


2. 
Doing a Windows 10 Repair Install or Feature Update Using the Windows 10 ISO file


3. Doing a completely clean reinstall (options a & b are downloadable PDF files):

           a) Completely Clean Win10 (Re)install Using MCT to Download Win10 ISO File

           b) Completely Clean Win10 (Re)install Using MCT to Create a Bootable USB Drive

           c) How to do a CLEAN Installation of Windows 10  (Tom’s Hardware Forums, with screen shots)

I never choose the “thermonuclear option,” the completely clean reinstall, until it's clear that this is the only viable option. I hate having to go through all the work of reconfiguring a machine from scratch if that can reasonably and safely be avoided.

 

 


--

Brian - Windows 10 Pro, 64-Bit, Version 1903, Build 18362  

The color of truth is grey.

           ~ André Gide

 

 


tracking down NVDA triggers

Giles Turnbull
 

Hi all,

It must be over a year ago that I mentioned that, on my Asus laptop, NVDA would consistently and apparently randomly, announce the current program's title bar. Replies came to the conclusion that something was triggering NVDA's focus to switch away and then back to what was the active window, causing NVDA to re-announce the window's titlebar.

I haven't been experienceing this for the last year because I got a new Dell laptop which doesn't suffer this effect. But, after the death of my Dell I'm back on the Asus and I'm puzzled what might be triggering this.

Is there any way through the debugging logs to figure out what is causing NVDA to do this?

On this laptop I'm using NVDA 2019.2 and Windows 10 Version 1903 (OS Build 18362.356)

Thanks for any thoughts ... I've not used NVDA with logging enabled before.

Giles


Re: In-Process 1st October

 

2 things. I still see the NVDA getting started audio from 2017 up in the store. Also, if we bought the first getting started audio how do we get the new, upgraded, version?


Re: Zoom with nvda

Ralf Kefferpuetz
 

Hello,

I fully agree, Zoom is very accessible. I use it in my company daily many times since it  replaced webEx and Skype for Business for our conference calls. Even the presentation pane can be focussed easily and the content of it can be read with NVDAs OCR (NVDA-r).

 

Cheers,

  Ralf

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of George Kerscher
Sent: Dienstag, 1. Oktober 2019 13:35
To: nvda@nvda.groups.io
Subject: Re: [nvda] Zoom with nvda

 

Hi,

 

I read their training materials and it worked well for me. Also, their tech support is excellent, and they have been trained about screen readers. I am not saying that they know keystrokes and all that, but they do have a clue about screen readers. Try their training materials first. Oh, and I love Zoom.

 

Best

George

 

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Governor staten
Sent: Monday, September 30, 2019 8:44 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Zoom with nvda

 

About the time limit thing, you read correctly. Alt+a mutes and unnmutes audio, alt+v turns on and off your video. NVDA WILL READ ALERTS TO YOU. Alerts are when you turn on/off video, audio, or when someone joins the meeting.

 

If you are in the home tab, you will see a search field. Tab past that, and you will see a drop down button. When you down-arrow, you will eventually get to settings. Most everything explains itself as far as settings go. There is a tab under settings that gives you all keyboard shortcuts you could ever want. You can change them if you wish to. I hope this helps you a bit.

 

 

 


 

On 9/30/2019 6:18 PM, hurrikennyandopo ... wrote:

Hi guys

 

Does any one know of a tutorial for us to learn how to use this program?

There seems to be videos aimed more at the sighted.

 

I was browsing there website at https://zoom.us

It looks as though you can do one on one for free but if in a group only up to 40 minutes for free if I read it right.

 

Has any one used it or have notes on it to use it.

 

I have been asked to use it they sent me a link and it is all setup to go into a room etc and had a look around the app I think you would call it.

 

But I was also looking at it from the other side you setting up a room or inviting some one into the room etc if you get what I mean but not going into all the other features it has.

 

 

Any help would be great I guess also down the track to try it out from the other side the basic's of using it with some one.

 

 

Gene nz

 

--

Check out my website for NVDA tutorials and other blindness related materials at http://www.accessibilitycentral.net

To find out which library networks in New Zealand have a copy of the NVDA screen reader on them and there library locations please go to http://www.accessibilitycentral.net/nz%20libraries%20with%20nvda.html
To find a NVDA certified expert near you, please visit the following link https://certification.nvaccess.org/. The certification page contains the official list of NVDA certified individuals from around the world, who have sat and successfully passed the NVDA expert exam.



Monthly Group Rules Reminder for the NVDA Group (nvda@nvda.groups.io)

nvda@nvda.groups.io Group Moderators <nvda@...>
 

This is the NVDA Group Monthly Reminder Notice, which is meant to re-emphasize the NVDA Group Rules.

The central purpose of the NVDA Group is discussing how to use NVDA, either configuring NVDA's settings or familiarizing oneself with its modes and commands.  Discussions about which programs are accessible using NVDA, NVDA add-ons, NVDA tutorials and documentation, and configuring synthesizers or Braille displays for use with NVDA are also permitted.  Like all screen readers, it is a tool for accessing something else, and really serves no other purpose.  Its function as an accessibility tool is, of course, its reason for being.

It is presumed that the majority of members will be using NVDA, and possibly other screen readers, as part of their daily routine.  This being the case, before you post a message you have to consider whether the question you are about to ask is actually about NVDA itself, or about the program you’re using it to access.  Questions of the form, How do I use . . . with NVDA?, are very seldom about NVDA, but are almost always about the program being accessed with NVDA.

The NVDA Group has a Chat Subgroup (see: https://nvda.groups.io/g/chat, Group Email Addresses section) that has as its purpose the asking of virtually any “off-topic” question about anything you can think of, including just socializing.  It should be used for exactly that purpose. The Chat Subgroup has generally had technically focused topics related to using features of the programs that one is using NVDA to access or about other programs that have proven helpful.  Only those who are already members of the NVDA Group can subscribe to the Chat Subgroup.  

Before choosing where to post, please ask yourself the question, “Is what I’m about to ask or offer directly related to controlling or using NVDA, or whether a specific program is accessible with NVDA?”  If that can be answered, “Yes,” then post to the NVDA Group, and if the answer is, “No,” then the topic belongs in the NVDA Chat Subgroup.

In order to make your experience, and those of all other members, as pleasant as they can be, please follow these practices:

1.  Use threaded or conversation view in your e-mail client program or webmail and reading through the entirety of a topic before replying.  It gets you completely up to speed and avoids a lot of repetition.  If you choose not to use threaded/conversation view, please take the time to read through all messages from the group that are in your inbox prior to adding any reply to the group.  It’s the only way you can be sure you’re up to speed on any topic when not using threaded/conversation view.

2.  Reading through all new topics before replying, as topics have a tendency to get split upon occasion and often an answer ends up being in a separate topic.

3. If you have reason to believe your question has likely been asked and answered in the past please search the Group Archive first before asking it again.  Step-by-Step instructions for searching the group archive using the Groups.io search or a web search engine of your choosing: Searching_the_NVDA_Group_Archive.docx.  Please consider using a web search first for questions that have almost certainly been asked frequently and for which myriad answers, often in the form of tutorials, already exist.

4.  Think very carefully about the title you are going to give any topic you post.  The topic is the first (and, sometimes, only) thing a member sees and that may be how they decide if they’re going to look further.   Generic titles, such as “Help Me!,” are not helpful because they give no idea about what.  Compare that to something like, “NVDA not reading Excel cell contents,” or, “NVDA setting for pronouncing numbers,” where the exact issue where help is needed is front and center.   Even something like, “Need help with the following . . .,” lets the reader know that you are going to present a list of issues.

5.  Please avoid, “What is the best . . .?,” topics, because what qualifies as “best” is entirely subjective.   Topics of this sort are also always chat topics.  If you know you have specific needs then asking, “What {insert program type here} has the following features . . .,” is much more descriptive.   If you want to know what programs people like for a specific task, asking, “What’s your favorite . . . and why?,” is far more likely to get you the details you want to have.  Notice that none of the above questions ask about whether a program is accessible with NVDA.  If you’re asking something like, “Which {insert program class here} is accessible with NVDA?,” then it’s a main group topic.

6.  Any topic that is not about using NVDA to accomplish a task, or how to control NVDA, belongs in the chat subgroup, not the main group.  All questions about how to use the specific features of a program that you’re using NVDA to access, but not about NVDA itself, belong in the chat subgroup.

 

Respectful, even if slightly heated, disagreements will occur occasionally and will be tolerated provided what is described next does not occur.  Flaming, name calling, instigating arguments for their own sake that do nothing to advance anyone’s knowledge, pointed rudeness, and similar boorish behavior will not be tolerated.  If at any point one of you happens upon a message anywhere in the NVDA Group sphere, main or chat, that fits the preceding description then please report it to the group owner either via e-mail at, nvda+owner@nvda.groups.io, or, if you read via the web interface at https://nvda.groups.io/g/nvda/topics, then use the Report this message option that’s a part of the More button at the end of each message.  Please don’t add a protest message the topic.  If we receive a report and agree with it, the issue will be taken care of promptly.

 

If you find the amount of traffic from this Group, or any Groups.io group, overwhelming, then please download and read:

Controlling the Messages You Receive via E-Mail from Groups.io (docx)

Controlling the Messages You Receive via E-Mail from Groups.io (PDF)

Each of you has the ability to mute topics that don’t interest you, get digests instead of individual messages, or to set up topic preview for yourself via the Following Only and First Messages Also features used in conjunction with each other.  It is up to you to use those to manage your e-mail as you see fit.  It’s almost certain that there will be plenty of topics on the chat subgroup that will not be of the least interest to you as an individual. Setting up topic preview lets you pick and choose what you want to continue to see, and this function can be used on any Groups.io group.

 

Sincerely,

Nimer Jaber                                     Brian Vogel

 

NVDA Group Owner                      NVDA Group Moderator

 

To learn more about the NVDA Group, please visit https://nvda.groups.io/g/nvda

To start sending messages to members of this group, send email to nvda@nvda.groups.io 

If you do not wish to belong to the NVDA Group, you may unsubscribe by sending an email to nvda+unsubscribe@nvda.groups.io 

To see and modify all of your groups, go to https://groups.io