Date   
NVDA not announcing listview items in TortoiseSVN commit dialog

Petr Řehák
 

Hello,

 

When using TortoiseSVN to commit, after the commit finishes a list view is displayed reporting items which were committed. Items as such are being announced but with no text, you hear just "selected". Following is the NVDA log excerpt:

ERROR - eventHandler.executeEvent (08:42:02.983) - MainThread (18740):

error executing event: gainFocus on <NVDAObjects.IAccessible.sysListView32.ListItem object at 0x07B50250> 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 "C:\Users\Uzivatel\AppData\Roaming\nvda\addons\remote\globalPlugins\remoteClient\__init__.py", line 426, in event_gainFocus

    nextHandler()

  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 485, in speakObject

  File "speech\__init__.pyc", line 318, in speakObjectProperties

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

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

  File "NVDAObjects\IAccessible\sysListView32.pyc", line 438, in _get_name

  File "NVDAObjects\IAccessible\sysListView32.pyc", line 382, in _getColumnContent

  File "NVDAObjects\IAccessible\sysListView32.pyc", line 374, in _getColumnContentRaw

  File "winKernel.pyc", line 219, in readProcessMemory

ctypes.ArgumentError: argument 2: <class 'OverflowError'>: int too long to convert

ERROR - eventHandler.executeEvent (08:42:04.208) - MainThread (18740):

error executing event: gainFocus on <NVDAObjects.IAccessible.sysListView32.ListItem object at 0x008981F0> 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 "C:\Users\Uzivatel\AppData\Roaming\nvda\addons\remote\globalPlugins\remoteClient\__init__.py", line 426, in event_gainFocus

    nextHandler()

  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 485, in speakObject

  File "speech\__init__.pyc", line 318, in speakObjectProperties

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

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

  File "NVDAObjects\IAccessible\sysListView32.pyc", line 438, in _get_name

  File "NVDAObjects\IAccessible\sysListView32.pyc", line 382, in _getColumnContent

  File "NVDAObjects\IAccessible\sysListView32.pyc", line 374, in _getColumnContentRaw

  File "winKernel.pyc", line 219, in readProcessMemory

ctypes.ArgumentError: argument 2: <class 'OverflowError'>: int too long to convert

ERROR - eventHandler.executeEvent (08:42:04.579) - MainThread (18740):

error executing event: gainFocus on <NVDAObjects.IAccessible.sysListView32.ListItem object at 0x00898BD0> 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 "C:\Users\Uzivatel\AppData\Roaming\nvda\addons\remote\globalPlugins\remoteClient\__init__.py", line 426, in event_gainFocus

    nextHandler()

  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 485, in speakObject

  File "speech\__init__.pyc", line 318, in speakObjectProperties

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

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

  File "NVDAObjects\IAccessible\sysListView32.pyc", line 438, in _get_name

  File "NVDAObjects\IAccessible\sysListView32.pyc", line 382, in _getColumnContent

  File "NVDAObjects\IAccessible\sysListView32.pyc", line 374, in _getColumnContentRaw

  File "winKernel.pyc", line 219, in readProcessMemory

ctypes.ArgumentError: argument 2: <class 'OverflowError'>: int too long to convert

ERROR - eventHandler.executeEvent (08:42:04.833) - MainThread (18740):

error executing event: gainFocus on <NVDAObjects.IAccessible.sysListView32.ListItem object at 0x00898CB0> 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 "C:\Users\Uzivatel\AppData\Roaming\nvda\addons\remote\globalPlugins\remoteClient\__init__.py", line 426, in event_gainFocus

    nextHandler()

  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 485, in speakObject

  File "speech\__init__.pyc", line 318, in speakObjectProperties

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

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

  File "NVDAObjects\IAccessible\sysListView32.pyc", line 438, in _get_name

  File "NVDAObjects\IAccessible\sysListView32.pyc", line 382, in _getColumnContent

  File "NVDAObjects\IAccessible\sysListView32.pyc", line 374, in _getColumnContentRaw

  File "winKernel.pyc", line 219, in readProcessMemory

ctypes.ArgumentError: argument 2: <class 'OverflowError'>: int too long to convert

ERROR - eventHandler.executeEvent (08:42:08.422) - MainThread (18740):

error executing event: gainFocus on <NVDAObjects.IAccessible.sysListView32.ListItem object at 0x030DABF0> 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 "C:\Users\Uzivatel\AppData\Roaming\nvda\addons\remote\globalPlugins\remoteClient\__init__.py", line 426, in event_gainFocus

    nextHandler()

  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 485, in speakObject

  File "speech\__init__.pyc", line 318, in speakObjectProperties

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

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

  File "NVDAObjects\IAccessible\sysListView32.pyc", line 438, in _get_name

  File "NVDAObjects\IAccessible\sysListView32.pyc", line 382, in _getColumnContent

  File "NVDAObjects\IAccessible\sysListView32.pyc", line 374, in _getColumnContentRaw

  File "winKernel.pyc", line 219, in readProcessMemory

