Date   
Re: NVDA and web buttons

Hettie
 

Thanks for the information. Will try that in future when I'm stuck.


Hettie

On 2020/08/01 8:44 pm, Jackie wrote:
Just press NVDA spacebar again, Hettie. A lower beep tone is what you
want to hear.

So I suspect I'm gonna get in trouble for saying this, but I'm just
sharing my experience. Sometimes, it appears like NVDA has trouble
activating some web elements, & I often have to use a variety of
techniques if enter or spacebar doesn't work, including the NVDA f7
key, using object navigation, NVDA backspace/shift backspace to ensure
the element is in focus & then enter/spacebar/click, etc. I think some
of it just has to do w/the element not actually being in focus,
although NVDA indicates that it is.

On 8/1/20, Hettie <woehler.hettie@...> wrote:
Hi all

I used the NVDA key + spacebar to activate an unsubscribe button on my
AVG account web page. I was able to tab to the wanted button but unable
to activate it. After this it was also not possible to read the screen
with the arrow keys. When my son came to assist me he saw that there was
a message on the screen asking whether I really want to unsubscribe.
That message wasn't read to me and as I douldn't navigate the screen I
didn't knew that I was supposed to react on a yes/no question.

How do I return to the normal screen after pressing the NVDA key +
spacebar?


Thanks for any help.


Hettie



--
This email has been checked for viruses by AVG.
https://www.avg.com




--
This email has been checked for viruses by AVG.
https://www.avg.com

Re: NVDA contribution guide (users edition): so you want to write and submit pull requests for NVDA...

Sean
 

Joseph, this is a great mail or article :) . I read it with all my attention. Thank you so much.

Here writes a lot of thought about NVDA’s code database.
I’m just curious about one thing:
NVDA’s code database is big.
I’m looking for a document describing NVDA’s folder layout.

  • For example, which module of NVDA is processing notifications to Action Center?

I’m very new to NVDA. I have been using it for years and now I want to support coding.
Do you know any documents or methods on this subject?
How should we consider the NVDA’s folder hierarchy?

On 02/08/2020 05:42, Joseph Lee wrote:

Hi NVDA users,

The below post was sent to NVDA developers (including code contributors outside of NV Access) and add-on authors, but figured it would be a good idea to let you (users) see what it takes to propose, develop, and submit changes to NVDA through code. Before we get into that, a few things to note:

  • Some of the things I wrote are rough at times (my apologies for these).
  • The biggest takeaway is that coding is not for everyone.
  • Although I produced various NVDA tutorials (including tutorials on add-on development), I do not work for NV Access nor my views represent that of the organization.

 

With that out of the way:

 

Hi all,

 

While editing the latest edition of NVDA Add-on Dev Guide and in the midst of planning a pull request strategy, I thought about something that was nagging at the back of my mind and I’m sure many are wondering about: submitting pull requests. This stems from a discussion on NVDA add-ons list several weeks ago regarding add-on development strategies such as code layout and such. I hope the following serves as sort of a rough map as to how to navigate the complex landscape of pull requests for any project, specifically for NVDA.

 

One of the reasons why NVDA is popular is because people can suggest and submit changes publicly. Sometimes this is needed to keep up with technology and accessibility standards. Sometimes a braille display manufacturer would like to see drivers for their products integrated into NVDA. Sometimes people submit spelling and grammar fixes for documentation. Whatever the suggestion might be, they go through a review process – the moment a pull request is submitted, it goes through several checks, culminating in improving your work based on feedback from stable version users (I’ll talk about this phrasing later, as that is going to be important).

 

Some of you might be wondering what a pull request is. A pull request is the act of submitting changes you made to a piece of software for inclusion in the original product. It starts with you thinking about an idea, a change, or a bug, then you go through researching, coding, and testing your idea, and if you believe your idea is ready for the world, publish a pull request. The maintainer of the product you are sending a pull request for would review your idea, suggest improvements if any, and if things are looking fine, integrate it into the original product.

 

No, forget the above definition. In truth, a pull request is a collection of your thought process, research and coding skills, test cases, real-world (and sometimes hypothetical) justifications, user impact, empathy and communication, refinements, feedback, and life-long learning. A successful pull request contains ALL of these. For example, a pull request is not complete without impactful justifications, code without tests will come back to haunt you years later, and your brilliant fix becomes meaningless when you don’t show empathy and effective communication skills.

 

So I guess some of you might insist on writing pull requests. There is one more thing that makes or breaks a pull request: do you understand the project itself? I don’t want you to think that code is everything – beginning computer science and software engineering students may think that coding is all there is to it. A project, as a complete system, contains not only code, but personnel, history, culture, assumptions, norms, expectations, and impact. This is more so for a specialized project such as NVDA: screen reader users have different expectations about what it means to use computers and using software. For instance, one of the cultural artifacts of NVDA is keyboard accessibility, which is different than say, a touch-based user interface. After these warnings, if you are not willing to or not comfortable with learning to appreciate screen reading, cultural assumptions about disability, and accessibility norms, then I’m afraid that writing pull requests for NVDA might not be a good idea for you at this time.

 

I’m saying all these (in a long way) to give you this solemn warning: without understanding the context in which NVDA operates (computer accessibility and usability for people with disabilities), writing effective NVDA pull requests is impossible. Sure, we (NVDA developers and code contributors) look for coding style, test cases, and good justifications when reviewing pull requests. But what we are after is your willingness to understand the culture in which NVDA is used. Do not give us a brilliant algorithm that can solve hundreds of different IAccessible2 issues at once. Rather, let us know that you are learning the NVDA source code and culture.

 

So how do you write an effective NVDA pull request? Well, the second step is thinking carefully (the first step was the above warning). After being part of NVDA community and culture for a while (obviously you need to be familiar with bits of NVDA source code and coding style), you may come across an interesting idea, a user suggestion or two, or perhaps you found an ancient bug. Do not be tempted to start coding right away – sit down, get a drink (not alcohol please), and think about what you just heard or discovered (the latter in case you found a bug). Depending on what’s bothering you, you can think about the following:

 

  • Someone suggested something. How can I better understand what this person is talking about? If you want, start talking to the person who suggested such and such change.
  • I discovered a bug. Do I understand what this bug might be (or what the bug is), or is this something wrong with my NVDA settings? If it is truly an ancient bug, how can I reproduce it, and are there potential causes, impact, and solutions?
  • I have this brilliant idea I want to test. Can I articulate it to NVDA beginners? How can I test this idea? What will its impact be for users? What potential issues can it cause?

 

But don’t just think aloud to yourself: talk to someone. The best way to do so is searching GitHub, and if you know the idea you have (or a bug you found) wasn’t found, file a new issue. Chances are that someone will talk to you through various means (including commenting on the issue you filed); after all, humans are social beings.

 

