+1

(Aural has been superseded by http://www.w3.org/TR/css3-speech/ )

+1

There is very little info on this. It would be great for this to be included.

+1

CSS3 Version: https://www.w3.org/TR/css3-speech/
+1

+1

Why is there no movement on this three year old issue.

CSS 2.1 Aural has been deprecated: https://developer.mozilla.org/en-US/docs/Web/CSS/Aural

As @rogerfrace pointed out, for CSS 3 there's the Speech module.

The CSS Speech module is a re-work of the informative CSS2.1 Aural appendix, within which the "aural" media type was described, but also deprecated (in favor of the "speech" media type). Although the [CSS21] specification reserves the "speech" media type, it doesn't actually define the corresponding properties. The Speech module describes the CSS properties that apply to the "speech" media type..

@frob note that this issue is currently behind 4 others in the list of requested features so there's clearly interest. And maybe we can other developers to +1 this?

Suggestions for where to go from here:

1. We should close this issue, and move discussion (and +1's to here: CSS3 Speech Module Which browsers support it? See #1240 )

2. Anyone with time could contribute a pull request. For base data, you could start here.

Sidenote, I just ran across a good article about CSS Speech. (Also, you'd think with the popularity of voice based devices this will become increasingly important!)

Good to see some discussion!

And thanks for the excellent css-tricks link. It touches on various topics I think are under-explored.

I'd be happy to see this issue closed and migrate our attentions to #1240

I was aware about CSS 2.1 Aural -> CSS 3 speech. Although there is very little information about what is currently going on with CSS 3 speech implementations. Caniuse is the first place I look for such data, so the vacuum is striking. The impression given is that the whole effort is stagnating or even deprecated, although this must certainly be incorrect.

Primarily there should be coverage in caniuse of CSS 3 speech, with CSS 2.1 Aural mentioned in a stub that points to the CSS 3 speech resources.

As I see it, there are two 'real-world' usage concerns here:

1. Browser support for css 3 speech
2. Screenreader support for css3 speech

It's all very well if a browser doesn't complain about css3 speech properties, or even does something useful with them, when using the speech synth features, but until screenreaders are standard features of ordinary browsers (go Opera!), what (I believe) we most sorely need is data about how screenreaders handle those properties.

Perhaps bolt-on screenreaders fall out of the scope of caniuse. But what to make of browser vendors that have delegated screenreading to the OS they themselves control. (viz. Apple's Safari with VoiceOver and Microsoft's Edge/IE with Narrator)? It's reasonable to expect that these vendors have allocated some 'design thinking' resources to how the browser and the system-level screen reader interact, and web content professionals will need to know how well they are doing.

Screenreader support for css3 speech is something that needs tracking somewhere, now that WCAG is being mandated across North America, in the EU and in various other regions. If not in caniuse, then where?

It's time to get the ball moving again.

+1 for this from @brennanyoung:

Primarily there should be coverage in caniuse of CSS 3 speech, with CSS 2.1 Aural mentioned in a stub that points to the CSS 3 speech resources.

Let's keep this issue open until "CSS 2.1 Aural mentioned in a stub" is implemented, and meanwhile focus discussion specific to CSS 3 Speech Module to #1240.

OK I just committed a stub for CSS 2.1 Aural. I left all the default versions in, but changed the support flag to "n". AFAICT this is correct, although we perhaps don't need ALL those browser versions listed. (Is there a preferred way to trim those to the minimum "not gonna happen" setting?

@brennanyoung Is there a PR that needs checking? I don't see anything linking any commit and this issue.

@frob
as per #4263 (comment)

So, now the 'stub' appears as a search result, rather than a full entry.

This is quite suitable. When we get the CSS 3 Speech data in there, the stub should also point to that.

Should this issue be closed now or do you want to leave it as a reminder to add the speech notes once that entry is added?

"CSS Speech Module Level 1" is now a W3C Candidate Recommendation Draft

https://www.w3.org/TR/css-speech-1/

Trying to figure out what, if anything, supports it.