Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
I suggest adding statistics for Aural style sheets which contain CSS properties such as "speak.... #1515
I suggest adding statistics for Aural style sheets which contain CSS properties such as "speak."
This issue was imported from Google Moderator
Moderator votes: +3
referenced this issue
Aug 1, 2015
CSS 2.1 Aural has been deprecated: https://developer.mozilla.org/en-US/docs/Web/CSS/Aural
Suggestions for where to go from 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:
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.
referenced this issue
May 16, 2018
+1 for this from @brennanyoung:
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?