ctypes.ArgumentError: argument 2: <class 'OverflowError'>: int too long to convert

ERROR - eventHandler.executeEvent (08:42:10.143) - MainThread (18740):

error executing event: gainFocus on <NVDAObjects.IAccessible.sysListView32.ListItem object at 0x030DAB10> 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 "C:\Users\Uzivatel\AppData\Roaming\nvda\addons\remote\globalPlugins\remoteClient\__init__.py", line 426, in event_gainFocus

    nextHandler()

  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 485, in speakObject

  File "speech\__init__.pyc", line 318, in speakObjectProperties

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

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

  File "NVDAObjects\IAccessible\sysListView32.pyc", line 438, in _get_name

  File "NVDAObjects\IAccessible\sysListView32.pyc", line 382, in _getColumnContent

  File "NVDAObjects\IAccessible\sysListView32.pyc", line 374, in _getColumnContentRaw

  File "winKernel.pyc", line 219, in readProcessMemory

ctypes.ArgumentError: argument 2: <class 'OverflowError'>: int too long to convert

INFO - globalCommands.GlobalCommands.script_navigatorObject_devInfo (08:42:13.175) - MainThread (18740):

Developer info for navigator object:

name: exception: argument 2: <class 'OverflowError'>: int too long to convert

role: ROLE_LISTITEM

roleText: None

states: STATE_FOCUSABLE, STATE_SELECTABLE, STATE_FOCUSED, STATE_SELECTED

isFocusable: True

hasFocus: True

Python object: <NVDAObjects.IAccessible.sysListView32.ListItem object at 0x030DAB10>

Python class mro: (<class 'NVDAObjects.IAccessible.sysListView32.ListItem'>, <class 'NVDAObjects.behaviors.RowWithFakeNavigation'>, <class 'NVDAObjects.behaviors.RowWithoutCellObjects'>, <class 'NVDAObjects.IAccessible.sysListView32.ListItemWithoutColumnSupport'>, <class 'NVDAObjects.IAccessible.IAccessible'>, <class 'NVDAObjects.window.Window'>, <class 'NVDAObjects.NVDAObject'>, <class 'documentBase.TextContainerObject'>, <class 'baseObject.ScriptableObject'>, <class 'baseObject.AutoPropertyObject'>, <class 'object'>)

description: None

location: RectLTWH(left=14, top=133, width=894, height=18)

value: None

appModule: <'appModuleHandler' (appName 'tortoiseproc', process ID 13528) at address ac69f0>

appModule.productName: 'TortoiseSVN'

appModule.productVersion: '1.11.0.28416'

TextInfo: <class 'NVDAObjects.NVDAObjectTextInfo'>

windowHandle: 396098

windowClassName: 'SysListView32'

windowControlID: 1013

windowStyle: 1342248961

extendedWindowStyle: 516

windowThreadID: 10052

windowText: ''

displayText: 'Dokončeno Na revizi: 76'

IAccessibleObject: <POINTER(IAccessible) ptr=0x515dec8 at d0eb70>

IAccessibleChildID: 5

IAccessible event parameters: windowHandle=396098, objectID=-4, childID=5

IAccessible accName: None

IAccessible accRole: ROLE_SYSTEM_LISTITEM

IAccessible accState: STATE_SYSTEM_SELECTED, STATE_SYSTEM_FOCUSED, STATE_SYSTEM_FOCUSABLE, STATE_SYSTEM_SELECTABLE, STATE_SYSTEM_MULTISELECTABLE, STATE_SYSTEM_VALID (19922950)

IAccessible accDescription: None

IAccessible accValue: None

 

Best regards,

 

Petr Řehák

 

Odesláno z aplikace Pošta pro Windows 10

 

Re: Serious issue with NVDA not reading menus and totally silent in Firefox and Chrome

Mallard
 

Oh, and I forgot to say that my friend and I had tried it once before, but then I checked her version of NVDA, and it was 2019.1. So I had her update it, and then it worked.


It would really be interesting to know if there-s a similar solution for earlier versions.


Ciao,

Ollie

On 18/03/2020 18:24, Brian Vogel wrote:
On Wed, Mar 18, 2020 at 08:01 AM, Tyler Spivey wrote:

However if that didn't fix it (which I doubt it would), please do
the following, assuming you have an installed copy of NVDA 2019.3
or higher:

Just curious if there's anything similar that would work with pre-2019.3 versions of NVDA to achieve the same end, since you explicitly specify 2019.3 or higher?

--

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

*Power is being told you're not loved and not being destroyed by it.*

       ~ Madonna

Re: Serious issue with NVDA not reading menus and totally silent in Firefox and Chrome

Tyler Spivey
 

On 3/18/2020 10:24 AM, Brian Vogel wrote:
On Wed, Mar 18, 2020 at 08:01 AM, Tyler Spivey wrote:
However if that didn't fix it (which I doubt it would), please do the following, assuming you have an installed copy of NVDA 2019.3 or higher:
Just curious if there's anything similar that would work with pre-2019.3 versions of NVDA to achieve the same end, since you explicitly specify 2019.3 or higher?


Yes, the original line in #9039:

import comtypes,ctypes;p=comtypes.typeinfo.LoadTypeLibEx(r"c:\windows\syswow64\oleacc.dll");ctypes.windll.oleaut32.RegisterTypeLib(p, ur"c:\windows\syswow64\oleacc.dll", None)

I just recreated the issue here and tried your sfc/dism method, with no luck.
Also everyone saying run the COM Registration Fixing Tool can just go away, because it *doesn't actually work*. And NVDA is mostly *useless* if you happen to be one of the ones affected by this.


Re: Serious issue with NVDA not reading menus and totally silent in Firefox and Chrome

Mallard
 

Hello Joseph,


Yes. I left this one as a last resort, trying all other sugggestions first. When they didn-t work, I asked my husband and we got it right.


Ciao,

Ollie

On 18/03/2020 18:33, Joseph Lee wrote:

Hi,
And this time, Tyler’s workaround did work (essentially, registering oleacc.dll once again).

Cheers,

Joseph

*From:* nvda@nvda.groups.io <nvda@nvda.groups.io> *On Behalf Of *Brian Vogel
*Sent:* Wednesday, March 18, 2020 10:20 AM
*To:* nvda@nvda.groups.io
*Subject:* Re: [nvda] Serious issue with NVDA not reading menus and totally silent in Firefox and Chrome

On Wed, Mar 18, 2020 at 01:07 PM, Joseph Lee wrote:

try running COM registration fixing tool, and if that and
restarting the computer doesn’t make a difference

Agreed.  I simply presume that once the same thing is recommended by multiple people it will definitely be tried first, moving on to other things only if it doesn't solve the problem.  I tossed the SFC/DISM idea out as a "just in case the COM registration fixing tool doesn't work" idea.

--

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

*Power is being told you're not loved and not being destroyed by it.*

       ~ Madonna

Re: Serious issue with NVDA not reading menus and totally silent in Firefox and Chrome

Mallard
 

I-m not defensive. I asked a question, it was answered. You didn-t understand. That-s all.



As I said in my previous reply to you, minunderstandings are what makes us human.


Forget about it, please.


We have worse stuff to fight for and against at the moment than a subject line or whatever else.. At least we have here in Italy. Ifyou don-t, then you-re lucky, so thank God or whoever you believe in for it.


Ciao,

Ollie

On 18/03/2020 19:00, Gene wrote:
I’m sorry, but look at your message and please stop being defensive.  Your subject line says menus are not being read.  The only menu you spoke of is the start menu.  Yes, many people answered with suggestions for help, including me.  But the fact that the solution you report as working did work is proof that the problem was not acdcessibility settings in the browsers and that the menus in the browses were, I assume, being read.
I didn’t write what I wrote to be negatively critical.  I wrote it to have you clarify the problem so you could follow the most likely path toward a resolution.  My question as to what the message meant was legitimate.
Gene
----- Original Message -----
*From:* Mallard <mailto:mallard@...>
*Sent:* Wednesday, March 18, 2020 12:20 PM
*To:* nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
*Subject:* Re: [nvda] Serious issue with NVDA not reading menus and totally silent in Firefox and Chrome
I strongly suspect you either didn-t read the whole message, or you
simply didn-t understand it for your own reasons.

In fact, the message was very well understood and acted upon by a good
number of people, and eventually the problem was solved...


Thanks anyway.

Ciao,

Ollie




