Add DumpAccessibilityTree tests (11 of 20)

content/test/data/accessibility/aria-pressed.html

Index: content/test/data/accessibility/aria-pressed.html
diff --git a/content/test/data/accessibility/aria-pressed.html b/content/test/data/accessibility/aria-pressed.html
index a6a45f475e9abbbebc1b1016102db3319072b768..980fed3413755a4cacceb62127ff060bfa0919d0 100644
--- a/content/test/data/accessibility/aria-pressed.html
+++ b/content/test/data/accessibility/aria-pressed.html
@@ -12,5 +12,6 @@
 <div tabindex=1 role="button" aria-pressed="false">Toggle button unpressed</div>
 <div tabindex=2 role="button" aria-pressed="true">Toggle button pressed</div>
 <div tabindex=3 role="button" aria-pressed="mixed">Toggle button mixed</div>
+<div tabindex=4 role="button" aria-pressed="undefined">Toggle button undefined</div>

[dmazzoni, 2014/11/05 07:10:49]

When the spec says that aria-pressed is undefined, I don't think they mean
aria-pressed="undefined", they mean that the aria-pressed attribute is not
present - that case is handled by the first one, a regular button.

Right now our logic is that if the aria-pressed attribute is present, it's a
toggle button, even if it's not true, false, or mixed - that's probably wrong.

[shreeramk, 2014/11/05 07:25:17]

But Why values other than true, false or mixed will be assigned to aria-pressed?

Are you talking about a content of this type??

<div role="button" aria-pressed="ooo">Toggle button unknown</div>

Following was the AX output:
IA2_ROLE_TOGGLE_BUTTON name='Toggle button unknown' FOCUSABLE xml-roles:button
checkable:true

 </body>
 </html>