1. nvda@nvda.groups.io
  2. Messages
   Date   
Re: Browse Mode single letter quick navigation shortcuts

Rui Fontes
 

Hello!


If you press Escape, after that the keys work as expected?


Other possibility, press NVDA+Spacebar and try the keys...


Rui Fontes


Às 20:38 de 07/10/2021, Mike Adams escreveu:

> What is happening is nvda not changing to browse mode? in a web page?

Correct

> Is there some thing else grabbing the focus and you are stuck in focus mode?

It will read web pages, it will follow the mouse pointer, it will follow the tab key through links. But if i press H, X, 1 or any letter it just repeats the letter pressed back to me. It makes it frustrating to jump forward for our blind student in his known web pages (eg GMail in HTML mode)

> Is it only in the one browser or all of the browsers or nvda is saying unknown down on the running applications area.

All browsers though we use Chrome and Firefox with the blind student.

> I guess the first thing I would try is running the Run COM Registration Fixing tool... under the tools section in nvda and follow the directions.

Done, no change

> After that is done shut down the computer then start it up again and see if that fixes the problem.

Done, no change

> There have been updates in the nvda 2021.2 release for this tool so make sure you have this version of nvda.

I had and have. 

> We wil see if it makes a difference.

Sorry, none

> Gene nz

I saw, at least a year ago, a reference to a webpage that suggested making setup changes in Windows 10 to make it more NVDA friendly. I can no longer find that reference or the page. I'm sure it had a list of about 10 settings/registry changes/services that could be tweaked. We were still running Windows server 2012 at that time, and NVDA was behaving well. It has never worked correctly on this desktop.


Michael, Napier, Hawkes Bay


On Tue, 5 Oct 2021 at 15:06, hurrikennyandopo ... <hurrikennyandopo@...> wrote:

Hi


What is happening is nvda not changing to browse mode? in a web page?


Is there some thing else grabbing the focus and you are stuck in focus mode?


Is it only in the one browser or all of the browsers or nvda is saying unknown down on the running applications area.


I guess the first thing I would try is running the Run COM Registration Fixing tool... under the tools section in nvda and follow the directions.


After that is done shut down the computer then start it up again and see if that fixes the problem.


There have been updates in the nvda 2021.2 release for this tool so make sure you have this version of nvda.


We wil see if it makes a difference.


Gene nz


On 5/10/2021 1:53 pm, Mike Adams wrote:
NVDA Browse mode single letter quick navigation shortcuts (H for heading X for checkbox etc.) do not work on this computer. I remember coming across an online page which recommended settings for Windows 10, to make this work, but I have not found that page since. Anyone remember the page I am talking about?
 
Using:
Current NVDA + previous version
Windows 10 Pro V: 20H2 Build: 19042.1165
Windows is maintained by an external company, but I have good coms with them.
Re: Browse Mode single letter quick navigation shortcuts

Mike Adams
 

> What is happening is nvda not changing to browse mode? in a web page?

Correct

> Is there some thing else grabbing the focus and you are stuck in focus mode?

It will read web pages, it will follow the mouse pointer, it will follow the tab key through links. But if i press H, X, 1 or any letter it just repeats the letter pressed back to me. It makes it frustrating to jump forward for our blind student in his known web pages (eg GMail in HTML mode)

> Is it only in the one browser or all of the browsers or nvda is saying unknown down on the running applications area.

All browsers though we use Chrome and Firefox with the blind student.

> I guess the first thing I would try is running the Run COM Registration Fixing tool... under the tools section in nvda and follow the directions.

Done, no change

> After that is done shut down the computer then start it up again and see if that fixes the problem.

Done, no change

> There have been updates in the nvda 2021.2 release for this tool so make sure you have this version of nvda.

I had and have. 

> We wil see if it makes a difference.

Sorry, none

> Gene nz

I saw, at least a year ago, a reference to a webpage that suggested making setup changes in Windows 10 to make it more NVDA friendly. I can no longer find that reference or the page. I'm sure it had a list of about 10 settings/registry changes/services that could be tweaked. We were still running Windows server 2012 at that time, and NVDA was behaving well. It has never worked correctly on this desktop.


Michael, Napier, Hawkes Bay


On Tue, 5 Oct 2021 at 15:06, hurrikennyandopo ... <hurrikennyandopo@...> wrote:

Hi


What is happening is nvda not changing to browse mode? in a web page?


Is there some thing else grabbing the focus and you are stuck in focus mode?


Is it only in the one browser or all of the browsers or nvda is saying unknown down on the running applications area.


I guess the first thing I would try is running the Run COM Registration Fixing tool... under the tools section in nvda and follow the directions.


After that is done shut down the computer then start it up again and see if that fixes the problem.


There have been updates in the nvda 2021.2 release for this tool so make sure you have this version of nvda.


We wil see if it makes a difference.


Gene nz


On 5/10/2021 1:53 pm, Mike Adams wrote:
NVDA Browse mode single letter quick navigation shortcuts (H for heading X for checkbox etc.) do not work on this computer. I remember coming across an online page which recommended settings for Windows 10, to make this work, but I have not found that page since. Anyone remember the page I am talking about?
 
Using:
Current NVDA + previous version
Windows 10 Pro V: 20H2 Build: 19042.1165
Windows is maintained by an external company, but I have good coms with them.
Re: adobe reader 64 bit does not work with NVDA

enes sarıbaş
 

Hi Brian,