On 18/03/2020 17:31, Gene wrote:
The message is unclear.  The subject line refers to menus but the
first part of the message talks about the start menu. I strongly
suspect that that is what is being referred to, not that menus are not
read in Firefox and in Chrome.  If, in fact, menus aren’t being read
in Chrome and Firefox, then Ron may be right about the accdcessibility
settings, but I find it very unlikely that both browsers would have
this setting be incorrect in the default installation and the user
would be extremely unlikely to have changed them. Therefore, without
more information, I shall assume that the menus work in both browsers
and that the start menu is the menu referred to in the subject line.
Also, the description is that Firefox and Chrome are unreadable.
Nothing is said about menus.
Gene
----- Original Message -----
*From:* Sarah k Alawami <mailto:marrie12@...>
*Sent:* Wednesday, March 18, 2020 10:36 AM
*To:* nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
*Subject:* Re: [nvda] Serious issue with NVDA not reading menus and
totally silent in Firefox and Chrome

Try a complete reinstall of NVDA. This might help. All nvda related
folders will need to be removed. Also if she has any add ons try
uninstalling those then on the full reinstall of nvda reinstall the
add ons one at a time to see if they still have the issue.

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

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 18 Mar 2020, at 3:53, Mallard wrote:

     Hello all,

     A friend of mine recently bought a HP laptop.

     She experiences some really weird behaviours with NVDA.

     When the Start key is pressed, no menu is read.

     But that can be bypassed by using the Start button on the bar.

     The main issue is that both Firefox and Chrome aer unreadable, and
     I-ve never seen anything like that in my life.

     I tried to help her via Teamviewer, as she lives in a different
     town, and I was shocked.

     How is it possible that NVDA doesn-t read browsers like that_

     I-m not a techie at all, so have no idea of what to do and how to
     help her.

     she-s a teacher and, with the Covid/19 lockdown active here in
     Italy, she needs to teach online. Not easy under these conditions.

     any help will be greatly appreciated.

     Ciao,

     Ollie


Re: Serious issue with NVDA not reading menus and totally silent in Firefox and Chrome

Mallard
 

Gene,


Tat-s ok... No problem... The issue was solved, and this is what matters...


Misunderstandings are what make us human, aren-t they_ Otherwise we would be robots, and we wouldn-t be allowed to solve CAPTCHAS ROFL!!!!!


Take care, stay safe, and try to protect yourself from COVID. It-s nasty...


Hug your country virtually from me.


Ciao,

Ollie

On 18/03/2020 19:11, Gene wrote:
I’m sorry, but if you interpret the message differently from me, that is a legitimate disagreement and I saw a problem with the message that needed to be clarified, in my opinion.  I am not going to argue this with you further.
Gene
----- Original Message -----
*From:* Brian Vogel <mailto:@britechguy>
*Sent:* Wednesday, March 18, 2020 1:02 PM
*To:* nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
*Subject:* Re: [nvda] Serious issue with NVDA not reading menus and totally silent in Firefox and Chrome
On Wed, Mar 18, 2020 at 01:51 PM, Gene wrote:

I didn’t say the statements are inaccurate.
Gene, whether "inaccurate" or "unclear," you never seem to be willing to admit that the leaps you're willing to jump to are what are problematic, and they are.  You wrote, and I quote, "Therefore, without more information, I shall assume that the menus work in both browsers and that the start menu is the menu referred to in the subject line." That goes directly against the information originally offered, period.

But with this, I'm done.  You've done this before and you'll do it again, certain that you're just fine in ignoring what has been explicitly stated.  There were no lines to read between here in the way you did.

--

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

*Power is being told you're not loved and not being destroyed by it.*

       ~ Madonna

Re: Serious issue with NVDA not reading menus and totally silent in Firefox and Chrome

Mallard
 

Lol, you-re so right about hp and bloatware and all!


We solved it, and while we were at it, my husband cleaned up her computer via Teamviewer, and now NVDA flies on it, and reads everyting eprfectly.


In addition, I-d like to thank Brian once more for the tutorial on using ribbons in Windows 10. I explained my friend how to handle them based on that tutorial, and now she-s happy about those as well.


Ciao, nd again ghanks to all that responded offering solutions.


Ciao,

Ollie

On 18/03/2020 20:29, Jackie wrote:
Yeah--the other thing is that HP does some weird stuff w/its keyboard
sometimes, especially the function keys. The other thing is that it
tends to have bloatware upon bloatware running, all of which may or
may not be contributory. But that is 1 instance where a computer
really needs some work to get it aligned w/the needs of screen reader
users.

The other thing, Alli, is that you might want to see if Narrator works
similarly.

On 3/18/20, Hareth <hareth4m@...> wrote:
English is my 2nd language. I got what she meant perfectly clear.
Better for me in the future to avoid this kind of unnecessary
arguments, to read the whole message instead of taking the whole
meaning based on the message subject line or title.
Some times its impossible to put the entire inquiry in a single line.
Plus its not a common practice to put multiple issues squeezed in the
title.
Good enough to place a single hint there,
and go farther in the message body to clarify more on issue.