So you talked to someone, and either you know you’re going to work on this idea or may get help from someone (or perhaps artificial intelligence might come to the rescue). If you are comfortable (and confident) enough to work on researching, coding, testing, explaining, and justifying your idea, go ahead with research, coding, and testing. Do not spend all night coding (trust me, I and many others have gone through countless all-night hackathons and regretted afterwards).

 

When you research, code, and test your idea (which may or may not become your dream pull request), keep the following in mind:

 

  • You need to read a lot. You need to prepare your mind so that when it comes time to code and test, you will know what you are up to.
  • You are writing an essay. After all, coding is responding to an essay prompt (or two).
  • You are teaching a machine to think differently. You are a movie director, an architect, a tutor, a politician (maybe that’s going too far), or any job that requires you to teach someone (or something) new skills.
  • Don’t forget to “taste your wine”. An effective software is not complete without extensive tests. And no, just compiling and running your changes does not constitute a complete test – you MUST try your best to comply with pull request expectations (including, yes, linting BEFORE you commit).
  • You are a user, after all. In other words, perform tests as though you are the person who suggested the idea you are “talking” about in your code.

 

After you think, research, code, and test your idea (or a pull request), and verifying that it is ready to be sent to NV Access for review (via GitHub), prepare to explain and justify your changes. An effective pull request is more subjective than objective. That is, how you explain and justify your changes will have great impact on acceptance of your pull request. For example, if you just tell NVDA Developers that you fixed an ancient bug without specifying what it is or how you did it, reviewers might say, “hmmm, tell us more.” Or you come up with a brilliant algorithm for fixing hundreds of IAccessible2 issues at once but do not justify the impact of your algorithm on users. The overwhelming response will be, “how will your idea affect users as they use NVDA in hundreds of different scenarios?” Or in some cases, you submit a pull request based on a user’s suggestion, thinking that it is in scope for screen reading. How reviewers react to that pull request will depend on how effective your justifications are going to be (after all, persuasion matters).

 

At some point, reviewers will review your work and either approve your idea, suggest changes, or direct you elsewhere. Do not worry if reviewers tell you that your idea does not fit NVDA and its culture; think of that decision as a way for you to reflect on your thought process. If reviewers suggest changes, think about what these are and respond accordingly (perhaps make suggested changes, discuss changes, or something else).

 

Now your pull request has been approved and integrated into NVDA. This is not the time to pop open that champagne bottle you kept for this purpose. Rather, prepare to receive feedback from users, even when your idea makes it to the next public release of NVDA. This is so that you can learn and refine your work. Also, if you are willing, take some time to help others with their pull requests (reviewing, suggesting things, researching on behalf of others if asked, or drop some occasional joke or two (joking)).

 

I did briefly mention humor as an interesting way to help others. I included it to highlight the serious and rigorous nature of writing and submitting NVDA pull requests. NVDA development through pull requests is a serious and rigorous process, as a small change you make will be used in many scenarios by thousands of users around the world. More importantly, as a seasoned code contributor (I joined NVDA community in 2012), the most important thing you should learn is understanding the culture (disability culture) in which NVDA operates – I want you to become advocates, not just programmers.

 

Before I forget: some of you might be wondering about NVDA add-on development. Although not as rigorous as NVDA itself, you should take that process seriously, as your add-on(s) will be used by many people.

 

For me, among recent pull requests I wrote, the one I’m proud of is introducing foundations to support UIA notification event. It took me days to understand the scope of the problem and work on a stable solution. The pull request that brought you UIA notification event support was merged in 2018, and we have seen refinements since.

 

Perhaps the most intriguing pull request I submitted was ability to enable and disable individual add-ons. I spent days trying to understand the internal logic required to support this scenario. I received feedback from many people on this regard, including from several core NVDA developers. Ever since this pull request was merged in 2016, many improvements were made, some of which I provided feedback on.

 

I’m sure many of you would like to contribute to NVDA for months and years to come (including for the eventual new developer hired by NV Access). But remember my warning above: coding, specifically writing and submitting pull requests is not for everyone. Writing and submitting pull requests is a serious and rigorous task, and if you are not willing to learn the culture surrounding NVDA, your pull requests will not be effective. I and other developers can teach you the inner workings of NVDA for weeks to months (or years), but it is up to potential pull request writers themselves to show willingness to make an impactful difference for a community who must now rely on the double-edged sword that is technological progress, especially given the era we live in.

 

To those writing pull requests, good luck. To those contributing in other ways, keep up the good work. Please stay safe and healthy.

Cheers,

Joseph

--

Sean

👨‍🦯 I’m programmer. I coding often Python, sometimes Go and rarely C++.

NVDA contribution guide (users edition): so you want to write and submit pull requests for NVDA...

 

Hi NVDA users,

The below post was sent to NVDA developers (including code contributors outside of NV Access) and add-on authors, but figured it would be a good idea to let you (users) see what it takes to propose, develop, and submit changes to NVDA through code. Before we get into that, a few things to note:

  • Some of the things I wrote are rough at times (my apologies for these).
  • The biggest takeaway is that coding is not for everyone.
  • Although I produced various NVDA tutorials (including tutorials on add-on development), I do not work for NV Access nor my views represent that of the organization.

 

With that out of the way:

 

Hi all,

 

While editing the latest edition of NVDA Add-on Dev Guide and in the midst of planning a pull request strategy, I thought about something that was nagging at the back of my mind and I’m sure many are wondering about: submitting pull requests. This stems from a discussion on NVDA add-ons list several weeks ago regarding add-on development strategies such as code layout and such. I hope the following serves as sort of a rough map as to how to navigate the complex landscape of pull requests for any project, specifically for NVDA.

 

One of the reasons why NVDA is popular is because people can suggest and submit changes publicly. Sometimes this is needed to keep up with technology and accessibility standards. Sometimes a braille display manufacturer would like to see drivers for their products integrated into NVDA. Sometimes people submit spelling and grammar fixes for documentation. Whatever the suggestion might be, they go through a review process – the moment a pull request is submitted, it goes through several checks, culminating in improving your work based on feedback from stable version users (I’ll talk about this phrasing later, as that is going to be important).

 

Some of you might be wondering what a pull request is. A pull request is the act of submitting changes you made to a piece of software for inclusion in the original product. It starts with you thinking about an idea, a change, or a bug, then you go through researching, coding, and testing your idea, and if you believe your idea is ready for the world, publish a pull request. The maintainer of the product you are sending a pull request for would review your idea, suggest improvements if any, and if things are looking fine, integrate it into the original product.

 

No, forget the above definition. In truth, a pull request is a collection of your thought process, research and coding skills, test cases, real-world (and sometimes hypothetical) justifications, user impact, empathy and communication, refinements, feedback, and life-long learning. A successful pull request contains ALL of these. For example, a pull request is not complete without impactful justifications, code without tests will come back to haunt you years later, and your brilliant fix becomes meaningless when you don’t show empathy and effective communication skills.

 

