Tested the issue on Windows 7 using 51.0.2703.0, latest stable 49.0.2623.112, canary 52.0.2707.0 with below steps:

1.Opened URL: http://oaa-accessibility.org/example/42/
2.Observed the chrome and firefox screen same.

Please find attached screencast.

jnurthen@Could you please provide expected behavior screenshot for further triaging the issue.

Deleted: 601933.mp4 704 KB

601933.mp4 704 KB Download

Please keep in mind that the accessible name of an element is not
something you would see on screen, it is part of the information
assistive technologies like screenreaders require to correctly parse a
given item, in this case a treeview item. Therefore, a screenshot
would not accurately describe the problem unless it would be a
screenshot of some kind of accessibility checker.
Nektarios, might  your fixes for  issue 593646    indirectly help in
this case as well, or is it a different problem altogether?

You need to look at the accessible tree in order to see what is coming through. In Chrome open a new tab and type chrome://accessibility then expand the tree and find the node with the text 'Birds' - note that the parent of the static text node with 'Birds' is the tree item itself.

++++++++++ROLE_SYSTEM_OUTLINEITEM FOCUSABLE display:block tag:div xml-roles:treeitem level:2 class:tree-item tree-focus id:birds ia2_hypertext='Birds' location=(108, 239) size=(218, 19) index_in_parent=2 n_relations=0 group_level=0 similar_items_in_group=0 position_in_group=0 table_rows=472451024 table_columns=32 row_index=3 column_index=7661680 n_characters=5 caret_offset=2 n_selections=0

Note that this doesn't have an accessible name displayed.

In FF you will need to install the DOM Inspector in order to see the accessible tree. There you will find that the treeitem has an accessible name of 'Birds' (and a role of Outline Item)

Thank you for providing more feedback. Adding requester "ssamanoori@chromium.org" for another review and adding "Needs-Review" label for tracking.

For more details visit https://sites.google.com/a/chromium.org/dev/issue-tracking/autotriage - Your friendly Sheriffbot

Fixing tree views is next on my list of TODOs.

Any news on this one? :) Still see broken behavior for this in latest Canary build

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/e4bce828f9d8b7674497603d2ca02649923abbd4

commit e4bce828f9d8b7674497603d2ca02649923abbd4
Author: nektar <nektar@chromium.org>
Date: Wed Jul 20 16:24:57 2016

Elements with an ARIA role of treeitem should be able to get their accessible name from their contents.

ARIA Spec 1.1 says that elements with a role of "treeitem" should get their accessible name either "from author" or "from contents". We didn't support "from contents".
BUG= 601933 
R=dmazzoni@chromium.org, aboxhall@chromium.org
TESTED=browser test

Review-Url: https://codereview.chromium.org/2165463003
Cr-Commit-Position: refs/heads/master@{#406579}

[modify] https://crrev.com/e4bce828f9d8b7674497603d2ca02649923abbd4/content/test/data/accessibility/aria/aria-level-expected-mac.txt
[modify] https://crrev.com/e4bce828f9d8b7674497603d2ca02649923abbd4/content/test/data/accessibility/aria/aria-level-expected-win.txt
[modify] https://crrev.com/e4bce828f9d8b7674497603d2ca02649923abbd4/content/test/data/accessibility/aria/aria-tree-expected-android.txt
[modify] https://crrev.com/e4bce828f9d8b7674497603d2ca02649923abbd4/content/test/data/accessibility/aria/aria-tree-expected-mac.txt
[modify] https://crrev.com/e4bce828f9d8b7674497603d2ca02649923abbd4/content/test/data/accessibility/aria/aria-tree-expected-win.txt
[modify] https://crrev.com/e4bce828f9d8b7674497603d2ca02649923abbd4/content/test/data/accessibility/aria/aria-tree.html
[modify] https://crrev.com/e4bce828f9d8b7674497603d2ca02649923abbd4/third_party/WebKit/LayoutTests/inspector-protocol/accessibility/accessibility-ignoredNodes-expected.txt
[modify] https://crrev.com/e4bce828f9d8b7674497603d2ca02649923abbd4/third_party/WebKit/Source/modules/accessibility/AXObject.cpp