Two approaches are being explored: 1) either in-lining #SSML markup the same way as #SVG or #MathML can be, or 2) bringing the SSML model via attributes in HTML
w3.org/TR/2020/WD-pronunciat…
The explainer “Improving Spoken Presentation on the Web” explores what mechanisms can be provided to give pronunciation guidance in #HTML content - this is helpful for #accessibility and for voice assistants reading content off the Web
A @w3c CSS4 #CommunityGroup was recently launched to give more space for the discussion of what would a CSS4 label encompass - join if you want to help!
It is important to note that the @csswg decided not to try to describe #CSS for users and #developers. The group works primarily for implementors and hopes others like MDN would create resources for devs. For ex., check the CSS reference on @MozDevNet: developer.mozilla.org/en-US/…
That's why, starting from 1999, #CSS was decomposed into modules, each having its own life at its own pace. Each module defines a part of CSS to allow more immediate, incremental improvement of the specification: w3.org/Style/2011/CSS-proces…
All current #CSS specs have their own specific levels ranging from 1 to 5, but CSS as a whole does not have a version. Two reasons: 1) some features are easier to complete than others, 2) CSS became so big that it is too much work for the editors to maintain as a monolithic spec.
This specification was eventually renamed CSS 2.1 (a revision was published in June 2011 - Editors were Bert Bos, @viumlie, @Hixie and @t)
w3.org/TR/CSS2/