JAWS does not support alt text for CSS pseudo content content with url image

[mraccess77]

Summary

JAWS does not support alt text for CSS pseudo content content with url image on calculated accessible name. JAWS will speak CSS content when url is not used -- but not when URL is used.

Example:
button::before {
content: url(./img/star.png) / "New!";
}

Expected result

The text "New!" is announced.

Actual result

The text "New!" is not announced.

Example

A test case that demonstrates the issue - provide linked test case, CodePen, JSbin, etc...

Additional Information

JAWS version and build number

2020 - February Update

Operating System and version

Browser and version:

Chrome

[JAWS-test]

This possibility of alt text is so far only specified in the CSS Working Draft. No idea whether this is already so final that AT should implement it

[JAWS-test]

I have tested the problem with Chrome 79.0.3945.130 and JAWS 2020.1910.54 (and JAWS 2019 and NVDA 2019), but the problem does not occur: the alternative text is output correctly. You can also see in the developer tools of Chrome that the alternative text is transmitted correctly. The empty alternative text for marking decorative content also works correctly.

See: https://codepen.io/jaws-test/pen/PoqqYgv

Unfortunately, this function is currently not supported by Firefox (and IE 11), so that CSS content with alternative text is not displayed and output at all.

[cblouch]

Looks like it's working with buttons but not links on JAWS 2020.2001.70. For example:

link

and then in the CSS

#b1:after {
content: url(test.jpg) / "this is alt text";
}

Does not seem to matter if I'm using :before or :after or whether the rule is based off the ID as shown above or applied to all anchors.

[JAWS-test]

True, for links the URL of the link is output if the pseudo content is a graphic, although Chrome transmits the Accessible Name correctly (see https://codepen.io/jaws-test/pen/eYNNdro). I had tested with buttons, because the example of @mraccess77 referred to buttons.

The problem does not occur with Chrome+NVDA. So it is actually a bug in JAWS.

The incorrect output occurs in forms mode, when navigating with the virtual cursor, in fast navigation, and in the element overview. The link is output as a link with graphic.

[stevefaulkner]

noted that when virtual cursor turned off and the link is focused, it announces correctly. Also noted in chrome the correct accessible name is present for both button and link.
test case and codepen

[JAWS-test]

Related: #297