Going 64 bit is really benefitial for certain types of software, for example file compression software, antiviruses etc that use lots of memory and CPU cycles.  I will get around to nuking 64 bit reader, but I wish it had worked especially since Quentin on this list earlier had said he had no issues.

On 10/7/2021 9:49 PM, Brian Vogel wrote:
enes,

       I can say, with absolute certainty, that at one point (probably in the past) Microsoft explicitly instructed to use the 32-bit version of Office unless you needed something that could not be had without the 64-bit.

        But, my statement is about what we techs "on the ground" routinely advise, particularly after an issue has reared its ugly head with a 64-bit version of anything.  For lots of stuff I still just install the 32-bit because it's the "most focused upon" in the development cycles at the moment.  That's definitely going to change, and I wish it had changed ages ago, but there has always been a need to keep the 32-bit stuff "in tip top shape" since it can run under a 32-bit and 64-bit version of Windows.

        There's lots of 64-bit software, I'd say most of it, that you won't have a single, solitary problem with.  But if you are, or suspect you might based upon reports such as those made in this topic, and a 32-bit version exists, then nuke the 64-bit install and then install the 32-bit version.
--

Brian - Windows 10, 64-Bit, Version 21H1, Build 19043  

The ignorance of one voter in a democracy impairs the security of all.

         ~ John F. Kennedy

 
Re: adobe reader 64 bit does not work with NVDA

Brian Vogel
 

enes,

       I can say, with absolute certainty, that at one point (probably in the past) Microsoft explicitly instructed to use the 32-bit version of Office unless you needed something that could not be had without the 64-bit.

        But, my statement is about what we techs "on the ground" routinely advise, particularly after an issue has reared its ugly head with a 64-bit version of anything.  For lots of stuff I still just install the 32-bit because it's the "most focused upon" in the development cycles at the moment.  That's definitely going to change, and I wish it had changed ages ago, but there has always been a need to keep the 32-bit stuff "in tip top shape" since it can run under a 32-bit and 64-bit version of Windows.

        There's lots of 64-bit software, I'd say most of it, that you won't have a single, solitary problem with.  But if you are, or suspect you might based upon reports such as those made in this topic, and a 32-bit version exists, then nuke the 64-bit install and then install the 32-bit version.
--

Brian - Windows 10, 64-Bit, Version 21H1, Build 19043  

The ignorance of one voter in a democracy impairs the security of all.

         ~ John F. Kennedy

 
Re: adobe reader 64 bit does not work with NVDA

Gene
 

In the early days of 64 bit Firefox, I don’t recall hearing about performance problems with the browser, but there were not many 64 bit add-ons so switching meant that you were losing one of the important reasons a lot of people used Firefox.
 
Gene

-----Original Message-----
Sent: Thursday, October 07, 2021 1:01 PM
Subject: Re: [nvda] adobe reader 64 bit does not work with NVDA
 

Hi Brian,

I very much went against this advice, and installed 64 bit versions of file compression, format conversion, and office software etc.Even browsers, I was one of the early upgraders to Firefox 64 bit. Until Reader 64 bit, I had no issues whatsoever with 64 bit software.  Nor did I see any advice with Mozilla, Microsoft etc against choosing a 64 bit version.

 

On 10/7/2021 7:29 PM, Brian Vogel wrote:
On Thu, Oct 7, 2021 at 11:02 AM, Gene wrote:
This page appears to indicate that Windows 10 can run the 32 bit version but not Windows 11.
-
Gene,

You've somehow overlooked or misread the table on that page.  32-bit software remains supported under all 64-bit versions of Windows, including Windows 11.  And the table for the 32-bit version of Acrobat Reader states it runs under:

Windows 11 (64 bit), Windows 10 (32 bit and 64 bit) version 1809 or later, Windows 8, 8.1 (32 bit and 64 bit)†, Windows 7 SP1 (32 bit and 64 bit), or Windows Server - 2008 R2 (64 bit), 2012 (64 bit), 2012 R2 (64 bit)†, 2016 (64 bit), or 2019 (64 bit)

Windows 10 is the final version of Windows that has an actual 32-bit version of the Windows operating system, but that's a separate issue.  Most of us are running Windows 10 64-bit unless we have very old hardware, and most will still have been using the 32-bit versions of Acrobat Reader, Microsoft Office, and a number of other pieces of software that still "prefer" (for lack of a better way of putting it) to install their 32-bit versions by default and only use 64-bit when explicitly chosen.

It's still pretty much "the general advice" among techs that if a piece of software "has some age on it" and there exist both 32 and 64-bit versions, to install the 32-bit versions for a more trouble-free experience.  I fully expect that this is going to change in the years after Windows 11 becomes common as there will be no reason to focus on maintaining 32-bit and 64-bit versions, and 64-bit will definitely win out as time marches on.
 
--

Brian - Windows 10, 64-Bit, Version 21H1, Build 19043  

The ignorance of one voter in a democracy impairs the security of all.

         ~ John F. Kennedy

 
Re: adobe reader 64 bit does not work with NVDA

enes sarıbaş
 

Hi Brian,

I very much went against this advice, and installed 64 bit versions of file compression, format conversion, and office software etc.Even browsers, I was one of the early upgraders to Firefox 64 bit. Until Reader 64 bit, I had no issues whatsoever with 64 bit software.  Nor did I see any advice with Mozilla, Microsoft etc against choosing a 64 bit version.


On 10/7/2021 7:29 PM, Brian Vogel wrote:
On Thu, Oct 7, 2021 at 11:02 AM, Gene wrote:
This page appears to indicate that Windows 10 can run the 32 bit version but not Windows 11. 
-
Gene,

