W3C home > Mailing lists > Public > public-css-archive@w3.org > March 2017

Re: [csswg-drafts] [css-display] Define interaction of display:contents and replaced elements

From: Amelia Bellamy-Royds via GitHub <sysbot+gh@w3.org>
Date: Thu, 16 Mar 2017 18:26:05 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-287149211-1489688764-sysbot+gh@w3.org>
> the contents of progress/meter are fallback content, exposed to the a11y tree

Not really, see: https://w3c.github.io/html-aam/#el-progress 

Although there's still open debate about how best to expose `meter` as something different from `progress`, they are both expected to be exposed as atomic widgets, with the actual numerical properties mapped to the accessibility API equivalents.  The text content wouldn't be exposed through the API in a supporting browser.  It's only there for older browsers.

> And embed/applet, I think.

Yes for `applet` (I had to look it up, it works like `object`). No for `embed` (which is void, no child/fallback). 

But regardless, my main point was : ideally, try to be as consistent as possible, rather than special rules for each different element type.  But I recognize that we don't live in an ideal world.

GitHub Notification of comment by AmeliaBR
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/540#issuecomment-287149211 using your GitHub account
Received on Thursday, 16 March 2017 18:26:11 UTC

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