No, it’s of course not just aria attributes. But it’s definitely not “how easy can I create user CSS”. Accessibility is a term of art, you can’t just expand its meaning to whatever you want.
Look, if it hinders me in my workarounds for my ADHD while every other framework does less so, then accessibility is worse. Shut up with your trademark gatekeeping bullshit.
![[ComiCSS] Benefits of Tailwind](https://files.catbox.moe/36lx9g.webp){kind=link}
Would be fine if it used a custom parameter for their tags. Using class names makes for bad accessibility.
How are class names relevant for accessibility?
https://lemmy.zip/comment/19872383
Usability by third-parties. A webpage is not a pdf.
That’s not accessibility.
You think only aria-attributes are accessibility? Most accessible is, what you not need additional tools and interpreters for.
No, it’s of course not just aria attributes. But it’s definitely not “how easy can I create user CSS”. Accessibility is a term of art, you can’t just expand its meaning to whatever you want.
https://en.wikipedia.org/wiki/Accessibility
Look, if it hinders me in my workarounds for my ADHD while every other framework does less so, then accessibility is worse. Shut up with your trademark gatekeeping bullshit.
Also,
They might mean class names can’t help screen readers parse meaning, whereas using the correct tag can?