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

Re: [csswg-drafts] Separation of style and content (#3778)

From: Alice via GitHub <sysbot+gh@w3.org>
Date: Sat, 30 Mar 2019 21:41:14 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-478291654-1553982072-sysbot+gh@w3.org>
I think it's a false dichotomy in any case to assume that the accessibility tree, focus, find in page etc. *shouldn't* depend on style. These experiences are and should be fundamentally based on the end result of layout, rendering etc, not the un-styled markup. It would make no sense for an element with `display: none` to take focus, for example.

For what my opinion is worth here, I think of the separation of style and content as more of a pragmatic progressive enhancement issue than a strict separation issue. Things should work ok without style, and probably better with style; they're unlikely to be the *same* experience, but they should be *comparable* (which is a [useful term from the inclusive design sphere](https://inclusivedesignprinciples.org/#provide-comparable-experience)). 

To me that helps draw a line around what information belongs in style and what doesn't - does this belong to the baseline experience or the styled experience? I could conceive of a case where a role only makes sense in the context of a style, and the page works OK without it (for example, applying a non-widget ARIA role to a pseudo-element).

GitHub Notification of comment by alice
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3778#issuecomment-478291654 using your GitHub account
Received on Saturday, 30 March 2019 21:41:15 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 20:26:58 UTC