+1

+1

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

+1

+1

+1

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?

@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.

+1

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.

Added #4274 to discuss.

+1

• https://bugzilla.mozilla.org/show_bug.cgi?id=1339987
• https://bugs.chromium.org/p/chromium/issues/detail?id=369863

+1

+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.