RESOLVED FIXED 226534
iOS - VoiceOver reads the programmatically associated label instead of the accessible name provided via the aria-label or aria-labelledby attribute
https://bugs.webkit.org/show_bug.cgi?id=226534
Summary iOS - VoiceOver reads the programmatically associated label instead of the ac...
Andres Gonzalez
Reported 2021-06-02 07:37:54 PDT
iOS - VoiceOver reads the programmatically associated label instead of the accessible name provided via the aria-label or aria-labelledby attribute
Attachments
Patch (13.77 KB, patch)
2021-06-02 08:02 PDT, Andres Gonzalez
no flags
Patch (13.77 KB, patch)
2021-06-10 06:20 PDT, Andres Gonzalez
no flags
Radar WebKit Bug Importer
Comment 1 2021-06-02 07:38:04 PDT
Andres Gonzalez
Comment 2 2021-06-02 07:41:45 PDT
Andres Gonzalez
Comment 3 2021-06-02 07:45:08 PDT
Expected: When an input has a programmatically associated label and an aria-label attribute or aria-labelledby attribute, based on the accessible name computation the aria-label or aria-labelledby attribute should take precedence over the programmatically associated label. Actual: VoiceOver on iOS, reads the programmatically associated label instead of the accessible name provided via the aria-label or aria-labelledby attribute Applies to input types: text, password, search, tel, email and url On macOS Catalina Version 10.15.5 works as expected - aria-label or aria-labelledby attribute takes precedence over the programmatically associated label.
Andres Gonzalez
Comment 4 2021-06-02 08:02:11 PDT
chris fleizach
Comment 5 2021-06-07 20:40:08 PDT
Comment on attachment 430350 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=430350&action=review > Source/WebCore/ChangeLog:10 > + given objet, and using the label of that title element as the label of object > Source/WebCore/accessibility/atk/WebKitAccessibleUtil.cpp:111 > + if (text.textSource == AccessibilityTextSource::LabelByElement && !coreObject->titleUIElement()) if we don't expose the titleUIElement, should it even be in the accessibilityText that's generated?
Andres Gonzalez
Comment 6 2021-06-10 06:20:49 PDT
Andres Gonzalez
Comment 7 2021-06-10 06:28:57 PDT
(In reply to chris fleizach from comment #5) > Comment on attachment 430350 [details] > Patch > > View in context: > https://bugs.webkit.org/attachment.cgi?id=430350&action=review > > > Source/WebCore/ChangeLog:10 > > + given objet, and using the label of that title element as the label of > > object Fixed. > > > Source/WebCore/accessibility/atk/WebKitAccessibleUtil.cpp:111 > > + if (text.textSource == AccessibilityTextSource::LabelByElement && !coreObject->titleUIElement()) > > if we don't expose the titleUIElement, should it even be in the > accessibilityText that's generated? This is used for aria-label, so you can have a form field, for instance, with aria-label="blah" and we want to return "blah" if there is no titleUIElement. It seems that the precedence of titleUIElement over aria-label was established at some point, but I have not check what the aria spec says about this, if any thing.
EWS
Comment 8 2021-06-10 12:08:59 PDT
Committed r278718 (238686@main): <https://commits.webkit.org/238686@main> All reviewed patches have been landed. Closing bug and clearing flags on attachment 431069 [details].
Note You need to log in before you can comment on or make changes to this bug.