You've somehow overlooked or misread the table on that page.  32-bit software remains supported under all 64-bit versions of Windows, including Windows 11.  And the table for the 32-bit version of Acrobat Reader states it runs under:

Windows 11 (64 bit), Windows 10 (32 bit and 64 bit) version 1809 or later, Windows 8, 8.1 (32 bit and 64 bit)†, Windows 7 SP1 (32 bit and 64 bit), or Windows Server - 2008 R2 (64 bit), 2012 (64 bit), 2012 R2 (64 bit)†, 2016 (64 bit), or 2019 (64 bit)

Windows 10 is the final version of Windows that has an actual 32-bit version of the Windows operating system, but that's a separate issue.  Most of us are running Windows 10 64-bit unless we have very old hardware, and most will still have been using the 32-bit versions of Acrobat Reader, Microsoft Office, and a number of other pieces of software that still "prefer" (for lack of a better way of putting it) to install their 32-bit versions by default and only use 64-bit when explicitly chosen.

It's still pretty much "the general advice" among techs that if a piece of software "has some age on it" and there exist both 32 and 64-bit versions, to install the 32-bit versions for a more trouble-free experience.  I fully expect that this is going to change in the years after Windows 11 becomes common as there will be no reason to focus on maintaining 32-bit and 64-bit versions, and 64-bit will definitely win out as time marches on.
 
--

Brian - Windows 10, 64-Bit, Version 21H1, Build 19043  

The ignorance of one voter in a democracy impairs the security of all.

         ~ John F. Kennedy

 
Re: adobe reader 64 bit does not work with NVDA

Brian Vogel
 

On Thu, Oct 7, 2021 at 11:02 AM, Gene wrote:
This page appears to indicate that Windows 10 can run the 32 bit version but not Windows 11. 
-
Gene,

You've somehow overlooked or misread the table on that page.  32-bit software remains supported under all 64-bit versions of Windows, including Windows 11.  And the table for the 32-bit version of Acrobat Reader states it runs under:

Windows 11 (64 bit), Windows 10 (32 bit and 64 bit) version 1809 or later, Windows 8, 8.1 (32 bit and 64 bit)†, Windows 7 SP1 (32 bit and 64 bit), or Windows Server - 2008 R2 (64 bit), 2012 (64 bit), 2012 R2 (64 bit)†, 2016 (64 bit), or 2019 (64 bit)

Windows 10 is the final version of Windows that has an actual 32-bit version of the Windows operating system, but that's a separate issue.  Most of us are running Windows 10 64-bit unless we have very old hardware, and most will still have been using the 32-bit versions of Acrobat Reader, Microsoft Office, and a number of other pieces of software that still "prefer" (for lack of a better way of putting it) to install their 32-bit versions by default and only use 64-bit when explicitly chosen.

It's still pretty much "the general advice" among techs that if a piece of software "has some age on it" and there exist both 32 and 64-bit versions, to install the 32-bit versions for a more trouble-free experience.  I fully expect that this is going to change in the years after Windows 11 becomes common as there will be no reason to focus on maintaining 32-bit and 64-bit versions, and 64-bit will definitely win out as time marches on.
 
--

Brian - Windows 10, 64-Bit, Version 21H1, Build 19043  

The ignorance of one voter in a democracy impairs the security of all.

         ~ John F. Kennedy

 
locked Re: As Concerns Windows 11 Installation

Brian Vogel
 

This is a question that is off-topic for the NVDA group.  It has nothing, absolutely nothing, to do with NVDA.  This topic is locked as of the posting of this message.

It either belongs on the Chat Subgroup or, better if you're seeking answers regarding Windows-related topics as a screen reader user, the Windows Access with Screen Readers Group (Formerly: Windows 10 for Screen Reader Users Group)

Group Archive: https://winaccess.groups.io/g/winaccess/topics

Subscribe: winaccess+subscribe@winaccess.groups.io

Post: winaccess@winaccess.groups.io  

Unsubscribe: winaccess+unsubscribe@winaccess.groups.io  

Group Owner: winaccess+owner@winaccess.groups.io  

Help: winaccess+help@winaccess.groups.io  

 
What I wrote above is not aimed at Ron, specifically, but the membership in general.  The main NVDA group is not going to become a Windows 11, Windows Feature Update, or anything else directly related to Windows but utterly disconnected from NVDA group.  Please lets nip this trend in the bud, now.

--

Brian - Windows 10, 64-Bit, Version 21H1, Build 19043  

The ignorance of one voter in a democracy impairs the security of all.

         ~ John F. Kennedy

 
Re: adobe reader 64 bit does not work with NVDA

Rui Fontes
 

Downgrading, I don't believe...

But, you can remove the 64-bit version and install the 32-bit version.


It gaves always an error when starting, but it works...


Rui Fontes


Às 15:56 de 07/10/2021, enes sarıbaş escreveu:

I don't know if downgrading to 32 bit is even possible.   I am hoping someone from NVAccess would respond to this.

On 10/7/2021 5:51 PM, Christopher Duffley wrote:
OK...that's strange! Are you able to use another version of Adobe Reader for the time being? I'm not sure if NVAccess or someone in the add-ons community can do something about it, or better yet, Adobe themselves.

Thanks,

Christopher Duffley
Host of Mission Possible Podcast: http://www.missionpossiblepodcast.com
Cell: +1 (603) 851-6971

12 Pro Max

On Oct 7, 2021, at 10:42, enes sarıbaş <enes.saribas@...> wrote:



Hi,

