Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CSS3 Speech Module Which browsers support it? See #1240

Open
Fyrd opened this issue May 12, 2015 · 16 comments
Open

CSS3 Speech Module Which browsers support it? See #1240

Fyrd opened this issue May 12, 2015 · 16 comments

Comments

@Fyrd
Copy link
Owner

Fyrd commented May 12, 2015

CSS3 Speech Module
Which browsers support it?
See: http://www.w3.org/TR/2011/WD-css3-speech-20110419/


This issue was imported from Google Moderator

Moderator votes: +6
Issue added by Ozzy on 2012-05-06
To vote this issue up or down, simply include +1 or -1 in your comment.

@beatak
Copy link

beatak commented Feb 22, 2016

+1

@neoncitylights
Copy link

neoncitylights commented Feb 22, 2016

+1

1 similar comment
@techieshark
Copy link

techieshark commented Sep 5, 2016

+1

@cvrebert
Copy link
Contributor

cvrebert commented Dec 8, 2017

Updated spec link: https://drafts.csswg.org/css-speech-1/

@Pr0methean
Copy link

Pr0methean commented Apr 10, 2018

+1

@tommai78101
Copy link

tommai78101 commented May 1, 2018

+1

@brennanyoung
Copy link

brennanyoung commented May 16, 2018

+1

@brennanyoung
Copy link

brennanyoung commented May 16, 2018

It's been suggested on the discussion under #1515 to merge with this issue, and close #1515.

Somehow I think it should be the other way round because #1515 is placed very high at https://caniuse.com/issue-list whereas #1240 is considerably lower. They are essentially duplicates.

If we do this, will the votes for both get summed? If so, it doesn't matter which one is the 'winner'.

Can anyone offer a compelling reason not to do this at some early opportunity?

@techieshark
Copy link

techieshark commented May 16, 2018

@brennanyoung thanks for your comments. Since the feature requested in #1515 was never completed, perhaps it should stay open to discuss completing as the CSS 2 stub, as you suggested there.

Getting vote parity between this issue and #1515 shouldn't be hard, we just need 10 more +1's here.

@frob
Copy link

frob commented May 22, 2018

+1

@frob
Copy link

frob commented May 22, 2018

It sounds like these are two different issues about the same essential topic --css accessibility.

Once the stub is done and speech is implemented it would be good to make sure there is a link in the notes on https://caniuse.com/#feat=wai-aria to these topics and other accessibility related topics/features.

But that should be filed under a new issue.

@frob
Copy link

frob commented May 22, 2018

Added #4274 to discuss.

@Malvoz
Copy link
Contributor

Malvoz commented Jun 18, 2018

@xerz-one
Copy link

xerz-one commented Aug 26, 2019

+1

1 similar comment
@Pr0methean
Copy link

Pr0methean commented Sep 14, 2019

+1

@hcientist
Copy link

hcientist commented Mar 18, 2021

+1 It looks like the issue here doesn't reference the most recent info, it's in CR (Candidate Recommendation) Status with W3C from Spring 2020.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests