Expose accessible descriptions on Android.

Expose accessible descriptions on Android.

Improve handling of accessible text by exposing the accessible name of
an element in "text" for text fields and "contentDescription" otherwise,
and by exposing the accessible description (secondary) as the name of
the SELECT accessibility action, which is a nice trick to get TalkBack to
announce that text after a short delay.

BUG=592297

[dmazzoni, 2016-03-16 20:47:15]

dmazzoni@chromium.org changed reviewers:
+ dtseng@chromium.org

[David Tseng, 2016-03-17 22:55:15]

https://codereview.chromium.org/1800183004/diff/20001/content/browser/accessi...
File content/browser/accessibility/browser_accessibility_android.cc (left):

https://codereview.chromium.org/1800183004/diff/20001/content/browser/accessi...
content/browser/accessibility/browser_accessibility_android.cc:363: // Perhaps
we could return color names in the future?
Unrelated; this begs to be made into a TODO with a bug?

https://codereview.chromium.org/1800183004/diff/20001/content/browser/accessi...
File content/browser/accessibility/browser_accessibility_android.cc (right):

https://codereview.chromium.org/1800183004/diff/20001/content/browser/accessi...
content/browser/accessibility/browser_accessibility_android.cc:350: if
(!value.empty() && ShouldExposeValueAsName())
So, in the Android world, text is same as name?

What happens with text fields with a value and a name? Do we only show the value
in that case?

https://codereview.chromium.org/1800183004/diff/20001/content/browser/accessi...
content/browser/accessibility/browser_accessibility_android.cc:404: //
accessible name as the only accessible text.
Can you reword this last part? Accessible text or description?

https://codereview.chromium.org/1800183004/diff/20001/content/browser/accessi...
content/browser/accessibility/browser_accessibility_android.cc:406: if
(!value.empty() && ShouldExposeValueAsName())
Can you move this non-empty value check into ShouldExposeValueAsName method?

https://codereview.chromium.org/1800183004/diff/20001/content/public/android/...
File
content/public/android/java/src/org/chromium/content/browser/accessibility/LollipopBrowserAccessibilityManager.java
(right):

https://codereview.chromium.org/1800183004/diff/20001/content/public/android/...
content/public/android/java/src/org/chromium/content/browser/accessibility/LollipopBrowserAccessibilityManager.java:46:
AccessibilityNodeInfo.ACTION_SELECT,
This action (according to the docs) is meant for selecting this node. If
TalkBack ever gets selection working, wouldn't we have no way to convey that
info? Just curious if that might be a concern.