It does persist after running the tool.

On 10/7/2021 4:41 PM, Christopher Duffley wrote:
Could you try running the COM Registry Fixing Tool in the Tools menu, then restart the machine, and see if this persists?

Thanks,

Christopher Duffley
Host of Mission Possible Podcast: http://www.missionpossiblepodcast.com
Cell: +1 (603) 851-6971

12 Pro Max

On Oct 7, 2021, at 08:07, enes sarıbaş <enes.saribas@...> wrote:

this sequence repeats in the log.

ERROR - RPC process 10084 (Acrobat.exe) (14:56:39.824) - Dummy-1229 (4232):
Thread 8124, build\x86_64\remote\COMProxyRegistration.cpp, registerCOMProxy, 182:
Unable to register interface IAccessibleHyperlink with proxy stub IAccessible2Proxy.dll, code -2147023156


On 10/7/2021 3:05 PM, enes sarıbaş wrote:
Hi all,

I am running latest windows 10 21h1, with NVDA latest alpha build   as of this writing.   Adobe reader 64 bit doesn't work at all.  When clicking on a document, it becomes unresponsive, and exits adobe reader within 30 seconds with no error message.  Is anyone else experiencing this?
Re: adobe reader 64 bit does not work with NVDA

Gene
 

This page appears to indicate that Windows 10 can run the 32 bit version but not Windows 11. 
 
Gene

-----Original Message-----
Sent: Thursday, October 07, 2021 9:56 AM
Subject: Re: [nvda] adobe reader 64 bit does not work with NVDA
 

I don't know if downgrading to 32 bit is even possible.   I am hoping someone from NVAccess would respond to this.

On 10/7/2021 5:51 PM, Christopher Duffley wrote:
OK...that's strange! Are you able to use another version of Adobe Reader for the time being? I'm not sure if NVAccess or someone in the add-ons community can do something about it, or better yet, Adobe themselves.
 
Thanks,
 
Christopher Duffley
Host of Mission Possible Podcast: http://www.missionpossiblepodcast.com
Cell: +1 (603) 851-6971
 
12 Pro Max

On Oct 7, 2021, at 10:42, enes sarıbaş mailto:enes.saribas@... wrote:



Hi,

It does persist after running the tool.

On 10/7/2021 4:41 PM, Christopher Duffley wrote:
Could you try running the COM Registry Fixing Tool in the Tools menu, then restart the machine, and see if this persists?
 
Thanks,
 
Christopher Duffley
Host of Mission Possible Podcast: http://www.missionpossiblepodcast.com
Cell: +1 (603) 851-6971
 
12 Pro Max

On Oct 7, 2021, at 08:07, enes sarıbaş mailto:enes.saribas@... wrote:

this sequence repeats in the log.

ERROR - RPC process 10084 (Acrobat.exe) (14:56:39.824) - Dummy-1229 (4232):
Thread 8124, build\x86_64\remote\COMProxyRegistration.cpp, registerCOMProxy, 182:
Unable to register interface IAccessibleHyperlink with proxy stub IAccessible2Proxy.dll, code -2147023156


On 10/7/2021 3:05 PM, enes sarıbaş wrote:
Hi all,

I am running latest windows 10 21h1, with NVDA latest alpha build   as of this writing.   Adobe reader 64 bit doesn't work at all.  When clicking on a document, it becomes unresponsive, and exits adobe reader within 30 seconds with no error message.  Is anyone else experiencing this?
Re: adobe reader 64 bit does not work with NVDA

enes sarıbaş
 

I don't know if downgrading to 32 bit is even possible.   I am hoping someone from NVAccess would respond to this.

On 10/7/2021 5:51 PM, Christopher Duffley wrote:
OK...that's strange! Are you able to use another version of Adobe Reader for the time being? I'm not sure if NVAccess or someone in the add-ons community can do something about it, or better yet, Adobe themselves.

Thanks,

Christopher Duffley
Host of Mission Possible Podcast: http://www.missionpossiblepodcast.com
Cell: +1 (603) 851-6971

12 Pro Max

On Oct 7, 2021, at 10:42, enes sarıbaş <enes.saribas@...> wrote:



Hi,

It does persist after running the tool.

On 10/7/2021 4:41 PM, Christopher Duffley wrote:
Could you try running the COM Registry Fixing Tool in the Tools menu, then restart the machine, and see if this persists?

Thanks,

Christopher Duffley
Host of Mission Possible Podcast: http://www.missionpossiblepodcast.com
Cell: +1 (603) 851-6971

12 Pro Max

On Oct 7, 2021, at 08:07, enes sarıbaş <enes.saribas@...> wrote:

this sequence repeats in the log.

ERROR - RPC process 10084 (Acrobat.exe) (14:56:39.824) - Dummy-1229 (4232):
Thread 8124, build\x86_64\remote\COMProxyRegistration.cpp, registerCOMProxy, 182:
Unable to register interface IAccessibleHyperlink with proxy stub IAccessible2Proxy.dll, code -2147023156


On 10/7/2021 3:05 PM, enes sarıbaş wrote:
Hi all,

I am running latest windows 10 21h1, with NVDA latest alpha build   as of this writing.   Adobe reader 64 bit doesn't work at all.  When clicking on a document, it becomes unresponsive, and exits adobe reader within 30 seconds with no error message.  Is anyone else experiencing this?
Re: adobe reader 64 bit does not work with NVDA

Christopher Duffley
 

OK...that's strange! Are you able to use another version of Adobe Reader for the time being? I'm not sure if NVAccess or someone in the add-ons community can do something about it, or better yet, Adobe themselves.

