Comment 1 by jteh on 2012-11-18 21:52
What version of NVDA did you test this with? Did it work with NVDA 2012.2.1?

Comment 2 by PZajda on 2012-11-19 13:23
For me it has never worked, since 2011.1 which is the first version of NVDA I really used.
And with the most recent snapshot it doesn't work too.

Comment 3 by briang1 on 2012-11-20 08:39
It is true this has never worked. There are other parts of sysinternals that also suffer the same way. I'm sure this was discussed some years ago and it was determined the text list was not accessible. It is indeed interesting that much of autoruns is accessible though the tabs at the top of the screen need to be used with flat review and mouse keys to get them to be usable. I think this suite bears all the hallmarks of being written by different techniques at different times and tweaked and modified with no attempt toward preserving access, as they all behave strangely to a greater or lesser extent on many screenreaders.

Comment 4 by briang1 (in reply to comment 3) on 2012-11-20 08:45
Replying to briang1:

It is true this has never worked. There are other parts of sysinternals that also suffer the same way. I'm sure this was discussed some years ago and it was determined the text list was not accessible. It is indeed interesting that much of autoruns is accessible though the tabs at the top of the screen need to be used with flat review and mouse keys to get them to be usable. I think this suite bears all the hallmarks of being written by different techniques at different times and tweaked and modified with no attempt toward preserving access, as they all behave strangely to a greater or lesser extent on many screenreaders.

Developer info for navigator object:
name: u''
role: ROLE_LIST
states: STATE_INVISIBLE, STATE_FOCUSABLE, STATE_FOCUSED
isFocusable: True
hasFocus: True
Python object: <NVDAObjects.IAccessible.sysListView32.List object at 0x03CCE8B0>
Python class mro: (<class 'NVDAObjects.IAccessible.sysListView32.List'>, <class 'NVDAObjects.IAccessible.List'>, <class 'NVDAObjects.IAccessible.IAccessible'>, <class 'NVDAObjects.window.Window'>, <class 'NVDAObjects.NVDAObject'>, <class 'baseObject.ScriptableObject'>, <class 'baseObject.AutoPropertyObject'>, <type 'object'>)
description: None
location: (105, 533, 590, 0)
value: None
appModule: <'appModuleHandler' (appName u'procexp', process ID 2680) at address 3d40a50>
TextInfo: <class 'NVDAObjects.NVDAObjectTextInfo'>
windowHandle: 197912
windowClassName: u'SysListView32'
windowControlID: 102
windowStyle: 1082197573
windowThreadID: 2300
windowText: u''
displayText: ''
IAccessibleObject: <POINTER(IAccessible) ptr=0x1aa318 at 1e40f80>
IAccessibleChildID: 0
IAccessible event parameters: windowHandle=197912, objectID=-4, childID=0
IAccessible accName: None
IAccessible accRole: ROLE_SYSTEM_LIST
IAccessible accState: STATE_SYSTEM_INVISIBLE, STATE_SYSTEM_FOCUSED, STATE_SYSTEM_FOCUSABLE, STATE_SYSTEM_VALID (1081348)
IAccessible accDescription: None
IAccessible accValue: None

@Brian1Gaff Could you please test if this still occurs with the latest version of Process Explorer? As a side note, this might require the app specific label also. @ehollig

cc @PZajda: could you verify whether this is still the case?

@LeonarddeR I confirm this is still the case, i've just tested on Windows 7 and 10 with ProcessExplorer 16.22, published on December 11, 2018.

Still the case in processExplorer 17.05 on Windows 11.