Fixing mapping conflicts for required html attribute and aria-required

Source/core/accessibility/AXNodeObject.cpp

Index: Source/core/accessibility/AXNodeObject.cpp
diff --git a/Source/core/accessibility/AXNodeObject.cpp b/Source/core/accessibility/AXNodeObject.cpp
index f90ad0135b5ef1208f51cc0f546e02e4fbe81d61..a4dc7b8565dc39abcd7aa2b1360c649762d2b68e 100644
--- a/Source/core/accessibility/AXNodeObject.cpp
+++ b/Source/core/accessibility/AXNodeObject.cpp
@@ -746,13 +746,13 @@ bool AXNodeObject::isReadOnly() const
 
 bool AXNodeObject::isRequired() const
 {
-    if (equalIgnoringCase(getAttribute(aria_requiredAttr), "true"))
-        return true;
-
     Node* n = this->node();
     if (n && (n->isElementNode() && toElement(n)->isFormControlElement()))
         return toHTMLFormControlElement(n)->isRequired();
 
+    if (equalIgnoringCase(getAttribute(aria_requiredAttr), "true"))

[shreeramk, 2014/12/05 07:32:54]

Spec says http://w3c.github.io/aria/aria/aria.html#aria-required

"Unless an exactly equivalent native attribute is available, host languages
should allow authors to use the aria-required attribute on host language form
elements that require input or selection by the user."

As we know html "required" attribute exists, then I think, in that scenario we
should give first priority to required attribute and then to aria-required
attribute for form elements.

Also for form elements we should first check for html required attribute then
check for aria-required attribute.

+        return true;
+
     return false;
 }