Zach Leatherman
Andrew Feeney@zachleat Honestly this fine. I can read that code. I can find what I need to edit it quickly and easily. It’s right next to the markup it is coupled to. I can predict exactly what my changes will do and what code will be affected. I can rest easy knowing I haven’t broken something somewhere else. I have this wrapped in a component for easy reuse.
Jared White (ResistanceNet ✊)@andrewfeeney @zachleat Well I can't read it. 🤷🏻♂️
I'll happily cop to being cognitively impared so that utility-classes-gone-wild can be seen as an accessibility violation. If all of this were in a co-located <style> tag as vanilla CSS, I could read that easily. 😊
@jaredwhite @zachleat Yes, I agree it’s not perfect. Accessibility is certainly a valid concern that I have little insight into and I am not surprised to hear that Tailwind is wanting in this regard.