Explainer
https://gist.github.com/alice/756caca028b2dae610e4ed5184c2f93e
Spec
https://drafts.csswg.org/css-content/#alt
Tag review
https://github.com/w3ctag/design-reviews/issues/351
Summary
This change allows for alternative text to be supplied for the content supplied using the CSS content property, to be used for non-visual mediums.
Link to “Intent to Implement” blink-dev discussion
https://groups.google.com/a/chromium.org/forum/#!msg/blink-dev/xnoMlEorXxw/mZisL9zqBwAJ
Is this feature supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)?
Yes.
Demo link
https://codepen.io/meredithl/pen/mZqYLW
Debuggability
Can use DevTools Style and Accessibility Panels, chrome://accessibility > Show accessibility tree
Risks
Interoperability and Compatibility
Syntax is not backwards compatible with the content property. See discussion: https://lists.w3.org/Archives/Public/www-style/2016May/0109.html
Firefox: No public signals
P3 bug filed for implementation, see: https://bugzilla.mozilla.org/show_bug.cgi?id=1281158
Edge: No public signals
Safari: Public support (https://bugs.webkit.org/show_bug.cgi?id=120188)
Implementation of vendor prefixed version, uses an alt property rather than the optional slash syntax, but support exists for the concept.
Web developers: Positive (https://twitter.com/rob_dodson/status/1090060058224803840)
Is this feature fully tested by web-platform-tests?
No
Can’t be tested in WPT yet because WPT tests lack a mechanism to assert things about the accessibility tree, for now.
Link to entry on the Chrome Platform Status
https://www.chromestatus.com/features/4550056227110912
Contact emails
Explainer
https://gist.github.com/alice/756caca028b2dae610e4ed5184c2f93e
Spec
https://drafts.csswg.org/css-content/#alt
Tag review
https://github.com/w3ctag/design-reviews/issues/351
Summary
This change allows for alternative text to be supplied for the content supplied using the CSS content property, to be used for non-visual mediums.
Link to “Intent to Implement” blink-dev discussion
https://groups.google.com/a/chromium.org/forum/#!msg/blink-dev/xnoMlEorXxw/mZisL9zqBwAJ
Is this feature supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)?
Yes.
Demo link
https://codepen.io/meredithl/pen/mZqYLW
Debuggability
Can use DevTools Style and Accessibility Panels, chrome://accessibility > Show accessibility tree
Risks
Interoperability and Compatibility
Syntax is not backwards compatible with the content property. See discussion: https://lists.w3.org/Archives/Public/www-style/2016May/0109.html
Firefox: No public signals
P3 bug filed for implementation, see: https://bugzilla.mozilla.org/show_bug.cgi?id=1281158
Edge: No public signals
Safari: Public support (https://bugs.webkit.org/show_bug.cgi?id=120188)
Implementation of vendor prefixed version, uses an alt property rather than the optional slash syntax, but support exists for the concept.
Web developers: Positive (https://twitter.com/rob_dodson/status/1090060058224803840)
Is this feature fully tested by web-platform-tests?
No
Can’t be tested in WPT yet because WPT tests lack a mechanism to assert things about the accessibility tree, for now.
Link to entry on the Chrome Platform Status
https://www.chromestatus.com/features/4550056227110912
--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/63411762-4e82-47ad-9a00-3ecd8c70443a%40chromium.org.
Firefox: No public signals
P3 bug filed for implementation, see: https://bugzilla.mozilla.org/show_bug.cgi?id=1281158
Edge: No public signals
Safari: Public support (https://bugs.webkit.org/show_bug.cgi?id=120188)
Implementation of vendor prefixed version, uses an alt property rather than the optional slash syntax, but support exists for the concept.
Glad to see Safari support the concept. Sad to see it being prefixed...Any sense on their willingness to unprefix once we ship?
Web developers: Positive (https://twitter.com/rob_dodson/status/1090060058224803840)
Is this feature fully tested by web-platform-tests?
No
Can’t be tested in WPT yet because WPT tests lack a mechanism to assert things about the accessibility tree, for now.
Have you filed relevant bugs against the WPT infrastructure?
----Link to entry on the Chrome Platform Status
https://www.chromestatus.com/features/4550056227110912
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/63411762-4e82-47ad-9a00-3ecd8c70443a%40chromium.org.
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CACj%3DBEhJcfAzjh1cxY3L%2BUR5vJaxv-yj-_%3DiRsh8py_qZPNYTQ%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CACj%3DBEiSmvkLOog-59PuVwfSy47DLuV6E5K9%3DNgCzqtBUy%3DfRw%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOMQ%2Bw8m8v9dxu0U%2BCq-2_5V7iOB68jZt%3D-ec562LzwbU16vVg%40mail.gmail.com.