So I guess some of you might insist on writing pull requests. There is one more thing that makes or breaks a pull request: do you understand the project itself? I don’t want you to think that code is everything – beginning computer science and software engineering students may think that coding is all there is to it. A project, as a complete system, contains not only code, but personnel, history, culture, assumptions, norms, expectations, and impact. This is more so for a specialized project such as NVDA: screen reader users have different expectations about what it means to use computers and using software. For instance, one of the cultural artifacts of NVDA is keyboard accessibility, which is different than say, a touch-based user interface. After these warnings, if you are not willing to or not comfortable with learning to appreciate screen reading, cultural assumptions about disability, and accessibility norms, then I’m afraid that writing pull requests for NVDA might not be a good idea for you at this time.

 

I’m saying all these (in a long way) to give you this solemn warning: without understanding the context in which NVDA operates (computer accessibility and usability for people with disabilities), writing effective NVDA pull requests is impossible. Sure, we (NVDA developers and code contributors) look for coding style, test cases, and good justifications when reviewing pull requests. But what we are after is your willingness to understand the culture in which NVDA is used. Do not give us a brilliant algorithm that can solve hundreds of different IAccessible2 issues at once. Rather, let us know that you are learning the NVDA source code and culture.

 

So how do you write an effective NVDA pull request? Well, the second step is thinking carefully (the first step was the above warning). After being part of NVDA community and culture for a while (obviously you need to be familiar with bits of NVDA source code and coding style), you may come across an interesting idea, a user suggestion or two, or perhaps you found an ancient bug. Do not be tempted to start coding right away – sit down, get a drink (not alcohol please), and think about what you just heard or discovered (the latter in case you found a bug). Depending on what’s bothering you, you can think about the following:

 

  • Someone suggested something. How can I better understand what this person is talking about? If you want, start talking to the person who suggested such and such change.
  • I discovered a bug. Do I understand what this bug might be (or what the bug is), or is this something wrong with my NVDA settings? If it is truly an ancient bug, how can I reproduce it, and are there potential causes, impact, and solutions?
  • I have this brilliant idea I want to test. Can I articulate it to NVDA beginners? How can I test this idea? What will its impact be for users? What potential issues can it cause?

 

But don’t just think aloud to yourself: talk to someone. The best way to do so is searching GitHub, and if you know the idea you have (or a bug you found) wasn’t found, file a new issue. Chances are that someone will talk to you through various means (including commenting on the issue you filed); after all, humans are social beings.

 

So you talked to someone, and either you know you’re going to work on this idea or may get help from someone (or perhaps artificial intelligence might come to the rescue). If you are comfortable (and confident) enough to work on researching, coding, testing, explaining, and justifying your idea, go ahead with research, coding, and testing. Do not spend all night coding (trust me, I and many others have gone through countless all-night hackathons and regretted afterwards).

 

When you research, code, and test your idea (which may or may not become your dream pull request), keep the following in mind:

 

  • You need to read a lot. You need to prepare your mind so that when it comes time to code and test, you will know what you are up to.
  • You are writing an essay. After all, coding is responding to an essay prompt (or two).
  • You are teaching a machine to think differently. You are a movie director, an architect, a tutor, a politician (maybe that’s going too far), or any job that requires you to teach someone (or something) new skills.
  • Don’t forget to “taste your wine”. An effective software is not complete without extensive tests. And no, just compiling and running your changes does not constitute a complete test – you MUST try your best to comply with pull request expectations (including, yes, linting BEFORE you commit).
  • You are a user, after all. In other words, perform tests as though you are the person who suggested the idea you are “talking” about in your code.

 

After you think, research, code, and test your idea (or a pull request), and verifying that it is ready to be sent to NV Access for review (via GitHub), prepare to explain and justify your changes. An effective pull request is more subjective than objective. That is, how you explain and justify your changes will have great impact on acceptance of your pull request. For example, if you just tell NVDA Developers that you fixed an ancient bug without specifying what it is or how you did it, reviewers might say, “hmmm, tell us more.” Or you come up with a brilliant algorithm for fixing hundreds of IAccessible2 issues at once but do not justify the impact of your algorithm on users. The overwhelming response will be, “how will your idea affect users as they use NVDA in hundreds of different scenarios?” Or in some cases, you submit a pull request based on a user’s suggestion, thinking that it is in scope for screen reading. How reviewers react to that pull request will depend on how effective your justifications are going to be (after all, persuasion matters).

 

At some point, reviewers will review your work and either approve your idea, suggest changes, or direct you elsewhere. Do not worry if reviewers tell you that your idea does not fit NVDA and its culture; think of that decision as a way for you to reflect on your thought process. If reviewers suggest changes, think about what these are and respond accordingly (perhaps make suggested changes, discuss changes, or something else).

 

Now your pull request has been approved and integrated into NVDA. This is not the time to pop open that champagne bottle you kept for this purpose. Rather, prepare to receive feedback from users, even when your idea makes it to the next public release of NVDA. This is so that you can learn and refine your work. Also, if you are willing, take some time to help others with their pull requests (reviewing, suggesting things, researching on behalf of others if asked, or drop some occasional joke or two (joking)).

 

I did briefly mention humor as an interesting way to help others. I included it to highlight the serious and rigorous nature of writing and submitting NVDA pull requests. NVDA development through pull requests is a serious and rigorous process, as a small change you make will be used in many scenarios by thousands of users around the world. More importantly, as a seasoned code contributor (I joined NVDA community in 2012), the most important thing you should learn is understanding the culture (disability culture) in which NVDA operates – I want you to become advocates, not just programmers.

 

Before I forget: some of you might be wondering about NVDA add-on development. Although not as rigorous as NVDA itself, you should take that process seriously, as your add-on(s) will be used by many people.

 

For me, among recent pull requests I wrote, the one I’m proud of is introducing foundations to support UIA notification event. It took me days to understand the scope of the problem and work on a stable solution. The pull request that brought you UIA notification event support was merged in 2018, and we have seen refinements since.

 

Perhaps the most intriguing pull request I submitted was ability to enable and disable individual add-ons. I spent days trying to understand the internal logic required to support this scenario. I received feedback from many people on this regard, including from several core NVDA developers. Ever since this pull request was merged in 2016, many improvements were made, some of which I provided feedback on.

 

I’m sure many of you would like to contribute to NVDA for months and years to come (including for the eventual new developer hired by NV Access). But remember my warning above: coding, specifically writing and submitting pull requests is not for everyone. Writing and submitting pull requests is a serious and rigorous task, and if you are not willing to learn the culture surrounding NVDA, your pull requests will not be effective. I and other developers can teach you the inner workings of NVDA for weeks to months (or years), but it is up to potential pull request writers themselves to show willingness to make an impactful difference for a community who must now rely on the double-edged sword that is technological progress, especially given the era we live in.

 

