Input type "number" is not exposed in Acc layer

content/test/data/accessibility/input-number-expected-mac.txt

Index: content/test/data/accessibility/input-number-expected-mac.txt
diff --git a/content/test/data/accessibility/input-number-expected-mac.txt b/content/test/data/accessibility/input-number-expected-mac.txt
new file mode 100644
index 0000000000000000000000000000000000000000..c09029f2e192de8e0b1c59adfe1537fbd887506c
--- /dev/null
+++ b/content/test/data/accessibility/input-number-expected-mac.txt
@@ -0,0 +1,6 @@
+AXWebArea AXRoleDescription='HTML content'
+    AXGroup AXRoleDescription='group'
+        AXIncrementor AXRoleDescription='stepper' AXValue='0'
+            AXIncrementor AXRoleDescription='stepper' AXValue='0'

[dmazzoni, 2014/11/27 07:33:41]

This is really confusing to have an AXIncrementor inside of an AXIncrementor,
and similarly on other platforms.

[shreeramk, 2014/11/27 07:57:07]

Correct. But may be this is how input type number has been implemented in blink.
I think accessibility can't control that.

+                AXButton AXRoleDescription='button'

[dmazzoni, 2014/11/27 07:33:41]

These buttons probably need labels, like "increment" and "decrement"

+                AXButton AXRoleDescription='button'