W3C home > Mailing lists > Public > public-css-archive@w3.org > July 2018

Re: [csswg-drafts] [mediaqueries-4] Port Media Groups section of CSS2.1

From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
Date: Wed, 04 Jul 2018 06:30:23 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-402377185-1530685822-sysbot+gh@w3.org>
The Working Group just discussed `porting media groups`, and agreed to the following:

* `RESOLVED: Add a normative statement for properties that say "Media: all" explaining what "Media: all" meant.`

<details><summary>The full IRC log of that discussion</summary>
&lt;heycam> Topic: porting media groups<br>
&lt;heycam> github: https://github.com/w3c/csswg-drafts/issues/2413<br>
&lt;heycam> fantasai: I ran a grep through the tree<br>
&lt;heycam> ... almost everything is Visual, some exceptiosn<br>
&lt;heycam> ... interactive vs not is not interesting<br>
&lt;heycam> ... but we distinguish between CSS props that shuld affect the accessibility tree, and the ones that shouldn't<br>
&lt;heycam> ... or don't<br>
&lt;heycam> ... content prop affects what shows up to a screen reader<br>
&lt;heycam> ... display does<br>
&lt;heycam> astearns: how is that expressed?<br>
&lt;heycam> florian: by Media: all<br>
&lt;heycam> astearns: are we consistent about that?<br>
&lt;heycam> fantasai: yes<br>
&lt;heycam> ... props that should add or remove content from the a11y tool<br>
&lt;heycam> ... it's an indicator to the screen reader as to what content should be added or skipped<br>
&lt;heycam> florian: I think it's not about screen readers<br>
&lt;heycam> ... it's about audio rendering<br>
&lt;heycam> fantasai: yes, but if we remove this, we need to make sure we're very clear in the spec, explicit wording to say this prop needs to affect non visual things<br>
&lt;heycam> dbaron: I think if that was the intent of the spec, I suspect most implementors missed it<br>
&lt;heycam> ... I think it would be good to have the wording in some other way<br>
&lt;heycam> astearns: I think it would be an improvement to be explicit, rather than hide it here<br>
&lt;heycam> frremy: most of these things, if they're defined, are in ARIA, they explicitly call out the properties and what you should do with them<br>
&lt;heycam> florian: for a11y, probably, for visual and non-visual media .... for the ones that say "all", a normative statement that says "this works on all media" is fine<br>
&lt;heycam> astearns: it should be more explicit<br>
&lt;heycam> ... "such as, screen readers"<br>
&lt;heycam> florian: no<br>
&lt;heycam> ... they don't work like that<br>
&lt;heycam> ... they're a visual media<br>
&lt;heycam> fantasai: but they're also not handling gencon properly<br>
&lt;heycam> Rossen: they do<br>
&lt;heycam> frremy: in Edge it works perfectly<br>
&lt;heycam> fantasai: but it is a common bug<br>
&lt;heycam> frremy: the content thing is defined precisely in the ARIA specs<br>
&lt;heycam> ... I don't believe we need to say anything in the CSS specs<br>
&lt;heycam> ... it says gencon should be exposed<br>
&lt;heycam> ... but it shouldn't require any specific wording<br>
&lt;heycam> florian: I would suggest adding a sentence not a11y specific, calling out that this property is supposed to apply to all kinds of rendering, even not visual<br>
&lt;heycam> ... not specifically to a11y, e.g. audio rendering without a screen reader, don't forget this property<br>
&lt;heycam> astearns: would that be enough?<br>
&lt;heycam> dbaron: sure<br>
&lt;heycam> fantasai: we should have these kinds of sentences anyway.  in the propdef table it's easy to look up which ones you need to care about<br>
&lt;heycam> ... but it takes up a lot of space<br>
&lt;heycam> ... removing from the propdef table is a benefit overall<br>
&lt;heycam> ... we should add a statement explaining normatively that CSS requires these to work<br>
&lt;heycam> ... we're defining what the properties mean and how they're interpreted, ARIA then uses that<br>
&lt;heycam> RESOLVED: Add a normative statement for properties that say "Media: all" explaining what "Media: all" meant.<br>
&lt;florian> ScribeNick: Florian<br>

GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2413#issuecomment-402377185 using your GitHub account
Received on Wednesday, 4 July 2018 06:30:49 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:41:33 UTC