To those writing pull requests, good luck. To those contributing in other ways, keep up the good work. Please stay safe and healthy.

Cheers,

Joseph

Re: NVDA and web buttons

Jackie
 

Just press NVDA spacebar again, Hettie. A lower beep tone is what you
want to hear.

So I suspect I'm gonna get in trouble for saying this, but I'm just
sharing my experience. Sometimes, it appears like NVDA has trouble
activating some web elements, & I often have to use a variety of
techniques if enter or spacebar doesn't work, including the NVDA f7
key, using object navigation, NVDA backspace/shift backspace to ensure
the element is in focus & then enter/spacebar/click, etc. I think some
of it just has to do w/the element not actually being in focus,
although NVDA indicates that it is.

On 8/1/20, Hettie <woehler.hettie@...> wrote:
Hi all

I used the NVDA key + spacebar to activate an unsubscribe button on my
AVG account web page. I was able to tab to the wanted button but unable
to activate it. After this it was also not possible to read the screen
with the arrow keys. When my son came to assist me he saw that there was
a message on the screen asking whether I really want to unsubscribe.
That message wasn't read to me and as I douldn't navigate the screen I
didn't knew that I was supposed to react on a yes/no question.

How do I return to the normal screen after pressing the NVDA key +
spacebar?


Thanks for any help.


Hettie



--
This email has been checked for viruses by AVG.
https://www.avg.com




--
Subscribe to a WordPress for Newbies Mailing List by sending a message to:
wp4newbs-request@... with 'subscribe' in the Subject field OR by
visiting the list page at http://www.freelists.org/list/wp4newbs
& check out my sites at www.brightstarsweb.com & www.mysitesbeenhacked.com

NVDA and web buttons

Hettie
 

Hi all

I used the NVDA key + spacebar to activate an unsubscribe button on my AVG account web page. I was able to tab to the wanted button but unable to activate it. After this it was also not possible to read the screen with the arrow keys. When my son came to assist me he saw that there was a message on the screen asking whether I really want to unsubscribe. That message wasn't read to me and as I douldn't navigate the screen I didn't knew that I was supposed to react on a yes/no question.

How do I return to the normal screen after pressing the NVDA key + spacebar?


Thanks for any help.


Hettie



--
This email has been checked for viruses by AVG.
https://www.avg.com

Re: Outlook 2016 - Cannot Open Certain Messages When NVDA is Active

Christo Vorster
 

Hi Quentin

 

It seems as if there was some kind of problem with the mail I receveid. After I installed NVDA 2020.2 and deleted the email, then requesting a re-send of the message, everything worked well.

 

Thank you, if I experience something similar, I’ll be in touch again.

 

Regards

 

Christo Vorster (Worcester, South Africa)

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Quentin Christensen
Sent: Friday, 31 July 2020 06:07
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA PROBLEM

 

Hi Christo,

 

Could you get me a copy of your NVDA log to have a look at please, ideally at debug level?
Please send it attached to an email to info@....  Include a description of what you have done and what isn't working as it should (so I know what it's about in case I don't get to investigate today).

First of all, your NVDA key is either INSERT or CAPS LOCK, depending on how you have NVDA setup.  So, to set your log level:
1) Press NVDA+control+g to open the general settings
2) Press TAB until the focus is on 'Log level'
3) Press DOWN ARROW to get to 'Debug'
4) Press ENTER to close settings
5) Press NVDA+control+c to save settings.

To restart NVDA with add-ons disabled:
1) Press NVDA+Q
2) Down arrow to 'Restart with add-ons disabled'
3) Press ENTER

Next, recreate the issue - do whatever causes problems.

To get NVDA's log after that, there are several ways:

If NVDA is still running and usable:
1) Press NVDA+F1 to open the log viewer
2) Press CONTROL+A to select all.
3) Press CONTROL+C to copy.
4) Open your email and start a message to info@..., type a little about what you have done and what has happened in the body of the message, then leave a space and:
5) Press CONTROL+V to paste the copied log.

Instead of using the log viewer, or if NVDA has stopped and you needed to restart it or the computer:
1) Press WINDOWS+R to open Windows' Run dialog
2) Type %temp% and press ENTER (that's the percent sign, the letter t e m p and another percent sign).  Windows Explorer should open to the temporary folder.
3) Press TAB to move to the file list
4) Press N and move down to find up to three files:  nvda.log (the log file for the current or most recent NVDA session), nvda-old.og (the log from the previous session) and nvda-crash.dmp (a crash dump with more information created if NVDA itself crashes).
5) Depending on what email program you use, the steps will be different, but attach as many of those three files to an email to info@... as will be useful, and again in the body of the message describe a bit about what has happened.

 

If possible, could you please also forward a message which causes problems to me so that I can endeavour to replicate myself?  Ideally, instead of forwarding as you normally would, could you please forward as attachment?  In Outlook you can move to the message in the list, then press ALT+H, 0, 0, then F.

 

Sometimes when forwarding a message normally, the email client can alter the structure enough so that even though it looks the same, it might not cause exactly the same effects, (such as crashing NVDA).

 

Kind regards

 

Quentin.

 

On Wed, Jul 29, 2020 at 7:21 PM Christo Vorster <christo.vorster.klavierstem@...> wrote:

GAood Morning list

Please help!!

Regards

 

Christo Vorster (Worcester, south Africa)

 

This is the copy of the log:

 

INFO - __main__ (10:54:35.500) - MainThread (9268):

Starting NVDA version 2020.1

INFO - core.main (10:54:36.897) - MainThread (9268):

Config dir: C:\Users\Christo Vorster\AppData\Roaming\nvda

INFO - config.ConfigManager._loadConfig (10:54:36.897) - MainThread (9268):

Loading config: C:\Users\Christo Vorster\AppData\Roaming\nvda\nvda.ini

INFO - core.main (10:54:40.442) - MainThread (9268):

Using Windows version 10.0.19041 workstation

INFO - core.main (10:54:40.442) - MainThread (9268):

Using Python version 3.7.7 (tags/v3.7.7:d7c567b08f, Mar 10 2020, 09:44:33) [MSC v.1900 32 bit (Intel)]

INFO - core.main (10:54:40.442) - MainThread (9268):

Using comtypes version 1.1.7

INFO - core.main (10:54:40.442) - MainThread (9268):

Using configobj version 5.1.0 with validate version 1.0.1

INFO - synthDriverHandler.setSynth (10:54:48.280) - MainThread (9268):

Loaded synthDriver ibmeci

INFO - core.main (10:54:49.218) - MainThread (9268):

Using wx version 4.0.3 msw (phoenix) wxWidgets 3.0.5 with six version 1.12.0