On 3/18/20, Gene <gsasner@...> wrote:
I’m sorry, but if you interpret the message differently from me, that is
a
legitimate disagreement and I saw a problem with the message that needed
to
be clarified, in my opinion. I am not going to argue this with you
further.

Gene
----- Original Message -----
From: Brian Vogel
Sent: Wednesday, March 18, 2020 1:02 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Serious issue with NVDA not reading menus and totally
silent in Firefox and Chrome

On Wed, Mar 18, 2020 at 01:51 PM, Gene wrote:

I didn’t say the statements are inaccurate.
Gene, whether "inaccurate" or "unclear," you never seem to be willing to
admit that the leaps you're willing to jump to are what are problematic,
and
they are. You wrote, and I quote, " Therefore, without more information,
I
shall assume that the menus work in both browsers and that the start menu
is
the menu referred to in the subject line." That goes directly against
the
information originally offered, period.

But with this, I'm done. You've done this before and you'll do it again,
certain that you're just fine in ignoring what has been explicitly
stated.
There were no lines to read between here in the way you did.

--

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

Power is being told you're not loved and not being destroyed by it.

~ Madonna









Re: changing reading speed on the fly in say all profile

 

On Wed, Mar 18, 2020 at 04:25 PM, Sarah k Alawami wrote:
You realise you have sent this 5 or so times, either that or someone is bottom posting.
Nope and nope.  The archive doesn't lie.
 
--

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

Power is being told you're not loved and not being destroyed by it.

       ~ Madonna

 

 

Re: changing reading speed on the fly in say all profile

Sarah k Alawami
 

You realise you have sent this 5 or so times, either that or someone is bottom posting. If that is the case I don't read all the way to the bottom as I don't really have the time to do so.. I hope you can file an issue on github and provide logs.

Take care

Sarah Alawami, owner of TFFP. . For more info go to our website.

to subscribe to the feed click here and you can also follow us on twitter

Our discord 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 and my tffp lbry page 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

On 17 Mar 2020, at 20:59, J.G wrote:

Thank you for your help. I can change settings of say all profile, when it is manually activated, but when I have pressed NVDA+down, and then tried to use synth ring via ctrl+NVDA+arrow keys, NVDA immediately fell back to original profile, so I was only able to change speech rate of this profile. I understand this logic behind, but anyway is it possible to embed some delay before fall back to original profile or other solution so we can save some time or I'm doing something wrong?

best regards,
Jožef

Re: Serious issue with NVDA not reading menus and totally silent in Firefox and Chrome

Jackie
 

Yeah--the other thing is that HP does some weird stuff w/its keyboard
sometimes, especially the function keys. The other thing is that it
tends to have bloatware upon bloatware running, all of which may or
may not be contributory. But that is 1 instance where a computer
really needs some work to get it aligned w/the needs of screen reader
users.

The other thing, Alli, is that you might want to see if Narrator works
similarly.

On 3/18/20, Hareth <hareth4m@...> wrote:
English is my 2nd language. I got what she meant perfectly clear.
Better for me in the future to avoid this kind of unnecessary
arguments, to read the whole message instead of taking the whole
meaning based on the message subject line or title.
Some times its impossible to put the entire inquiry in a single line.
Plus its not a common practice to put multiple issues squeezed in the
title.
Good enough to place a single hint there,
and go farther in the message body to clarify more on issue.

On 3/18/20, Gene <gsasner@...> wrote:
I’m sorry, but if you interpret the message differently from me, that is
a
legitimate disagreement and I saw a problem with the message that needed
to
be clarified, in my opinion. I am not going to argue this with you
further.

Gene
----- Original Message -----
From: Brian Vogel
Sent: Wednesday, March 18, 2020 1:02 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Serious issue with NVDA not reading menus and totally
silent in Firefox and Chrome

On Wed, Mar 18, 2020 at 01:51 PM, Gene wrote:

I didn’t say the statements are inaccurate.
Gene, whether "inaccurate" or "unclear," you never seem to be willing to
admit that the leaps you're willing to jump to are what are problematic,
and
they are. You wrote, and I quote, " Therefore, without more information,
I
shall assume that the menus work in both browsers and that the start menu
is
the menu referred to in the subject line." That goes directly against
the
information originally offered, period.

But with this, I'm done. You've done this before and you'll do it again,
certain that you're just fine in ignoring what has been explicitly
stated.
There were no lines to read between here in the way you did.

--

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

Power is being told you're not loved and not being destroyed by it.

~ Madonna










--
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.brighter-vision.com & www.mysitesbeenhacked.com

Re: changing reading speed on the fly in say all profile

