[Webkit-unassigned] [Bug 149297] AX: Implement ARIA 1.1 @aria-current on iOS

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=149297

--- Comment #6 from Nan Wang <n_wang at apple.com> ---
Issue:
When testing with the example(https://bug-146012-attachments.webkit.org/attachment.cgi?id=261418) on iOS, the link is not exposed as accessibility element. 

In the function determineIsAccessibilityElement in WebAccessibilityObjectWrapperIOS, link is not exposed because the function containsUnnaturallySegmentedChildren returns NO.

I'm wondering, in the comment it says "Links can sometimes be elements (when they only contain static text or don't contain anything).", which is the case for the example, shouldn't we expose the link as accessibility element?

While diving deeper, in containsUnnaturallySegmentedChildren function, it returns NO when the element only has one child. However, I'm thinking it should return NO only if the only child is NOT static text or image. Make sense?

Also with the current logic, the accessibility/ios-simulator/link-with-only-image.html test's expectation has a line "FAIL obj.isIgnored should be false. Was true.". We shouldn't include a failure in the expected result, right? 

In conclusion, by removing the "if (childrenSize == 1) return NO;" part in containsUnnaturallySegmentedChildren, the test will have the PASS result and link will be exposed as expected. Just want to make sure my logic is reasonable.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.webkit.org/pipermail/webkit-unassigned/attachments/20150918/2b3cd26e/attachment.html>