RESOLVED FIXED Bug 172588
[ATK] Add support for aria-details and aria-errormessage
https://bugs.webkit.org/show_bug.cgi?id=172588
Summary [ATK] Add support for aria-details and aria-errormessage
Joanmarie Diggs
Reported 2017-05-25 07:13:04 PDT
The aria-details attribute was added in ARIA 1.1. According to the Core AAM [1]: "If the referenced object is in the accessibility tree, expose a pointer to the accessible object using RELATION_DETAILS, and expose reverse relations as described in Relations." The reverse relation type for RELATION_DETAILS is RELATION_DETAILS_FOR. [1] https://rawgit.com/w3c/aria/master/core-aam/core-aam.html#ariaDetails
Attachments
Patch (18.95 KB, patch)
2017-06-26 04:53 PDT, Joanmarie Diggs
no flags
Patch (19.88 KB, patch)
2017-06-26 07:45 PDT, Joanmarie Diggs
no flags
Radar WebKit Bug Importer
Comment 1 2017-05-25 07:13:22 PDT
Joanmarie Diggs
Comment 2 2017-05-25 07:17:19 PDT
Note that the relation types needed to implement this support will require we update the minimum versions of atk, at-spi2-core, and at-spi2-atk in jhbuild to at least 2.15.2. That also needs to be done in order to fix bug 172355, for which there is a proposed patch. Therefore making this bug depend on 172355.
Joanmarie Diggs
Comment 3 2017-06-02 05:55:16 PDT
(Combining bugs since the implementation of aria-details and aria-errormessage should be simple, small, and quite similar and share the same dependencies.) The aria-errormessage attribute was added in ARIA 1.1. According to the Core AAM [1]: "If the referenced object is in the accessibility tree, expose a pointer to the accessible object using RELATION_ERROR_MESSAGE, and expose reverse relations as described in Relations." The reverse relation type for RELATION_ERROR_MESSAGE is RELATION_ERROR_FOR. Note that the relation types needed to implement this support will require we update the minimum versions of atk, at-spi2-core, and at-spi2-atk in jhbuild to at least 2.15.2. That also needs to be done in order to fix bug 172355, for which there is a proposed patch. Therefore making this bug depend on 172355. [1] https://rawgit.com/w3c/aria/master/core-aam/core-aam.html#ariaErrorMessage
Joanmarie Diggs
Comment 4 2017-06-02 05:55:35 PDT
*** Bug 172589 has been marked as a duplicate of this bug. ***
Joanmarie Diggs
Comment 5 2017-06-02 05:59:05 PDT
Fixing this depends on fixing bug 155494 because the implementation requires reverse relations.
Joanmarie Diggs
Comment 6 2017-06-26 04:53:40 PDT
Build Bot
Comment 7 2017-06-26 04:56:05 PDT
Attachment 313825 [details] did not pass style-queue: ERROR: Tools/WebKitTestRunner/InjectedBundle/AccessibilityUIElement.h:206: 'ariaDetailsElementAtIndex' is incorrectly named. It should be named 'protector' or 'protectedUnsigned'. [readability/naming/protected] [4] ERROR: Tools/WebKitTestRunner/InjectedBundle/AccessibilityUIElement.h:207: 'ariaDetailsReferencingElementAtIndex' is incorrectly named. It should be named 'protector' or 'protectedUnsigned'. [readability/naming/protected] [4] ERROR: Tools/WebKitTestRunner/InjectedBundle/AccessibilityUIElement.h:208: 'ariaErrorMessageElementAtIndex' is incorrectly named. It should be named 'protector' or 'protectedUnsigned'. [readability/naming/protected] [4] ERROR: Tools/WebKitTestRunner/InjectedBundle/AccessibilityUIElement.h:209: 'ariaErrorMessageReferencingElementAtIndex' is incorrectly named. It should be named 'protector' or 'protectedUnsigned'. [readability/naming/protected] [4] Total errors found: 4 in 13 files If any of these errors are false positives, please file a bug against check-webkit-style.
Joanmarie Diggs
Comment 8 2017-06-26 05:00:26 PDT
(In reply to Build Bot from comment #7) > If any of these errors are false positives, please file a bug against > check-webkit-style. They are either false positives or we need to rename a bunch of methods in WKTR and update many of the accessibility Layout Tests which call those methods. If it's the latter case, it goes beyond the scope of this bug.
Joanmarie Diggs
Comment 9 2017-06-26 07:45:17 PDT
Build Bot
Comment 10 2017-06-26 07:47:52 PDT
Attachment 313837 [details] did not pass style-queue: ERROR: Tools/WebKitTestRunner/InjectedBundle/AccessibilityUIElement.h:206: 'ariaDetailsElementAtIndex' is incorrectly named. It should be named 'protector' or 'protectedUnsigned'. [readability/naming/protected] [4] ERROR: Tools/WebKitTestRunner/InjectedBundle/AccessibilityUIElement.h:207: 'ariaDetailsReferencingElementAtIndex' is incorrectly named. It should be named 'protector' or 'protectedUnsigned'. [readability/naming/protected] [4] ERROR: Tools/WebKitTestRunner/InjectedBundle/AccessibilityUIElement.h:208: 'ariaErrorMessageElementAtIndex' is incorrectly named. It should be named 'protector' or 'protectedUnsigned'. [readability/naming/protected] [4] ERROR: Tools/WebKitTestRunner/InjectedBundle/AccessibilityUIElement.h:209: 'ariaErrorMessageReferencingElementAtIndex' is incorrectly named. It should be named 'protector' or 'protectedUnsigned'. [readability/naming/protected] [4] Total errors found: 4 in 14 files If any of these errors are false positives, please file a bug against check-webkit-style.
WebKit Commit Bot
Comment 11 2017-06-26 09:45:38 PDT
Comment on attachment 313837 [details] Patch Clearing flags on attachment: 313837 Committed r218809: <http://trac.webkit.org/changeset/218809>
WebKit Commit Bot
Comment 12 2017-06-26 09:45:40 PDT
All reviewed patches have been landed. Closing bug.
James Craig
Comment 13 2019-09-26 12:11:26 PDT
*** Bug 165190 has been marked as a duplicate of this bug. ***
Note You need to log in before you can comment on or make changes to this bug.