Thanks,

Christopher Duffley
Host of Mission Possible Podcast: http://www.missionpossiblepodcast.com
Cell: +1 (603) 851-6971

12 Pro Max

On Oct 7, 2021, at 10:42, enes sarıbaş <enes.saribas@...> wrote:



Hi,

It does persist after running the tool.

On 10/7/2021 4:41 PM, Christopher Duffley wrote:
Could you try running the COM Registry Fixing Tool in the Tools menu, then restart the machine, and see if this persists?

Thanks,

Christopher Duffley
Host of Mission Possible Podcast: http://www.missionpossiblepodcast.com
Cell: +1 (603) 851-6971

12 Pro Max

On Oct 7, 2021, at 08:07, enes sarıbaş <enes.saribas@...> wrote:

this sequence repeats in the log.

ERROR - RPC process 10084 (Acrobat.exe) (14:56:39.824) - Dummy-1229 (4232):
Thread 8124, build\x86_64\remote\COMProxyRegistration.cpp, registerCOMProxy, 182:
Unable to register interface IAccessibleHyperlink with proxy stub IAccessible2Proxy.dll, code -2147023156


On 10/7/2021 3:05 PM, enes sarıbaş wrote:
Hi all,

I am running latest windows 10 21h1, with NVDA latest alpha build   as of this writing.   Adobe reader 64 bit doesn't work at all.  When clicking on a document, it becomes unresponsive, and exits adobe reader within 30 seconds with no error message.  Is anyone else experiencing this?
Re: adobe reader 64 bit does not work with NVDA

enes sarıbaş
 

Hi,

It does persist after running the tool.

On 10/7/2021 4:41 PM, Christopher Duffley wrote:
Could you try running the COM Registry Fixing Tool in the Tools menu, then restart the machine, and see if this persists?

Thanks,

Christopher Duffley
Host of Mission Possible Podcast: http://www.missionpossiblepodcast.com
Cell: +1 (603) 851-6971

12 Pro Max

On Oct 7, 2021, at 08:07, enes sarıbaş <enes.saribas@...> wrote:

this sequence repeats in the log.

ERROR - RPC process 10084 (Acrobat.exe) (14:56:39.824) - Dummy-1229 (4232):
Thread 8124, build\x86_64\remote\COMProxyRegistration.cpp, registerCOMProxy, 182:
Unable to register interface IAccessibleHyperlink with proxy stub IAccessible2Proxy.dll, code -2147023156


On 10/7/2021 3:05 PM, enes sarıbaş wrote:
Hi all,

I am running latest windows 10 21h1, with NVDA latest alpha build   as of this writing.   Adobe reader 64 bit doesn't work at all.  When clicking on a document, it becomes unresponsive, and exits adobe reader within 30 seconds with no error message.  Is anyone else experiencing this?
Re: adobe reader 64 bit does not work with NVDA

Christopher Duffley
 

Could you try running the COM Registry Fixing Tool in the Tools menu, then restart the machine, and see if this persists?

Thanks,

Christopher Duffley
Host of Mission Possible Podcast: http://www.missionpossiblepodcast.com
Cell: +1 (603) 851-6971

12 Pro Max

On Oct 7, 2021, at 08:07, enes sarıbaş <enes.saribas@...> wrote:

this sequence repeats in the log.

ERROR - RPC process 10084 (Acrobat.exe) (14:56:39.824) - Dummy-1229 (4232):
Thread 8124, build\x86_64\remote\COMProxyRegistration.cpp, registerCOMProxy, 182:
Unable to register interface IAccessibleHyperlink with proxy stub IAccessible2Proxy.dll, code -2147023156


On 10/7/2021 3:05 PM, enes sarıbaş wrote:
Hi all,

I am running latest windows 10 21h1, with NVDA latest alpha build   as of this writing.   Adobe reader 64 bit doesn't work at all.  When clicking on a document, it becomes unresponsive, and exits adobe reader within 30 seconds with no error message.  Is anyone else experiencing this?
Re: Equivalent to Jaw's Screen Echo

Gene
 

Not when first turned on.  Nothing has changed on screen and a new screen hasn’t been ;presented.  If you justturn it on, it does nothing. 
 
Gene

-----Original Message-----
From: Steve Nutt
Sent: Thursday, October 07, 2021 6:28 AM
Subject: Re: [nvda] Equivalent to Jaw's Screen Echo
 

You’re right David, I just tried it. It doesn’t echo anything when first turned on.

 

All the best


Steve

 

--

To subscribe to our News and Special Offers list, go to https://www.comproom.co.uk/subscribe

 

Computer Room Services

77 Exeter Close

Stevenage

Hertfordshire

SG1 4PW

T: +44(0)1438-742286

M: +44(0)7956-334938

F: +44(0)1438-759589

E: steve@...

W: https://www.comproom.co.uk

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of David Goldfield
Sent: 07 October 2021 10:43
To: nvda@nvda.groups.io
Subject: Re: [nvda] Equivalent to Jaw's Screen Echo

 

My only disagreement with Steve’s description is that when you set the JAWS screen echo to “all” it does not automatically speak the contents of the screen.

This is not particularly detailed but here is the relevant description taken from the JAWS help system:

Screen Echo

This option allows you to select what information is echoed when text on the screen changes.

  • Off: Changes to displayed text are not echoed.
  • Highlighted: Changes to highlighted text are echoed. This is the default setting.
  • All: Changes to any displayed text are echoed.

 

David Goldfield,