Sarah k Alawami
 

Can you send a bug to github? or look for one?

Take care

Sarah Alawami, owner of TFFP. . For more info go to our website.

to subscribe to the feed click here and you can also follow us on twitter

Our discord 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 and my tffp lbry page 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

On 17 Mar 2020, at 20:59, J.G wrote:

Thank you for your help. I can change settings of say all profile, when it is manually activated, but when I have pressed NVDA+down, and then tried to use synth ring via ctrl+NVDA+arrow keys, NVDA immediately fell back to original profile, so I was only able to change speech rate of this profile. I understand this logic behind, but anyway is it possible to embed some delay before fall back to original profile or other solution so we can save some time or I'm doing something wrong?

best regards,
Jožef

Re: Serious issue with NVDA not reading menus and totally silent in Firefox and Chrome

Hareth
 

English is my 2nd language. I got what she meant perfectly clear.
Better for me in the future to avoid this kind of unnecessary
arguments, to read the whole message instead of taking the whole
meaning based on the message subject line or title.
Some times its impossible to put the entire inquiry in a single line.
Plus its not a common practice to put multiple issues squeezed in the title.
Good enough to place a single hint there,
and go farther in the message body to clarify more on issue.

On 3/18/20, Gene <gsasner@...> wrote:
I’m sorry, but if you interpret the message differently from me, that is a
legitimate disagreement and I saw a problem with the message that needed to
be clarified, in my opinion. I am not going to argue this with you
further.

Gene
----- Original Message -----
From: Brian Vogel
Sent: Wednesday, March 18, 2020 1:02 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Serious issue with NVDA not reading menus and totally
silent in Firefox and Chrome

On Wed, Mar 18, 2020 at 01:51 PM, Gene wrote:

I didn’t say the statements are inaccurate.
Gene, whether "inaccurate" or "unclear," you never seem to be willing to
admit that the leaps you're willing to jump to are what are problematic, and
they are. You wrote, and I quote, " Therefore, without more information, I
shall assume that the menus work in both browsers and that the start menu is
the menu referred to in the subject line." That goes directly against the
information originally offered, period.

But with this, I'm done. You've done this before and you'll do it again,
certain that you're just fine in ignoring what has been explicitly stated.
There were no lines to read between here in the way you did.

--

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

Power is being told you're not loved and not being destroyed by it.

~ Madonna








Re: accessible apps page.

 

The page is below. I plan on forking the wiki, at least, that portion of the wiki, then splitting all the different kinds of software into categories like Windows 10 Metro apps, media players, internet browsers, email clients, etc. I'm hoping everybody can contribute to it.

https://github.com/nvaccess/nvda-community/wiki/Application-Support

Re: Serious issue with NVDA not reading menus and totally silent in Firefox and Chrome

Gene
 

I’m sorry, but if you interpret the message differently from me, that is a legitimate disagreement and I saw a problem with the message that needed to be clarified, in my opinion.  I am not going to argue this with you further. 
 
Gene

----- Original Message -----
Sent: Wednesday, March 18, 2020 1:02 PM
Subject: Re: [nvda] Serious issue with NVDA not reading menus and totally silent in Firefox and Chrome
 
On Wed, Mar 18, 2020 at 01:51 PM, Gene wrote:
I didn’t say the statements are inaccurate.
Gene, whether "inaccurate" or "unclear," you never seem to be willing to admit that the leaps you're willing to jump to are what are problematic, and they are.  You wrote, and I quote, " Therefore, without more information, I shall assume that the menus work in both browsers and that the start menu is the menu referred to in the subject line."  That goes directly against the information originally offered, period.

But with this, I'm done.  You've done this before and you'll do it again, certain that you're just fine in ignoring what has been explicitly stated.  There were no lines to read between here in the way you did.
 
--

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

Power is being told you're not loved and not being destroyed by it.

       ~ Madonna

 

 

Re: Serious issue with NVDA not reading menus and totally silent in Firefox and Chrome

Gene
 

Saying unknown wouldn’t have happened if the problem was accessibility settings.  If the problem was accessibility settings, you wouldn’t have heard anything when you tried to read a page. 
 
I simply wrote what I did in my earlier messages to clarify the problem and to help you do the most likely things first that might resolve the problem.
 
Gene

----- Original Message -----
From: Mallard
Sent: Wednesday, March 18, 2020 12:21 PM
Subject: Re: [nvda] Serious issue with NVDA not reading menus and totally silent in Firefox and Chrome
 
Addendum> No. No browser read a single thing when you opened it. All you
got was "Unknown", Unknown, unknown, whatever you did...


Anyway, it-s all in the past now. Issue solved.

Ciao, stay safe,

