Bug 122138 - AX: WebKit does not expose text alternative of CSS generated image content
Summary: AX: WebKit does not expose text alternative of CSS generated image content
Status: RESOLVED DUPLICATE of bug 159022
Alias: None
Product: WebKit
Classification: Unclassified
Component: Accessibility (show other bugs)
Version: 528+ (Nightly build)
Hardware: All All
: P2 Normal
Assignee: Nobody
URL:
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2013-09-30 21:59 PDT by James Craig
Modified: 2022-03-15 16:14 PDT (History)
2 users (show)

See Also:


Attachments
test case (5.20 KB, text/html)
2013-09-30 21:59 PDT, James Craig
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description James Craig 2013-09-30 21:59:38 PDT
Created attachment 213054 [details]
test case

AX: WebKit does not expose text alternative of CSS generated image content. E.g.

  a[href$=".pdf"]::after { content: url(./pdf.png), "(PDF)"; }

Note: I think it should retain the AXImage's AXRole and AXRoleDescription, but otherwise let AT decide what to speak. Since this is inside a link, it should not be treated differently than if there was a hardcoded markup image in the link. So, on the link you'd hear "link, User Guide (PDF)" and if it was just plain text, you'd hear two elements, "User Guide" static text and then "(PDF) image"

Some related discussion on www-style and from the TPAC 2011.
http://lists.w3.org/Archives/Public/www-style/2012Nov/0316.html
Comment 1 James Craig 2013-09-30 21:59:43 PDT
<rdar://problem/10384914>
Comment 2 James Craig 2013-09-30 22:01:56 PDT
related to bug 120188
Comment 3 James Craig 2013-11-04 12:49:17 PST
Once this is patched, you should include a test to ensure it does not regress -webkit-alt.

content: url(resources/cake.png), "foo";
-webkit-alt: "bar, not foo";

content: url(resources/cake.png), "";
-webkit-alt: "not empty";

content: url(resources/cake.png), "foo";
-webkit-alt: ""; // should be empty, not foo

See bug 120188
Comment 4 James Craig 2022-03-15 16:14:21 PDT
Overcome by a later CSS WG syntax covered in https://bugs.webkit.org/show_bug.cgi?id=159022

*** This bug has been marked as a duplicate of bug 159022 ***