Blindness Assistive Technology Specialist

JAWS Certified, 2019

Subscribe to the Tech-VI announcement list to receive emails regarding news and events in the blindness assistive technology field.

Email: tech-vi+subscribe@groups.io

 

www.DavidGoldfield.org

 

 

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Steve Nutt
Sent: Thursday, October 7, 2021 3:59 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Equivalent to Jaw's Screen Echo

 

Hi Quentin,

 

Essentially, it does exactly as described earlier down the thread.

 

When you enable it, it echoes the whole screen once. Then it monitors for changes and echoes them.

 

This is very useful for accessibility testing. It’s probably not a mainstream feature that everyone could use, but it would be helpful to have it.

 

All the best


Steve

 

--

To subscribe to our News and Special Offers list, go to https://www.comproom.co.uk/subscribe

 

Computer Room Services

77 Exeter Close

Stevenage

Hertfordshire

SG1 4PW

T: +44(0)1438-742286

M: +44(0)7956-334938

F: +44(0)1438-759589

E: steve@...

W: https://www.comproom.co.uk

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Quentin Christensen
Sent: 06 October 2021 22:41
To: nvda@nvda.groups.io
Subject: Re: [nvda] Equivalent to Jaw's Screen Echo

 

Perhaps what would be helpful here would be for someone familiar with the Jaws feature, to please describe how it works for the user?  Ok, so I'm a user, I have a program which doesn't seem to be accessible, I launch this feature.... what does it do?

 

With a number of features, it may be that there is a solution to a problem, and it may or may not be identical to the way Jaws does it, and I think sometimes we get stuck on "this is what Jaws does, I want it to work the same", rather than "this is the problem I'm trying to solve, is there a solution"?

 

On Thu, Oct 7, 2021 at 2:42 AM Brian Vogel <britechguy@...> wrote:

On Wed, Oct 6, 2021 at 10:07 AM, Gene wrote:

Not having both of these options imposes limitations that should be discussed unless there is a technical reason that they can’t be implemented.

-
Gene,

There are multitudes of things that could, potentially, be implemented but that are not because the need for same is so infrequent and/or other things have higher priority.  I say that not as a criticism of you, but in reaction to an observation that's often repeated that has the underlying belief that because someone, somewhere, once in a blue moon might be able to use a feature that it should be implemented.  That's not always the case.

And in an instance such as this one, it makes way more sense to pursue accessibility improvements through the developers of the apps, rather than having the screen reader(s) workaround what is clearly bad to non-existent accessibility in the software design itself.
--

Brian - Windows 10, 64-Bit, Version 21H1, Build 19043  

The ignorance of one voter in a democracy impairs the security of all.

         ~ John F. Kennedy

 


 

--

Quentin Christensen
Training and Support Manager

 
Re: Equivalent to Jaw's Screen Echo

Gene
 

This comment is based on my recollection and my experimentation now with a very old version of JAWS.  I haven’t used JAWS for a long time and I haven’t updated  it.  This needs to be checked or confirmed as the current behavior. 
 
The description isn’t completely accurate.  I can cause either all or most of the screen to be automatically echoed at times and at other times, only new or changed text is echoed.  I don’t know just when either happens. 
 
Gene

------Original Message-----
Sent: Thursday, October 07, 2021 4:42 AM
Subject: Re: [nvda] Equivalent to Jaw's Screen Echo
 

My only disagreement with Steve’s description is that when you set the JAWS screen echo to “all” it does not automatically speak the contents of the screen.

This is not particularly detailed but here is the relevant description taken from the JAWS help system:

Screen Echo

This option allows you to select what information is echoed when text on the screen changes.

  • Off: Changes to displayed text are not echoed.
  • Highlighted: Changes to highlighted text are echoed. This is the default setting.
  • All: Changes to any displayed text are echoed.

 

David Goldfield,

Blindness Assistive Technology Specialist

JAWS Certified, 2019

Subscribe to the Tech-VI announcement list to receive emails regarding news and events in the blindness assistive technology field.

Email: tech-vi+subscribe@groups.io

 

www.DavidGoldfield.org

 

 

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Steve Nutt
Sent: Thursday, October 7, 2021 3:59 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Equivalent to Jaw's Screen Echo

 

Hi Quentin,

 

Essentially, it does exactly as described earlier down the thread.

 

When you enable it, it echoes the whole screen once. Then it monitors for changes and echoes them.

 

This is very useful for accessibility testing. It’s probably not a mainstream feature that everyone could use, but it would be helpful to have it.

 

All the best


Steve

 

--

To subscribe to our News and Special Offers list, go to https://www.comproom.co.uk/subscribe

 

Computer Room Services

77 Exeter Close

Stevenage

Hertfordshire

SG1 4PW

T: +44(0)1438-742286

M: +44(0)7956-334938

F: +44(0)1438-759589

E: steve@...

W: https://www.comproom.co.uk

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Quentin Christensen
Sent: 06 October 2021 22:41
To: nvda@nvda.groups.io
Subject: Re: [nvda] Equivalent to Jaw's Screen Echo

 

Perhaps what would be helpful here would be for someone familiar with the Jaws feature, to please describe how it works for the user?  Ok, so I'm a user, I have a program which doesn't seem to be accessible, I launch this feature.... what does it do?

 

With a number of features, it may be that there is a solution to a problem, and it may or may not be identical to the way Jaws does it, and I think sometimes we get stuck on "this is what Jaws does, I want it to work the same", rather than "this is the problem I'm trying to solve, is there a solution"?

 

