← Back to context Comment by luckydata 11 days ago that's a problem for accessibility too 2 comments luckydata Reply UqWBcuFx6NV4r 11 days ago No, it really isn’t. Use of Tailwind has no bearing on the semantics of your HTML. You’re conflating two completely different things. isqueiros 11 days ago tailwind is very much not a problem for accessibility? if your content is semantic and you add the appropriate aria tags, whether or not you have 300 classes or 1 will make no difference for screen readers
UqWBcuFx6NV4r 11 days ago No, it really isn’t. Use of Tailwind has no bearing on the semantics of your HTML. You’re conflating two completely different things.
isqueiros 11 days ago tailwind is very much not a problem for accessibility? if your content is semantic and you add the appropriate aria tags, whether or not you have 300 classes or 1 will make no difference for screen readers
No, it really isn’t. Use of Tailwind has no bearing on the semantics of your HTML. You’re conflating two completely different things.
tailwind is very much not a problem for accessibility? if your content is semantic and you add the appropriate aria tags, whether or not you have 300 classes or 1 will make no difference for screen readers