Re: [w3ctag/design-reviews] CSS Overflow Navigation Controls (Carousels) (Issue #1037)

flackr left a comment (w3ctag/design-reviews#1037)

> 1. It seems that [scroll markers would be used to impart roles to elements on the page](https://github.com/w3c/csswg-drafts/issues/12122#issuecomment-2920507737), and the nature of those roles would vary depending on whether the CSS author choses `discrete` or `navigation`. Setting roles via CSS is a fundamental expansion of what CSS is doing.
>    We do not think this is an appropriate use of CSS, and would encourage you to investigate the [Cascading Attribute Sheets](https://gist.github.com/tabatkins/4074abaf486af5b3f7ac289737e216e4) proposal, for this and future work. This seems like an effective way to address the general need, whilst maintaining separation of concerns.

The HTML attributes are as always the ultimate authority on the accessibility properties, however this is an example of an inferred role. There are many other cases where CSS already affects the inferred roles of nodes. In general many of the roles are determined in [AXNodeObject::RoleFromLayoutObjectOrNode](https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/renderer/modules/accessibility/ax_node_object.cc?q=%20AXNodeObject::RoleFromLayoutObjectOrNode&ss=chromium%2Fchromium%2Fsrc) by which LayoutObject we have. The function [LayoutObject::CreateLayoutObject](https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/renderer/core/layout/layout_object.cc;drc=2e2446ce78857c808c9b38afe6b527e455fe6c65;l=362) considers many styles.
* For pseudo-elements specifically the value of the content property determines whether the created object is treated as an image or not.
* The display CSS property is used to automatically assign list-item and various table roles

The CSS in this case is not specifically to set the role, but is about the behavior. The differing behaviors of course imply differing role, just as setting the various display values or content values can do.

Am I misunderstanding what you mean by setting roles via CSS?

> 2. What advice would be given to developers to help them decide whether the 'tabs' or 'links' semantics are more important?
> 
> Given particularly the first of these issues, we are still concerned about the addition of these features to the platform, particularly in their current form. We are keen to hear your thoughts on them.

Since selecting tabs or links has a significant impact (aside from the inferred roles) on the way the user interacts with the content, they should end up with the correct role based on the usage model. This is unlike the previous variant where they were expected to set up the behaviors and the roles separately.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/1037#issuecomment-5357662695
You are receiving this because you are subscribed to this thread.

Message ID: <w3ctag/design-reviews/issues/1037/5357662695@github.com>