On Thu, Oct 7, 2021 at 2:42 AM Brian Vogel <britechguy@...> wrote:

On Wed, Oct 6, 2021 at 10:07 AM, Gene wrote:

Not having both of these options imposes limitations that should be discussed unless there is a technical reason that they can’t be implemented.

-
Gene,

There are multitudes of things that could, potentially, be implemented but that are not because the need for same is so infrequent and/or other things have higher priority.  I say that not as a criticism of you, but in reaction to an observation that's often repeated that has the underlying belief that because someone, somewhere, once in a blue moon might be able to use a feature that it should be implemented.  That's not always the case.

And in an instance such as this one, it makes way more sense to pursue accessibility improvements through the developers of the apps, rather than having the screen reader(s) workaround what is clearly bad to non-existent accessibility in the software design itself.
--

Brian - Windows 10, 64-Bit, Version 21H1, Build 19043  

The ignorance of one voter in a democracy impairs the security of all.

         ~ John F. Kennedy

 


 

--

Quentin Christensen
Training and Support Manager

 
Re: adobe reader 64 bit does not work with NVDA

enes sarıbaş
 

this sequence repeats in the log.

ERROR - RPC process 10084 (Acrobat.exe) (14:56:39.824) - Dummy-1229 (4232):
Thread 8124, build\x86_64\remote\COMProxyRegistration.cpp, registerCOMProxy, 182:
Unable to register interface IAccessibleHyperlink with proxy stub IAccessible2Proxy.dll, code -2147023156

On 10/7/2021 3:05 PM, enes sarıbaş wrote:
Hi all,

I am running latest windows 10 21h1, with NVDA latest alpha build   as of this writing.   Adobe reader 64 bit doesn't work at all.  When clicking on a document, it becomes unresponsive, and exits adobe reader within 30 seconds with no error message.  Is anyone else experiencing this?
adobe reader 64 bit does not work with NVDA

enes sarıbaş
 

Hi all,

I am running latest windows 10 21h1, with NVDA latest alpha build   as of this writing.   Adobe reader 64 bit doesn't work at all.  When clicking on a document, it becomes unresponsive, and exits adobe reader within 30 seconds with no error message.  Is anyone else experiencing this?
Re: Equivalent to Jaw's Screen Echo

David Goldfield
 

Thanks for confirming this, Steve.

It’s one of those nice to have features but, for me, it is not essential. I occasionally use it for apps which frequently update the screen, such as when I copy a large number of files from one folder to another or when installing a piece of software where I want to automatically hear all of the changes which are taking place. Having all screen changes announced during such events is convenient but, again, not essential, at least for me. With NVDA I can always just use its review cursor to manually review screen updates. For most situations most of the time I never need to rely on it but someone else’s use case might dictate otherwise.

For those individuals I would say that filing this as a feature request in NVDA’s Github would be appropriate.

David Goldfield,

Blindness Assistive Technology Specialist

JAWS Certified, 2019

Subscribe to the Tech-VI announcement list to receive emails regarding news and events in the blindness assistive technology field.

Email: tech-vi+subscribe@groups.io

 

www.DavidGoldfield.org

 

 

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Steve Nutt
Sent: Thursday, October 7, 2021 7:29 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Equivalent to Jaw's Screen Echo

 

You’re right David, I just tried it. It doesn’t echo anything when first turned on.

 

All the best


Steve

 

--

To subscribe to our News and Special Offers list, go to https://www.comproom.co.uk/subscribe

 

Computer Room Services

77 Exeter Close

Stevenage

Hertfordshire

SG1 4PW

T: +44(0)1438-742286

M: +44(0)7956-334938

F: +44(0)1438-759589

E: steve@...

W: https://www.comproom.co.uk

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of David Goldfield
Sent: 07 October 2021 10:43
To: nvda@nvda.groups.io
Subject: Re: [nvda] Equivalent to Jaw's Screen Echo

 

My only disagreement with Steve’s description is that when you set the JAWS screen echo to “all” it does not automatically speak the contents of the screen.

This is not particularly detailed but here is the relevant description taken from the JAWS help system:

Screen Echo

This option allows you to select what information is echoed when text on the screen changes.

  • Off: Changes to displayed text are not echoed.
  • Highlighted: Changes to highlighted text are echoed. This is the default setting.
  • All: Changes to any displayed text are echoed.

 

David Goldfield,

Blindness Assistive Technology Specialist

JAWS Certified, 2019

Subscribe to the Tech-VI announcement list to receive emails regarding news and events in the blindness assistive technology field.

Email: tech-vi+subscribe@groups.io

 

www.DavidGoldfield.org

 

 

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Steve Nutt
Sent: Thursday, October 7, 2021 3:59 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Equivalent to Jaw's Screen Echo

 

Hi Quentin,

 

Essentially, it does exactly as described earlier down the thread.

 

When you enable it, it echoes the whole screen once. Then it monitors for changes and echoes them.

 

This is very useful for accessibility testing. It’s probably not a mainstream feature that everyone could use, but it would be helpful to have it.

 

All the best


Steve

 

--

To subscribe to our News and Special Offers list, go to https://www.comproom.co.uk/subscribe

 

Computer Room Services

77 Exeter Close

Stevenage

Hertfordshire

SG1 4PW

T: +44(0)1438-742286

M: +44(0)7956-334938

F: +44(0)1438-759589

E: steve@...

W: https://www.comproom.co.uk

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Quentin Christensen
Sent: 06 October 2021 22:41
To: nvda@nvda.groups.io
Subject: Re: [nvda] Equivalent to Jaw's Screen Echo

 