Ollie




On 18/03/2020 17:31, Gene wrote:
> The message is unclear.  The subject line refers to menus but the
> first part of the message talks about the start menu.  I strongly
> suspect that that is what is being referred to, not that menus are not
> read in Firefox and in Chrome.  If, in fact, menus aren’t being read
> in Chrome and Firefox, then Ron may be right about the accdcessibility
> settings, but I find it very unlikely that both browsers would have
> this setting be incorrect in the default installation and the user
> would be extremely unlikely to have changed them.  Therefore, without
> more information, I shall assume that the menus work in both browsers
> and that the start menu is the menu referred to in the subject line.
> Also, the description is that Firefox and Chrome are unreadable. 
> Nothing is said about menus.
> Gene
> ----- Original Message -----
> *From:* Sarah k Alawami <mailto:marrie12@...>
> *Sent:* Wednesday, March 18, 2020 10:36 AM
> *To:* nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
> *Subject:* Re: [nvda] Serious issue with NVDA not reading menus and
> totally silent in Firefox and Chrome
>
> Try a complete reinstall of NVDA. This might help. All nvda related
> folders will need to be removed. Also if she has any add ons try
> uninstalling those then on the full reinstall of nvda reinstall the
> add ons one at a time to see if they still have the issue.
>
> Sarah Alawami, owner of TFFP. . For more info go to our website.
> <http://www.tffppodcast.com>
>
> 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 18 Mar 2020, at 3:53, Mallard wrote:
>
>     Hello all,
>
>     A friend of mine recently bought a HP laptop.
>
>     She experiences some really weird behaviours with NVDA.
>
>     When the Start key is pressed, no menu is read.
>
>     But that can be bypassed by using the Start button on the bar.
>
>     The main issue is that both Firefox and Chrome aer unreadable, and
>     I-ve never seen anything like that in my life.
>
>     I tried to help her via Teamviewer, as she lives in a different
>     town, and I was shocked.
>
>     How is it possible that NVDA doesn-t read browsers like that_
>
>     I-m not a techie at all, so have no idea of what to do and how to
>     help her.
>
>     she-s a teacher and, with the Covid/19 lockdown active here in
>     Italy, she needs to teach online. Not easy under these conditions.
>
>     any help will be greatly appreciated.
>
>     Ciao,
>
>     Ollie
>
>


Re: Serious issue with NVDA not reading menus and totally silent in Firefox and Chrome

 

On Wed, Mar 18, 2020 at 01:51 PM, Gene wrote:
I didn’t say the statements are inaccurate. 
Gene, whether "inaccurate" or "unclear," you never seem to be willing to admit that the leaps you're willing to jump to are what are problematic, and they are.  You wrote, and I quote, " Therefore, without more information, I shall assume that the menus work in both browsers and that the start menu is the menu referred to in the subject line."  That goes directly against the information originally offered, period.

But with this, I'm done.  You've done this before and you'll do it again, certain that you're just fine in ignoring what has been explicitly stated.  There were no lines to read between here in the way you did.
 
--

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

Power is being told you're not loved and not being destroyed by it.

       ~ Madonna

 

 

Re: Serious issue with NVDA not reading menus and totally silent in Firefox and Chrome

Gene
 

I’m sorry, but look at your message and please stop being defensive.  Your subject line says menus are not being read.  The only menu you spoke of is the start menu.  Yes, many people answered with suggestions for help, including me.  But the fact that the solution you report as working did work is proof that the problem was not acdcessibility settings in the browsers and that the menus in the browses were, I assume, being read. 
 
I didn’t write what I wrote to be negatively critical.  I wrote it to have you clarify the problem so you could follow the most likely path toward a resolution.  My question as to what the message meant was legitimate. 
 
Gene

----- Original Message -----
From: Mallard
Sent: Wednesday, March 18, 2020 12:20 PM
Subject: Re: [nvda] Serious issue with NVDA not reading menus and totally silent in Firefox and Chrome
 
I strongly suspect you either didn-t read the whole message, or you
simply didn-t understand it for your own reasons.

In fact, the message was very well understood and acted upon by a good
number of people, and eventually the problem was solved...


Thanks anyway.

Ciao,

Ollie




