Post #1068259

2026-04-09 06:44 UTC

Not using semantic classes and names for your HTML elements is an accessibility violation. It prevents people from properly leveraging user provided CSS styles that help them use your site/app. E.g. I use many user styles to enhance readability or to remove clutter and noise from websites I frequent, helping me read and analyze. Unsemantic soup like in this image makes it near impossible and unpredictable to write user styles. #a11y #Accessibility #CSS #HTML #SemanticWeb #WebDevelopment

Replies (2)

@mugentoki@mastodon.social 2026-04-09 07:17

@ojrask Completely agree with you. Also I wanna throw something else in: Ignoring accessibility can lead to serious fines. In the European Union for example, we have the "European Accessibility Act (EEA)" which basically requires you to comply with WCAG2 rules. At least if you offer products or services. Fines are depending on the country, but can go up into millions of €.

Open ##1068265
@Isofruit@mastodon.social 2026-04-09 08:43

@whangdoodler if you want Devs to use semantic CSS I would not use the wcag as an argument. As far as I recall it contains nothing related to that level of style customisation beyond setting global font/text styles. I would focus on advocating for e.g. BEM and technologies/CSS organisation patterns that avoid class name soup. Edit: @mugentoki (I had intended to reply to you)

Open ##1068266