Show human-readable names for accessibility properties

Source/devtools/front_end/accessibility/AccessibilityStrings.js

Index: Source/devtools/front_end/accessibility/AccessibilityStrings.js
diff --git a/Source/devtools/front_end/accessibility/AccessibilityStrings.js b/Source/devtools/front_end/accessibility/AccessibilityStrings.js
new file mode 100644
index 0000000000000000000000000000000000000000..7567cbbbf3c6061e14c91ed17f7ce3665fb4ab54
--- /dev/null
+++ b/Source/devtools/front_end/accessibility/AccessibilityStrings.js
@@ -0,0 +1,171 @@
+// Copyright (c) 2015 The Chromium Authors. All rights reserved.
+// Use of this source code is governed by a BSD-style license that can be
+// found in the LICENSE file.
+
+WebInspector.AXAttributes = {
+    "disabled" : {
+        name : "Disabled",
+        description : "If true, this element currently cannot be interacted with.",
+        group : "AXGlobalStates"
+    },
+    "hidden" : {
+        name : "Hidden",

[dmazzoni, 2015/05/26 23:15:03]

We don't actually show a full AX node in this case, right? If it's hidden, there
is no AX node and we should just try to explain why.

[aboxhall, 2015/05/26 23:31:56]

Good point - this shouldn't actually ever get shown. Should I take it out?

+        description : "Whether this element is hidden from assistive technology.",
+        group : "AXGlobalStates"
+    },
+    "hiddenRoot" : {
+        name : "Hidden region root",

[dmazzoni, 2015/05/26 23:15:03]

I don't like this one but I'm not sure what it should be.

Does this include nodes that have aria-hidden set on them and also nodes that
aren't allowed to have children? It might be confusing if those two concepts are
conflated. If they're not, maybe this could be something like "Root of hidden
subtree", or "Ancestor that disallows children".

[aboxhall, 2015/05/26 23:31:56]

This is actually wrapped up in the hidden node explanation as well. It ends up
as "aria-hidden is true on ancestor: <selector-esque string>".

Should I take this out as well?

+        description : "The ancestor whose properties cause this element to be hidden.",
+        group : "AXGlobalStates"
+    },
+    "invalid" : {
+        name : "Invalid",

[dmazzoni, 2015/05/26 23:15:04]

Invalid user entry?

So it's not taken to mean that the AX data itself is invalid.

[aboxhall, 2015/05/26 23:31:56]

Done.

+        description : "If true, this element's user-entered value does not conform to validation requirement.",
+        group : "AXGlobalStates"
+    },
+    "live" : {
+        name : "Live",
+        description : "Whether and what type of live updates may be expected for this element.",
+        group : "AXLiveRegionAttributes"
+    },
+    "atomic" : {
+        name : "Atomic",

[dmazzoni, 2015/05/26 23:15:04]

Is this grouped under "Live region properties"? If not it should say Atomic
(Live Regions), or something like that.

[aboxhall, 2015/05/26 23:31:56]

It's not currently grouped, no. Good suggestion - can remove if/when we do group
live region properties.

+        description : "If this element may receive live updates, whether the entire live region should be presented to the user on changes.",
+        group : "AXLiveRegionAttributes"
+    },
+    "relevant" : {
+        name : "Relevant",
+        description : "If this element may receive live updates, what type of updates should trigger a notification.",
+        group : "AXLiveRegionAttributes"
+    },
+    "busy" : {
+        name : "Busy",
+        description : "Whether this element or its subtree are currently being updated (and thus may be in an inconsistent state).",
+        group : "AXLiveRegionAttributes"
+    },
+    "root" : {
+        name : "Live region root",
+        description : "If this element may receive live updates, the root element of the containing live region.",
+        group : "AXLiveRegionAttributes"
+    },
+    "autocomplete" : {
+        name : "Has autocomplete",
+        description : "Whether and what type of autocomplete suggestions are currently provided by this element.",
+        group : "AXWidgetAttributes"
+    },
+    "haspopup" : {
+        name : "Has popup",
+        description : "Whether this element has caused some kind of pop-up (such as a menu) to appear.",
+        group : "AXWidgetAttributes"
+    },
+    "level" : {
+        name : "Level",
+        description : "The hierarchical level of this element.",
+        group : "AXWidgetAttributes"
+    },
+    "multiselectable" : {
+        name : "Multi-selectable",
+        description : "Whether a user may select more than one option from this widget.",
+        group : "AXWidgetAttributes"
+    },
+    "orientation" : {
+        name : "Orientation",
+        description : "Whether this linear element's orientation is horizontal or vertical.",
+        group : "AXWidgetAttributes"
+    },
+    "multiline" : {
+        name : "Multi-line",
+        description : "Whether this textbox may have more than one line.",
+        group : "AXWidgetAttributes"
+    },
+    "readonly" : {
+        name : "Read-only",
+        description : "If true, this element may be interacted with, but its value cannot be changed.",
+        group : "AXWidgetAttributes"
+    },
+    "required" : {
+        name : "Required",
+        description : "Whether this element is a required field in a form.",
+        group : "AXWidgetAttributes"
+    },
+    "valuemin" : {
+        name : "Minimum value",
+        description : "For a range widget, the minimum possible value.",
+        group : "AXWidgetAttributes"
+    },
+    "valuemax" : {
+        name : "Maximum value",
+        description : "For a range widget, the maximum possible value.",
+        group : "AXWidgetAttributes"
+    },
+    "valuetext" : {
+        name : "Value description",
+        description : "A human-readable version of the value of a range widget (where necessary).",
+        group : "AXWidgetAttributes"
+    },
+    "checked" : {
+        name : "Checked",
+        description : "Whether this checkbox, radio button or tree item is checked, unchecked, or mixed (e.g. has both checked and un-checked children).",
+        group : "AXWidgetStates"
+    },
+    "expanded" : {
+        name : "Expanded",
+        description : "Whether this element, or another grouping element it controls, is expanded.",
+        group : "AXWidgetStates"
+    },
+    "pressed" : {
+        name : "Pressed",
+        description : "Whether this toggle button is currently in a pressed state.",
+        group : "AXWidgetStates"
+    },
+    "selected" : {
+        name : "Selected",
+        description : "Whether the option represented by this element is currently selected.",
+        group : "AXWidgetStates"
+    },
+    "activedescendant" : {
+        name : "Active descendant",
+        description : "The descendant of this element which is active; i.e. the element to which focus should be delegated.",
+        group : "AXRelationshipAttributes"
+    },
+    "flowto" : {
+        name : "Flows to",
+        description : "Element to which the user may choose to navigate after this one, instead of the next element in the DOM order.",
+        group : "AXRelationshipAttributes"
+    },
+    "controls" : {
+        name : "Controls",
+        description : "Element or elements whose content or presence is/are controlled by this widget.",
+        group : "AXRelationshipAttributes"
+    },
+    "describedby" : {
+        name : "Described by",
+        description : "Element or elements which form the description of this element.",
+        group : "AXRelationshipAttributes"
+    },
+    "labelledby" : {
+        name : "Labeled by",
+        description : "Element or elements which may form the name of this element.",
+        group : "AXRelationshipAttributes"
+    },
+    "owns" : {
+        name : "Owns",

[dmazzoni, 2015/05/26 23:15:04]

Note: with my latest change, we should reconsider how to surface this - maybe
exposing a node's children and parents with explanations as to why (from layout
tree, from DOM tree, etc.)

[aboxhall, 2015/05/26 23:31:56]

Once we're showing the full tree, yes, we should definitely do something like
that.

+        description : "Element or elements which should be considered descendants of this element, despite not being descendants in the DOM.",
+        group : "AXRelationshipAttributes"
+    },
+    "name": {
+        name : "Name",
+        description : "The computed name of this element.",
+        group : "Computed"
+    },
+    "role": {
+        name: "Role",
+        description: "The role of this element.",
+        group: "Computed"
+    },
+    "value": {
+        name: "Value",
+        description: "The value of this element.",
+        group: "Computed"
+    }
+}