[Webkit-unassigned] [Bug 137867] New: AX: [ATK] Do not return ATK_ROLE_UNKNOWN for null or otherwise invalid accessible objects

[bugzilla-daemon at webkit.org]

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

            Bug ID: 137867
           Summary: AX: [ATK] Do not return ATK_ROLE_UNKNOWN for null or
                    otherwise invalid accessible objects
    Classification: Unclassified
           Product: WebKit
           Version: 528+ (Nightly build)
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: Accessibility
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: jdiggs at igalia.com
                CC: webkit-bug-importer at group.apple.com

Currently in webkitAccessibleGetRole() we have:

    g_return_val_if_fail(WEBKIT_IS_ACCESSIBLE(object), ATK_ROLE_UNKNOWN);
    returnValIfWebKitAccessibleIsInvalid(WEBKIT_ACCESSIBLE(object), ATK_ROLE_UNKNOWN);

and:

    if (!coreObject)
        return ATK_ROLE_UNKNOWN;

ATK_ROLE_UNKNOWN suggests that there is a valid accessible object but the platform role mapping for that object is unknown. It is an indication of a WebKit bug (there should be a valid mapping). But it is also an indication to assistive technologies that there might be some obtainable useful information associated with this mystery object. As such assitive technologies might choose to poke at the object further. In contrast, if the object is null or otherwise invalid, there is arguably no obtainable useful information and thus ATs should not bother trying. We can distinguish these two conditions by exposing the latter as ATK_ROLE_INVALID.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20141019/f637ed88/attachment-0002.html>