Perhaps what would be helpful here would be for someone familiar with the Jaws feature, to please describe how it works for the user?  Ok, so I'm a user, I have a program which doesn't seem to be accessible, I launch this feature.... what does it do?

 

With a number of features, it may be that there is a solution to a problem, and it may or may not be identical to the way Jaws does it, and I think sometimes we get stuck on "this is what Jaws does, I want it to work the same", rather than "this is the problem I'm trying to solve, is there a solution"?

 

On Thu, Oct 7, 2021 at 2:42 AM Brian Vogel <britechguy@...> wrote:

On Wed, Oct 6, 2021 at 10:07 AM, Gene wrote:

Not having both of these options imposes limitations that should be discussed unless there is a technical reason that they can’t be implemented.

-
Gene,

There are multitudes of things that could, potentially, be implemented but that are not because the need for same is so infrequent and/or other things have higher priority.  I say that not as a criticism of you, but in reaction to an observation that's often repeated that has the underlying belief that because someone, somewhere, once in a blue moon might be able to use a feature that it should be implemented.  That's not always the case.

And in an instance such as this one, it makes way more sense to pursue accessibility improvements through the developers of the apps, rather than having the screen reader(s) workaround what is clearly bad to non-existent accessibility in the software design itself.
--

Brian - Windows 10, 64-Bit, Version 21H1, Build 19043  

The ignorance of one voter in a democracy impairs the security of all.

         ~ John F. Kennedy

 


 

--

Quentin Christensen
Training and Support Manager

 
Re: Equivalent to Jaw's Screen Echo

Steve Nutt
 

You’re right David, I just tried it. It doesn’t echo anything when first turned on.

 

All the best


Steve

 

--

To subscribe to our News and Special Offers list, go to https://www.comproom.co.uk/subscribe

 

Computer Room Services

77 Exeter Close

Stevenage

Hertfordshire

SG1 4PW

T: +44(0)1438-742286

M: +44(0)7956-334938

F: +44(0)1438-759589

E: steve@...

W: https://www.comproom.co.uk

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of David Goldfield
Sent: 07 October 2021 10:43
To: nvda@nvda.groups.io
Subject: Re: [nvda] Equivalent to Jaw's Screen Echo

 

My only disagreement with Steve’s description is that when you set the JAWS screen echo to “all” it does not automatically speak the contents of the screen.

This is not particularly detailed but here is the relevant description taken from the JAWS help system:

Screen Echo

This option allows you to select what information is echoed when text on the screen changes.

  • Off: Changes to displayed text are not echoed.
  • Highlighted: Changes to highlighted text are echoed. This is the default setting.
  • All: Changes to any displayed text are echoed.

 

David Goldfield,

Blindness Assistive Technology Specialist

JAWS Certified, 2019

Subscribe to the Tech-VI announcement list to receive emails regarding news and events in the blindness assistive technology field.

Email: tech-vi+subscribe@groups.io

 

www.DavidGoldfield.org

 

 

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Steve Nutt
Sent: Thursday, October 7, 2021 3:59 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Equivalent to Jaw's Screen Echo

 

Hi Quentin,

 

Essentially, it does exactly as described earlier down the thread.

 

When you enable it, it echoes the whole screen once. Then it monitors for changes and echoes them.

 

This is very useful for accessibility testing. It’s probably not a mainstream feature that everyone could use, but it would be helpful to have it.

 

All the best


Steve

 

--

To subscribe to our News and Special Offers list, go to https://www.comproom.co.uk/subscribe

 

Computer Room Services

77 Exeter Close

Stevenage

Hertfordshire

SG1 4PW

T: +44(0)1438-742286

M: +44(0)7956-334938

F: +44(0)1438-759589

E: steve@...

W: https://www.comproom.co.uk

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Quentin Christensen
Sent: 06 October 2021 22:41
To: nvda@nvda.groups.io
Subject: Re: [nvda] Equivalent to Jaw's Screen Echo

 

Perhaps what would be helpful here would be for someone familiar with the Jaws feature, to please describe how it works for the user?  Ok, so I'm a user, I have a program which doesn't seem to be accessible, I launch this feature.... what does it do?

 

With a number of features, it may be that there is a solution to a problem, and it may or may not be identical to the way Jaws does it, and I think sometimes we get stuck on "this is what Jaws does, I want it to work the same", rather than "this is the problem I'm trying to solve, is there a solution"?

 

On Thu, Oct 7, 2021 at 2:42 AM Brian Vogel <britechguy@...> wrote:

On Wed, Oct 6, 2021 at 10:07 AM, Gene wrote:

Not having both of these options imposes limitations that should be discussed unless there is a technical reason that they can’t be implemented.

-
Gene,

There are multitudes of things that could, potentially, be implemented but that are not because the need for same is so infrequent and/or other things have higher priority.  I say that not as a criticism of you, but in reaction to an observation that's often repeated that has the underlying belief that because someone, somewhere, once in a blue moon might be able to use a feature that it should be implemented.  That's not always the case.

And in an instance such as this one, it makes way more sense to pursue accessibility improvements through the developers of the apps, rather than having the screen reader(s) workaround what is clearly bad to non-existent accessibility in the software design itself.
--

Brian - Windows 10, 64-Bit, Version 21H1, Build 19043  

The ignorance of one voter in a democracy impairs the security of all.

         ~ John F. Kennedy

 


 

--

Quentin Christensen
Training and Support Manager

 
8561 - 8580 of 96817