- From: Sarah Higley <notifications@github.com>
- Date: Thu, 17 Sep 2026 04:44:15 -0700
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <w3ctag/design-reviews/issues/1037/5713769495@github.com>
smhigley left a comment (w3ctag/design-reviews#1037) > I mentioned above in https://github.com/w3ctag/design-reviews/issues/1037#issuecomment-5357662695 how we already have several ways in which CSS applies non-generic roles to elements (and pseudo-elements), not just removes them. For example specifically ([demo](https://jsbin.com/nekofem/edit?html,css,output)): This is not quite as straightforward an example as you claim 😅. The behavior of `display: listitem` or `display: table` adding semantic roles is a rather controversial and unspec'd internal Chrome behavior, and does not carry over to other browser engines. Even in Chrome, `display: table` creates a layout table, not a true table. <img width="547" height="229" alt="screenshot of the linked jsbin, showing that display listitem and table do not create listitems and tables" src="https://github.com/user-attachments/assets/91570ac0-c5bd-4eb5-828c-d5f9d8965fc4" /> Re: images in CSS content -- I just can't see how this is at all similar to creating entire widgets and composite widgets in CSS in a way that can be referenced as prior art. Perhaps I should have been more precise in using the word "semantic" -- I am specifically concerned about semantics that are more involved than essentially different types of static inline content being defined in CSS. Re: the column scroll marker issue -- many accessible names are not counter-based, nor is composing a static string + counter a good practice for localization. I have not yet seen an example of how to give each column scroll marker a true custom accessible name. On the translation bit -- per-site custom attributes would also not be user-translatable, now or in the foreseeable future. -- Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/1037#issuecomment-5713769495 You are receiving this because you are subscribed to this thread. Message ID: <w3ctag/design-reviews/issues/1037/5713769495@github.com>
Received on Thursday, 17 September 2026 11:44:19 UTC