Begin using ChromeVox Next to read tab and window titles.

ui/views/accessibility/ax_window_obj_wrapper.cc

Index: ui/views/accessibility/ax_window_obj_wrapper.cc
diff --git a/ui/views/accessibility/ax_window_obj_wrapper.cc b/ui/views/accessibility/ax_window_obj_wrapper.cc
index ebdb650d1a6b484f523067246ef311ad81963963..d2b1cbf0692668e640b3e19ae625401a3069fbde 100644
--- a/ui/views/accessibility/ax_window_obj_wrapper.cc
+++ b/ui/views/accessibility/ax_window_obj_wrapper.cc
@@ -57,8 +57,7 @@ void AXWindowObjWrapper::Serialize(ui::AXNodeData* out_node_data) {
   // Root windows currently have a non readable name (e.g. Display1234...);
   // ignore them unless the window is the only node in the tree.
   if (window_->parent() || window_->children().size() == 0) {
-    out_node_data->AddStringAttribute(ui::AX_ATTR_NAME,
-                                      base::UTF16ToUTF8(window_->title()));
+    out_node_data->AddStringAttribute(ui::AX_ATTR_NAME, window_->name());
   }
 }
 
@@ -66,6 +65,10 @@ int32_t AXWindowObjWrapper::GetID() {
   return AXAuraObjCache::GetInstance()->GetID(window_);
 }
 
+void AXWindowObjWrapper::OnWindowTitleChanged(aura::Window* window) {
+  AXAuraObjCache::GetInstance()->Remove(window);

[dmazzoni, 2016/05/25 15:18:00]

Does it get re-added? Why delete it rather than triggering an event on it?

[David Tseng, 2016/05/25 16:08:23]

Removed this; went with adding the name on the widget (similarly to RootView).

The issue with firing an event is we don't have the plumbing to dispatch an
event on Widget or Window. I think for other platforms, we never needed it.
However, for automation, we need these backing objects to maintain the tree
state in the browser for AXTree.

+}
+
 void AXWindowObjWrapper::OnWindowDestroyed(aura::Window* window) {
   AXAuraObjCache::GetInstance()->Remove(window);
 }