Re: [csswg-drafts] [mediaqueries-4 ] Deprecate 'speech' media type as well? (#1751)

@FremyCompany I agree most of what you said. As for "People who rely on assistive technologies do not want to disclose that", that is also true, but it seems a little disconnected from this feature: `@media speech { }` is not relevant from screen readers. Screen readers generate speech, but they are not standalone sound-only user agents: they're paired with a `@media screen` user agent and do take the visual into account as well. Media types are exclusive, so `@media speech` applies to media that **only** generate sound and don't match `@media screen`. screen readers don't match `@media speech`, and it would be a spec violation for them to match it.

`@media speech` is only for audio-only UAs, for example alexa/siri or linear rendering of audio books. Some software is roughly like this, but I have not run across any that implements speech media type. Other have also looked, with no more success. And as you said, even in the context of audio-only UAs, it's far from clear that using `@media speech` would be helpful, as audio related properties can be set by the author unconditionally, and merely get ignored when rendering the page visually.

Nonetheless, it happens repeatedly that people get confused and believe that speech is screenreaders. So we should probably drop it and move it to deprecated media types where syntactically valid but defined to never match.

@LJWatson, the csswg was inclined to agree to deprecate this, but we didn't resolve as we wanted to hear your point of view on this.

GitHub Notification of comment by frivoal
Please view or discuss this issue at using your GitHub account

Received on Thursday, 21 May 2020 04:04:04 UTC