INFO - brailleInput.initialize (10:54:49.220) - MainThread (9268):

Braille input initialized

INFO - braille.initialize (10:54:49.228) - MainThread (9268):

Using liblouis version 3.12.0

INFO - braille.initialize (10:54:49.241) - MainThread (9268):

Using pySerial version 3.4

INFO - braille.BrailleHandler.setDisplayByName (10:54:51.145) - MainThread (9268):

Loaded braille display driver noBraille, current display has 0 cells.

INFO - core.main (10:54:53.007) - MainThread (9268):

Java Access Bridge support initialized

INFO - _UIAHandler.UIAHandler.MTAThreadFunc (10:54:53.272) - _UIAHandler.UIAHandler.MTAThread (7440):

UIAutomation: IUIAutomation6

INFO - core.main (10:55:00.063) - MainThread (9268):

NVDA initialized

ERROR - eventHandler.executeEvent (11:07:11.977) - MainThread (9268):

error executing event: gainFocus on <appModules.outlook.UIAGridRow object at 0x079A43B0> with extra args of {}

Traceback (most recent call last):

  File "eventHandler.pyc", line 155, in executeEvent

  File "eventHandler.pyc", line 92, in __init__

  File "eventHandler.pyc", line 100, in next

  File "NVDAObjects\__init__.pyc", line 1102, in event_gainFocus

  File "NVDAObjects\behaviors.pyc", line 611, in reportFocus

  File "NVDAObjects\__init__.pyc", line 988, in reportFocus

  File "speech\__init__.pyc", line 469, in speakObject

  File "speech\__init__.pyc", line 506, in getObjectSpeech

  File "speech\__init__.pyc", line 377, in getObjectPropertiesSpeech

  File "baseObject.pyc", line 42, in __get__

  File "baseObject.pyc", line 145, in _getPropertyViaCache

  File "appModules\outlook.pyc", line 445, in _get_name

  File "comtypesMonkeyPatches.pyc", line 26, in __call__

_ctypes.COMError: (-2146233083, None, (None, None, None, 0, None))

ERROR - eventHandler.executeEvent (11:07:46.564) - MainThread (9268):

error executing event: gainFocus on <appModules.outlook.OutlookWordDocument object at 0x0708E250> with extra args of {}

Traceback (most recent call last):

  File "speech\__init__.pyc", line 512, in getObjectSpeech

  File "documentBase.pyc", line 24, in makeTextInfo

  File "NVDAObjects\window\winword.pyc", line 673, in __init__

AttributeError: 'NoneType' object has no attribute 'range'

 

During handling of the above exception, another exception occurred:

 

Traceback (most recent call last):

  File "eventHandler.pyc", line 155, in executeEvent

  File "eventHandler.pyc", line 92, in __init__

  File "eventHandler.pyc", line 100, in next

  File "NVDAObjects\__init__.pyc", line 1102, in event_gainFocus

  File "NVDAObjects\__init__.pyc", line 988, in reportFocus

  File "speech\__init__.pyc", line 469, in speakObject

  File "speech\__init__.pyc", line 527, in getObjectSpeech

  File "documentBase.pyc", line 24, in makeTextInfo

  File "NVDAObjects\window\winword.pyc", line 678, in __init__

AttributeError: 'NoneType' object has no attribute 'range'

ERROR - eventHandler.executeEvent (11:07:46.574) - MainThread (9268):

error executing event: caret on <appModules.outlook.OutlookWordDocument object at 0x0708E250> with extra args of {}

Traceback (most recent call last):

  File "eventHandler.pyc", line 155, in executeEvent

  File "eventHandler.pyc", line 92, in __init__

  File "eventHandler.pyc", line 100, in next

  File "NVDAObjects\IAccessible\winword.pyc", line 47, in event_caret

  File "documentBase.pyc", line 24, in makeTextInfo

  File "NVDAObjects\window\winword.pyc", line 673, in __init__

AttributeError: 'NoneType' object has no attribute 'range'

ERROR - eventHandler.executeEvent (11:07:46.595) - MainThread (9268):

error executing event: caret on <appModules.outlook.OutlookWordDocument object at 0x0708E250> with extra args of {}

Traceback (most recent call last):

  File "eventHandler.pyc", line 155, in executeEvent

  File "eventHandler.pyc", line 92, in __init__

  File "eventHandler.pyc", line 100, in next

  File "NVDAObjects\IAccessible\winword.pyc", line 47, in event_caret

  File "documentBase.pyc", line 24, in makeTextInfo

  File "NVDAObjects\window\winword.pyc", line 673, in __init__

AttributeError: 'NoneType' object has no attribute 'range'

 

 

 

I have a problem opening certain emails in Outlook 2016.

 

If NVDA is turned off, the specific mails can be opened.

 

I copied the View Log after I experienced the problem.

 

Would it help if I uninstall, and then re-install NVDA?

 

 


 

--

Quentin Christensen
Training and Support Manager

 

Free Tutorials for using NVDA with MS Office Word, PowerPoint and Excel

soloman s
 

Hello all,

Could someone share tutorials for Word, Excel and PowerPoint using NVDA? It will be helpful if you could direct me to links/resources.
I am looking for free resources.

--
With warm regards
Solomon S
teachsolo@...

Re: I can't read table of content with nvda

Aschalew Byness
 

I am reading word document. nvda reads all but the table of content.
this happens when I read many word documents with table of contents

On 8/1/20, Daniel Damacena <@DanielDamacena> wrote:
Which software do you refer to?
If you're talking about adobe reader or adobe digital editions, yes, you
can read the toc.

Em sáb., 1 de ago. de 2020 às 04:59, Aschalew Byness <
gakidan.ashagre235@...> escreveu:

Hi you lovely guys
I couldn’t read table of contents with NVDA. Whenever I try to read
table of contents, nvda reads: out of link TOC \o "1-3" \h \z \u
link .
My sighted friends read the full content of the TOC. Nvda skips it
this way. ‘out of link TOC \o "1-3" \h \z \u link .

Solution?



--
Daniel Damacena



Monthly Group Rules Reminder for the NVDA Group (nvda@nvda.groups.io) #monthly-notice

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

 

NVDA Group Description:  NonVisual Desktop Access (NVDA) is screen reader software.  The central purpose of this 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.

What follows is the NVDA Group Monthly Reminder Notice, which is meant to reacquaint members with the NVDA Group Rules.

The following rule has never been applied, but is necessary for managing unforeseen circumstances.  The Group Owner and Moderators reserve the right to block, edit, or remove any message at any time at our sole discretion.  Any message that has content that violates the Groups.io Terms of Service is not permitted, is subject to immediate removal, and the member posting same to be placed on moderated status or banned, at the sole discretion of the Group Owner or Moderator. 

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.

The discussion of software on the NVDA Group is limited to software currently in support.  Depending on the type of software, specific version numbers will change with time.  Users are expected to know what remains in support and what has been dropped, and announcements will be made to this group when new software is released. It should be assumed that, when a new version of software is released, primary discussion will take place on that version, not versions of software which are years old. 

Unsupported versions of any software may only be discussed on the Chat Subgroup, not the main NVDA Group. 

Windows:  Only Windows 8.1 and currently supported versions of Windows 10.  Members should refer to the Windows Lifecycle Fact Sheet to determine which versions of Windows are currently supported.  Information about the dates on which specific versions of Windows 10 reached or will reach their end of service dates is listed there as well and will be updated as new versions are released. 

Note that it is acceptable to direct a user to the NVAccess or Microsoft sites where older versions can be downloaded, however, this is different than supporting a specific version of software or operating system.

NVDA:  NVDA has, at any given time, a single version under active support.  If a question arises about how to update to that version, and you’re on an earlier version, that will be permitted as transition problems can occasionally occur.

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, we ask members to 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)

Other specific e-mail addresses for the NVDA Group are:

To see and modify all of the groups you are subscribed to, go to https://groups.io 


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 

Re: I can't read table of content with nvda

Daniel Damacena
 

Which software do you refer to?
If you're talking about adobe reader or adobe digital editions, yes, you can read the toc.

Em sáb., 1 de ago. de 2020 às 04:59, Aschalew Byness <gakidan.ashagre235@...> escreveu:

Hi you lovely guys
I couldn’t read table of contents with NVDA. Whenever I try to read
table of contents, nvda reads: out of link  TOC \o "1-3" \h \z \u
link   .
My sighted friends read the full content of the TOC. Nvda skips it
this way. ‘out of link  TOC \o "1-3" \h \z \u   link   .

Solution?





--
Daniel Damacena

I can't read table of content with nvda

Aschalew Byness
 

Hi you lovely guys
I couldn’t read table of contents with NVDA. Whenever I try to read
table of contents, nvda reads: out of link TOC \o "1-3" \h \z \u
link .
My sighted friends read the full content of the TOC. Nvda skips it
this way. ‘out of link TOC \o "1-3" \h \z \u link .

Solution?

Re: I am needing assistance updating to the latest version of NVDA

Kevin Cussick
 

Hi, well done, I remember what was like when I got my first computer. so just shout out and we will help if we can.

On 31/07/2020 00:02, Betsy Grenevitch wrote:
Sorry to clutter the list but I wanted to thank David and Sarah for helping me so much. I did not have the website that sarah mentioned written down before and when I went in that way it worked. I have memory problems now and thus the reason my confidence level is even lower. Thank you both for helping me have the courage to try downloading it this way.
Thank you to those who designed the website that the link said exactly what told me that I was at the correct spot to download the latest update.
On 7/30/2020 3:59 PM, Sarah k Alawami wrote:

You will be fine. Go to nvda-project.org and use yoru screen reader's find function to find and navigate. You will be fine. You won't get hurt.

--

Sarah Alawami, owner of TFFP. . For more info go to our website. <http://www.tffppodcast.com>

Check out my adventures with a shadow machine. <http://tffppodcast.com/shadow>

to subscribe to the feed click here <http://feeds.feedburner.com/tffp> and you can also follow us on twitter <http://twitter.com/tffppodcast>

Our discord <http://discord.tffppodcast.com> is where you will know when we go live on twitch. <http://twitch.tv/ke7zum> Feel free to give the channel a follow and see what is up there.

For stream archives, products you can buy and more visit my main lbry page <http://lbry.tv/@ke7zum> and my tffp lbry page <http://lbry.tv/@tffppodcast> You will also be able to buy some of my products and eBooks there.

Finally, to become a patron and help support the podcast go here <Http://patreon.com/tffppodcast>

On 30 Jul 2020, at 12:25, Betsy Grenevitch wrote:

Thank you. I am waiting to hear back from David hopefully with a
link to the full install. As I have told you and now told him I do
not feel comfortable with websites where I have to download
something unless there is a direct link. I know it is a fear I
need to get over but I guess it is because of a lack of training
on computers.


On 7/30/2020 11:39 AM, Brian Vogel wrote:
And to add to Mr. Goldfield's advice, if you have an issue
running the full installer for NVDA 2020.2, then manually
uninstall whatever NVDA you currently have installed via Control
Panel, Programs and Features, then trying to install the latest
again.  But don't do that first, as an install-over install
generally works just fine.
--

Brian *-*Windows 10 Pro, 64-Bit, Version 1909, Build 18363