On 18/03/2020 17:31, Gene wrote:
> The message is unclear.  The subject line refers to menus but the
> first part of the message talks about the start menu.  I strongly
> suspect that that is what is being referred to, not that menus are not
> read in Firefox and in Chrome.  If, in fact, menus aren’t being read
> in Chrome and Firefox, then Ron may be right about the accdcessibility
> settings, but I find it very unlikely that both browsers would have
> this setting be incorrect in the default installation and the user
> would be extremely unlikely to have changed them.  Therefore, without
> more information, I shall assume that the menus work in both browsers
> and that the start menu is the menu referred to in the subject line.
> Also, the description is that Firefox and Chrome are unreadable. 
> Nothing is said about menus.
> Gene
> ----- Original Message -----
> *From:* Sarah k Alawami <mailto:marrie12@...>
> *Sent:* Wednesday, March 18, 2020 10:36 AM
> *To:* nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
> *Subject:* Re: [nvda] Serious issue with NVDA not reading menus and
> totally silent in Firefox and Chrome
>
> Try a complete reinstall of NVDA. This might help. All nvda related
> folders will need to be removed. Also if she has any add ons try
> uninstalling those then on the full reinstall of nvda reinstall the
> add ons one at a time to see if they still have the issue.
>
> Sarah Alawami, owner of TFFP. . For more info go to our website.
> <http://www.tffppodcast.com>
>
> 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 18 Mar 2020, at 3:53, Mallard wrote:
>
>     Hello all,
>
>     A friend of mine recently bought a HP laptop.
>
>     She experiences some really weird behaviours with NVDA.
>
>     When the Start key is pressed, no menu is read.
>
>     But that can be bypassed by using the Start button on the bar.
>
>     The main issue is that both Firefox and Chrome aer unreadable, and
>     I-ve never seen anything like that in my life.
>
>     I tried to help her via Teamviewer, as she lives in a different
>     town, and I was shocked.
>
>     How is it possible that NVDA doesn-t read browsers like that_
>
>     I-m not a techie at all, so have no idea of what to do and how to
>     help her.
>
>     she-s a teacher and, with the Covid/19 lockdown active here in
>     Italy, she needs to teach online. Not easy under these conditions.
>
>     any help will be greatly appreciated.
>
>     Ciao,
>
>     Ollie
>
>


Re: Serious issue with NVDA not reading menus and totally silent in Firefox and Chrome

Gene
 

I didn’t say the statements are inaccurate.  The meswsage is being interpreted by some people to mean that the Firefox and Chrome menus aren’t being read and from there, they are saying that it is a problem with accessibility settings in the browser.  The message says nothing about menus in Firefox and Chrome.  It says, they are unreadable, which very likely doesn’t refer to the menus at all, but rather to web pages not being able to be read.  the first thing to try is the coms (spelling) registration tool.  And it would be helpful to know whether the menus are being read.  The subject line speaks of menus not reading.  That is what I think is inaccurate.  the only menu spoken of is the start menu and it is unlikely that the browser menus are being referred to, even though the subject line, evidently mistakenly, refers to menus.
 
Gene

----- Original Message -----
Sent: Wednesday, March 18, 2020 11:59 AM
Subject: Re: [nvda] Serious issue with NVDA not reading menus and totally silent in Firefox and Chrome
 
On Wed, Mar 18, 2020 at 12:31 PM, Gene wrote:
The message is unclear.
Perhaps a bit, but when I see, "When the Start key is pressed, no menu is read. But that can be bypassed by using the Start button on the bar," followed by, "The main issue is that both Firefox and Chrome are unreadable," I have no reason to believe that both statements are not accurate.  I have no idea why you'd believe otherwise.

Something's definitely off, but I suspect it is, like most issues, idiosyncratic to that machine.   This behavior is so uncharacteristic I'd be starting with:  Using SFC (System File Checker) and DISM (Deployment Imaging Servicing and Management) to Repair Windows 8 & 10


 
--

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

Power is being told you're not loved and not being destroyed by it.

       ~ Madonna

 

 

accessible apps page.

Sue J. Ward
 

Hello am glad that bookworm is up, am wondering what is the link to the accessible apps page am not a git hub user sounds interesting just like to look around on the web for stuff anything to make our life easier.

Re: Serious issue with NVDA not reading menus and totally silent in Firefox and Chrome

 

Hi,
And this time, Tyler’s workaround did work (essentially, registering oleacc.dll once again).

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Brian Vogel
Sent: Wednesday, March 18, 2020 10:20 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Serious issue with NVDA not reading menus and totally silent in Firefox and Chrome

 

On Wed, Mar 18, 2020 at 01:07 PM, Joseph Lee wrote:

try running COM registration fixing tool, and if that and restarting the computer doesn’t make a difference

Agreed.  I simply presume that once the same thing is recommended by multiple people it will definitely be tried first, moving on to other things only if it doesn't solve the problem.  I tossed the SFC/DISM idea out as a "just in case the COM registration fixing tool doesn't work" idea.
 
--

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

Power is being told you're not loved and not being destroyed by it.

       ~ Madonna