@hbuchel I think for me, I see web designers mostly taking care of the "Figma" (or equivalent) part, and frontend developers want to mostly take care of the JS part. And the problem I see is with the HTML/CSS.
I personally think that web designers should be able to write HTML and CSS for the different components, and the frontend developers would "just" need to make the components interactive with JS. However, nowadays your HTML mostly depends on your web framework, creating a list of components uses different keywords in different frameworks, in some cases we put the HTML in a different file and in other cases we put it in the same file, and write JS directly in it... It has become a happy mess, and nobody writes good ol' HTML and CSS anymore. As a result, it became the responsibility of frontend developers, who are usually not educated on the new frameworks they're going to use and will likely produce something that results in a horrible DOM. After all, they mostly want to do JS.
At least, that is what I see in the industry: web designers take care of Figma, frontend developers take care of reimplementing things in the web framework the project uses, and we rarely have any kind of expert in HTML, which means all the accessibility elements of HTML, that are usually not visible, are just lost. But, at least, we have somewhat coherent looking web pages ​:akko_shrug:​
