Comment 1 by jteh on 2013-06-03 00:24
Please provide the following info:

1. Move to an item in the list, press NVDA+f1 and provide the output.
2. Move to the first item in the list, use object navigation to find the first item, press NVDA+f1 and provide the output.

Comment 2 by oaron (in reply to comment 1) on 2013-06-03 06:53
Replying to jteh:

Please provide the following info:

1. Move to an item in the list, press NVDA+f1 and provide the output.

When I navigate to the second item with review cursor, NVDA shows only the first item in the log.

1. Move to the first item in the list, use object navigation to find the first item, press NVDA+f1 and provide the output.

Developer info for navigator object:
name: None
role: ROLE_UNKNOWN
states: STATE_FOCUSABLE, STATE_FOCUSED
isFocusable: True
hasFocus: True
Python object: <NVDAObjects.IAccessible.ContentGenericClient object at 0x0574E990>
Python class mro: (<class 'NVDAObjects.IAccessible.ContentGenericClient'>, <class 'NVDAObjects.IAccessible.IAccessible'>, <class 'NVDAObjects.window.Window'>, <class 'NVDAObjects.NVDAObject'>, <class 'baseObject.ScriptableObject'>, <class 'baseObject.AutoPropertyObject'>, <type 'object'>)
description: None
location: (11, 505, 339, 203)
value: u'1 Litewolf - Express 0:372 Litewolf - In The News Today 0:153 Litewolf - SAM Can! 0:30'
appModule: <'appModuleHandler' (appName u'sambc', process ID 7656) at address 574e890>
TextInfo: <class 'displayModel.DisplayModelTextInfo'>
windowHandle: 19990800
windowClassName: u'TVirtualSongTree'
windowControlID: 19990800
windowStyle: 1442906112
windowThreadID: 5484
windowText: u''
displayText: u'1 Litewolf - Express 0:372 Litewolf - In The News Today 0:153 Litewolf - SAM Can! 0:30'
IAccessibleObject: <POINTER(IAccessible) ptr=0x3b3da8 at 56ca080>
IAccessibleChildID: 0
IAccessible event parameters: windowHandle=19990800, objectID=-4, childID=0
IAccessible accName: None
IAccessible accRole: ROLE_SYSTEM_CLIENT
IAccessible accState: STATE_SYSTEM_FOCUSED, STATE_SYSTEM_FOCUSABLE, STATE_SYSTEM_VALID (1048580)
IAccessible accDescription: None
IAccessible accValue: None

Comment 3 by jteh (in reply to comment 2) on 2013-06-04 00:21
Replying to oaron:

When I navigate to the second item with review cursor, NVDA shows only the first item in the log.

Are you saying the list shows up as one object with object navigation with each item being on a separate line of text in that object?

This list is fairly inaccessible. There should be separate objects for each list item. Without this, individual list items can't get focus. The only way to work around this would be to watch for changes in screen text and look for specific text formatting to detect the current item; e.g. perhaps the current item is highlighted or bold.

Comment 4 by oaron (in reply to comment 3) on 2013-07-25 12:46
Replying to jteh:

Replying to oaron:

When I navigate to the second item with review cursor, NVDA shows only the first item in the log.

Are you saying the list shows up as one object with object navigation with each item being on a separate line of text in that object?

This list is fairly inaccessible. There should be separate objects for each list item. Without this, individual list items can't get focus. The only way to work around this would be to watch for changes in screen text and look for specific text formatting to detect the current item; e.g. perhaps the current item is highlighted or bold.

The selected item is light blue, and the others is white. How can I get color of a selected item?

Comment 5 by jteh on 2013-07-26 05:04
You can verify by finding the text in screen review and pressing NVDA+f. If this works, you can do it programmatically by getting a TextInfo for the window, calling getTextWithFields() and walking through the fields, looking for formatChange fields which have an appropriate color/background-color attribute. See the PoeditListItem._get_isBold method in the poedit app module for an example of scanning for formatting (though it checks for bold, not colour).

Comment 6 by oaron (in reply to comment 5) on 2013-08-05 10:07
Replying to jteh:

You can verify by finding the text in screen review and pressing NVDA+f. If this works, you can do it programmatically by getting a TextInfo for the window, calling getTextWithFields() and walking through the fields, looking for formatChange fields which have an appropriate color/background-color attribute. See the PoeditListItem._get_isBold method in the poedit app module for an example of scanning for formatting (though it checks for bold, not colour).

NVDA doesn't recognize the different colours. Does it mean this list view is not accessible, so we can't create an appmodule for fix it?

I am under the impression that @josephsl was experimenting with SAM Broadcaster and even designed a 'skeleton' app module for the same. If this impression was an illusion, please excuse me, but if not, could you please test for the reported issue and kindly share your findings? While the version number system for SAM was probably different four years ago (when this ticket was originally filed), the latest stable release is 2017.6 released this July, implying that it is very much possible that an NVDA update and more likely a SAM Broadcaster update may have resolved this bug.

@josephsl, are you happy with this issue to be closed?

Closing