*/Science has become just another voice in the room; it has lost
its platform.  Now, you simply declare your own truth./*

~ Dr. Paul A. Offit, in /New York Times/ article, /How
Anti-Vaccine Sentiment Took Hold in the United States/
<https://www.nytimes.com/2019/09/23/health/anti-vaccination-movement-us.html>/,/September
23, 2019
--
Betsy Grenevitch
678-862-3876
--
Betsy Grenevitch
678-862-3876

Re: nvda addon list

 

Go to Groups.io, activate the "Find or Create a Group" control at the top, enter NVDA in the search box, activate search, and you'll get the list of the 29 NVDA related groups on Groups.io, this one and nvda-addons among them.

Every group's main page, is shown as a link, which is also a header, in the search results just like most web search engines.  You can use the H browsing shortcut to jump from group to group.  On the group page, if you activate the link, for any Groups.io group, will be a section entitled Group Email addresses under which all the addresses related to post, subscribe, unsubscribe and several other controls and contacts for the group will be listed.

--

Brian - Windows 10 Pro, 64-Bit, Version 1909, Build 18363  

Science has become just another voice in the room; it has lost its platform.  Now, you simply declare your own truth.

      ~ Dr. Paul A. Offit, in New York Times article, How Anti-Vaccine Sentiment Took Hold in the United States, September 23, 2019

 

 

nvda addon list

Aschalew Byness
 

I want to subscribe to nvda addon group list. I want also to subscribe
to other nvda related group list. help me please by sending their
subscription email address. thank you

Re: ALLOW APP THROUGH CONTROLLED FOLDER ACCESS DOESN'T READ

Quentin Christensen
 

Do you have any blocked apps?  I must admit I haven't really used this feature, but turning it on, it says most apps will be allowed by default, so maybe it is simply that there aren't any blocked apps?


On Wed, Jul 29, 2020 at 11:47 PM <heaven.lists92@...> wrote:

Dear List

 

My husband and I both have laptops with Windows 10 2004 and NVDA 2020-2.

 

Since we updated Windows, NVDA doesn't read the list of blocked apps in Controlled Folder Access.

 

Does anyone know what to do about this, please?

 

Kind regards

 

Heaven



--
Quentin Christensen
Training and Support Manager

Re: Possible nvda problems when the system and the nvda language is set to Greek

Luke Davis
 

On Fri, 31 Jul 2020, Nikos Demetriou via groups.io wrote:

People from Greece reported to me that after there is an update to nvda, the option to start nvda automatically with windows gets unchecked and they have to
go into general settings and enable it again.
I never had this issue so I assume that it has got something to do with the windows language or perhaps the nvda language.
All these people have got Greek selected for both windows and NVDA.
That happens to all kinds of people, with English or various other languages set. It happens to me about 25% of the time I upgrade, and it doesn't seem to happen consistently for the same version of NVDA across various systems.

For now it's just one of those little quirks of computer life. If NVDA is silent for a while after updating and doing the restart, this has probably happened. Press the shortcut to start it and if it starts, that's what occurred.

Luke

Re: Possible nvda problems when the system and the nvda language is set to Greek

 

Hi,

As for Windows 10 App Essentials problem, I do need a debug log from affected users (and I beg you from bottom of my heart, please don’t cross-post, especially by putting more than one list addresses in the CC field).

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Bobby Vinton
Sent: Thursday, July 30, 2020 11:46 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Possible nvda problems when the system and the nvda language is set to Greek

 

On 7/31/2020 2:38 AM, Nikos Demetriou via groups.io wrote:

Hi all.

I would like to report 2 issues some other users reported to me.

I cannot reproduce them for now because my windows language is set to English and the same applies for the nvda language.

 

I am sending this to both the nvda list and the nvda addons list because one issue is for nvda in general and the other issue is with an addon.

Both issues seem to affect windows 10 users only.

 

People from Greece reported to me that after there is an update to nvda, the option to start nvda automatically with windows gets unchecked and they have to go into general settings and enable it again.

I never had this issue so I assume that it has got something to do with the windows language or perhaps the nvda language.

All these people have got Greek selected for both windows and NVDA.

 

The second issue has got to do with the addon windows 10 app essentials.

 

The addon is refusing to install on some systems.

The message they receive says failed to install without any further explanations.

 

By changing the nvda language the problem is not fixed.

 

A user mannaged to install the addon at the end by changing the nvda language, uninstalling nvda and reinstalling it.

This user had windows 10 1909 at first, then she updated to 2004, but the addon was refusing to install.

 

If you need more information let me know.

If needed I will try to find some logs from some people.

Thanks

Nikos

I never had this issue eather.  That's very odd.

Re: Possible nvda problems when the system and the nvda language is set to Greek

Bobby Vinton
 

On 7/31/2020 2:38 AM, Nikos Demetriou via groups.io wrote:
Hi all.
I would like to report 2 issues some other users reported to me.
I cannot reproduce them for now because my windows language is set to English and the same applies for the nvda language.

I am sending this to both the nvda list and the nvda addons list because one issue is for nvda in general and the other issue is with an addon.
Both issues seem to affect windows 10 users only.

People from Greece reported to me that after there is an update to nvda, the option to start nvda automatically with windows gets unchecked and they have to go into general settings and enable it again.
I never had this issue so I assume that it has got something to do with the windows language or perhaps the nvda language.
All these people have got Greek selected for both windows and NVDA.

The second issue has got to do with the addon windows 10 app essentials.

The addon is refusing to install on some systems.
The message they receive says failed to install without any further explanations.

By changing the nvda language the problem is not fixed.

A user mannaged to install the addon at the end by changing the nvda language, uninstalling nvda and reinstalling it.
This user had windows 10 1909 at first, then she updated to 2004, but the addon was refusing to install.

If you need more information let me know.
If needed I will try to find some logs from some people.
Thanks
Nikos

I never had this issue eather.  That's very odd.

Possible nvda problems when the system and the nvda language is set to Greek

 

Hi all.
I would like to report 2 issues some other users reported to me.
I cannot reproduce them for now because my windows language is set to English and the same applies for the nvda language.

I am sending this to both the nvda list and the nvda addons list because one issue is for nvda in general and the other issue is with an addon.
Both issues seem to affect windows 10 users only.

People from Greece reported to me that after there is an update to nvda, the option to start nvda automatically with windows gets unchecked and they have to go into general settings and enable it again.
I never had this issue so I assume that it has got something to do with the windows language or perhaps the nvda language.
All these people have got Greek selected for both windows and NVDA.

The second issue has got to do with the addon windows 10 app essentials.

The addon is refusing to install on some systems.
The message they receive says failed to install without any further explanations.

By changing the nvda language the problem is not fixed.

A user mannaged to install the addon at the end by changing the nvda language, uninstalling nvda and reinstalling it.
This user had windows 10 1909 at first, then she updated to 2004, but the addon was refusing to install.

If you need more information let me know.
If needed I will try to find some logs from some people.
Thanks
Nikos

Re: Outlook 2016 - Cannot Open Certain Messages When NVDA is Active

Quentin Christensen
 

Hi Christo,

Could you get me a copy of your NVDA log to have a look at please, ideally at debug level?
Please send it attached to an email to info@....  Include a description of what you have done and what isn't working as it should (so I know what it's about in case I don't get to investigate today).

First of all, your NVDA key is either INSERT or CAPS LOCK, depending on how you have NVDA setup.  So, to set your log level:
1) Press NVDA+control+g to open the general settings
2) Press TAB until the focus is on 'Log level'
3) Press DOWN ARROW to get to 'Debug'
4) Press ENTER to close settings
5) Press NVDA+control+c to save settings.

To restart NVDA with add-ons disabled:
1) Press NVDA+Q
2) Down arrow to 'Restart with add-ons disabled'
3) Press ENTER

Next, recreate the issue - do whatever causes problems.

To get NVDA's log after that, there are several ways:

If NVDA is still running and usable:
1) Press NVDA+F1 to open the log viewer
2) Press CONTROL+A to select all.
3) Press CONTROL+C to copy.
4) Open your email and start a message to info@..., type a little about what you have done and what has happened in the body of the message, then leave a space and:
5) Press CONTROL+V to paste the copied log.

Instead of using the log viewer, or if NVDA has stopped and you needed to restart it or the computer:
1) Press WINDOWS+R to open Windows' Run dialog
2) Type %temp% and press ENTER (that's the percent sign, the letter t e m p and another percent sign).  Windows Explorer should open to the temporary folder.
3) Press TAB to move to the file list
4) Press N and move down to find up to three files:  nvda.log (the log file for the current or most recent NVDA session), nvda-old.og (the log from the previous session) and nvda-crash.dmp (a crash dump with more information created if NVDA itself crashes).
5) Depending on what email program you use, the steps will be different, but attach as many of those three files to an email to info@... as will be useful, and again in the body of the message describe a bit about what has happened.

If possible, could you please also forward a message which causes problems to me so that I can endeavour to replicate myself?  Ideally, instead of forwarding as you normally would, could you please forward as attachment?  In Outlook you can move to the message in the list, then press ALT+H, 0, 0, then F.

Sometimes when forwarding a message normally, the email client can alter the structure enough so that even though it looks the same, it might not cause exactly the same effects, (such as crashing NVDA).

Kind regards

Quentin.

On Wed, Jul 29, 2020 at 7:21 PM Christo Vorster <christo.vorster.klavierstem@...> wrote:

GAood Morning list

Please help!!

Regards

 

Christo Vorster (Worcester, south Africa)

 

This is the copy of the log:

 

INFO - __main__ (10:54:35.500) - MainThread (9268):

Starting NVDA version 2020.1

INFO - core.main (10:54:36.897) - MainThread (9268):

Config dir: C:\Users\Christo Vorster\AppData\Roaming\nvda

INFO - config.ConfigManager._loadConfig (10:54:36.897) - MainThread (9268):

Loading config: C:\Users\Christo Vorster\AppData\Roaming\nvda\nvda.ini

INFO - core.main (10:54:40.442) - MainThread (9268):

Using Windows version 10.0.19041 workstation

INFO - core.main (10:54:40.442) - MainThread (9268):

Using Python version 3.7.7 (tags/v3.7.7:d7c567b08f, Mar 10 2020, 09:44:33) [MSC v.1900 32 bit (Intel)]

INFO - core.main (10:54:40.442) - MainThread (9268):

Using comtypes version 1.1.7

INFO - core.main (10:54:40.442) - MainThread (9268):

Using configobj version 5.1.0 with validate version 1.0.1

INFO - synthDriverHandler.setSynth (10:54:48.280) - MainThread (9268):

Loaded synthDriver ibmeci

INFO - core.main (10:54:49.218) - MainThread (9268):

Using wx version 4.0.3 msw (phoenix) wxWidgets 3.0.5 with six version 1.12.0

INFO - brailleInput.initialize (10:54:49.220) - MainThread (9268):

Braille input initialized

INFO - braille.initialize (10:54:49.228) - MainThread (9268):

Using liblouis version 3.12.0

INFO - braille.initialize (10:54:49.241) - MainThread (9268):

Using pySerial version 3.4

INFO - braille.BrailleHandler.setDisplayByName (10:54:51.145) - MainThread (9268):

Loaded braille display driver noBraille, current display has 0 cells.

INFO - core.main (10:54:53.007) - MainThread (9268):

Java Access Bridge support initialized

INFO - _UIAHandler.UIAHandler.MTAThreadFunc (10:54:53.272) - _UIAHandler.UIAHandler.MTAThread (7440):

UIAutomation: IUIAutomation6

INFO - core.main (10:55:00.063) - MainThread (9268):

NVDA initialized

ERROR - eventHandler.executeEvent (11:07:11.977) - MainThread (9268):

error executing event: gainFocus on <appModules.outlook.UIAGridRow object at 0x079A43B0> with extra args of {}

Traceback (most recent call last):

  File "eventHandler.pyc", line 155, in executeEvent

  File "eventHandler.pyc", line 92, in __init__

  File "eventHandler.pyc", line 100, in next

  File "NVDAObjects\__init__.pyc", line 1102, in event_gainFocus

  File "NVDAObjects\behaviors.pyc", line 611, in reportFocus

  File "NVDAObjects\__init__.pyc", line 988, in reportFocus

  File "speech\__init__.pyc", line 469, in speakObject

  File "speech\__init__.pyc", line 506, in getObjectSpeech

  File "speech\__init__.pyc", line 377, in getObjectPropertiesSpeech

  File "baseObject.pyc", line 42, in __get__

  File "baseObject.pyc", line 145, in _getPropertyViaCache

  File "appModules\outlook.pyc", line 445, in _get_name

  File "comtypesMonkeyPatches.pyc", line 26, in __call__

_ctypes.COMError: (-2146233083, None, (None, None, None, 0, None))

ERROR - eventHandler.executeEvent (11:07:46.564) - MainThread (9268):

error executing event: gainFocus on <appModules.outlook.OutlookWordDocument object at 0x0708E250> with extra args of {}

Traceback (most recent call last):

  File "speech\__init__.pyc", line 512, in getObjectSpeech

  File "documentBase.pyc", line 24, in makeTextInfo

  File "NVDAObjects\window\winword.pyc", line 673, in __init__

AttributeError: 'NoneType' object has no attribute 'range'

 

During handling of the above exception, another exception occurred:

 

Traceback (most recent call last):

  File "eventHandler.pyc", line 155, in executeEvent

  File "eventHandler.pyc", line 92, in __init__

  File "eventHandler.pyc", line 100, in next

  File "NVDAObjects\__init__.pyc", line 1102, in event_gainFocus

  File "NVDAObjects\__init__.pyc", line 988, in reportFocus

  File "speech\__init__.pyc", line 469, in speakObject

  File "speech\__init__.pyc", line 527, in getObjectSpeech

  File "documentBase.pyc", line 24, in makeTextInfo

  File "NVDAObjects\window\winword.pyc", line 678, in __init__

AttributeError: 'NoneType' object has no attribute 'range'

ERROR - eventHandler.executeEvent (11:07:46.574) - MainThread (9268):

error executing event: caret on <appModules.outlook.OutlookWordDocument object at 0x0708E250> with extra args of {}

Traceback (most recent call last):

  File "eventHandler.pyc", line 155, in executeEvent

  File "eventHandler.pyc", line 92, in __init__

  File "eventHandler.pyc", line 100, in next

  File "NVDAObjects\IAccessible\winword.pyc", line 47, in event_caret

  File "documentBase.pyc", line 24, in makeTextInfo

  File "NVDAObjects\window\winword.pyc", line 673, in __init__

AttributeError: 'NoneType' object has no attribute 'range'

ERROR - eventHandler.executeEvent (11:07:46.595) - MainThread (9268):

error executing event: caret on <appModules.outlook.OutlookWordDocument object at 0x0708E250> with extra args of {}

Traceback (most recent call last):

  File "eventHandler.pyc", line 155, in executeEvent

  File "eventHandler.pyc", line 92, in __init__

  File "eventHandler.pyc", line 100, in next

  File "NVDAObjects\IAccessible\winword.pyc", line 47, in event_caret

  File "documentBase.pyc", line 24, in makeTextInfo

  File "NVDAObjects\window\winword.pyc", line 673, in __init__

AttributeError: 'NoneType' object has no attribute 'range'

 

 

 

I have a problem opening certain emails in Outlook 2016.

 

If NVDA is turned off, the specific mails can be opened.

 

I copied the View Log after I experienced the problem.

 

Would it help if I uninstall, and then re-install NVDA?

 

 



--
Quentin Christensen
Training and Support Manager