91–100 of 258 posts
Earlier quoted context omitted.
> Side projects are typically time constrained What is the urgency in completing side projects? Commercial projects are usually the ones where you have some urgency.
If you only have a few hours a week and you want to actually finish a project the speed with which you can build is extremely important.
This has been killing me recently. Apparently I need slightly higher contrast than some people, and these vibe coded UIs are basically unreadable to my eyes
Earlier quoted context omitted.
I've genuinely had solid results from telling Claude "... and make sure it has good accessibility".
I could see that. I’ve found that the more specificity you add to your prompt and less freedom you give Claude Code to kind of just “do its own thing”, the better your results will be. FWIW, there’s also an official frontend-design skill for CC [1]. A while back I incorporated some of the more relevant guidance from WCAG into it [2]. [1] - https://github.com/anthropics/claude-code/blob/main/plugins/... [2] - https://…
Earlier quoted context omitted.
My biggest issue with LLM‑assisted webpages (Claude Code is especially egregious) is the lack of respect for basic web content accessibility guidelines. The number of dark‑mode sites I’ve seen where the text (and subtext) are various shades of dark brown or beige is just awful. For reference, you want a contrast ratio between the text and background of at least ~4:1 to be on the safe side. This isn't even that hard t…
Just chiming in to say I don't care at all about accessibility and I find it bewildering that every thread sharing some project has a comment like this.
Yes, it's the September That Never Ended again. It's fun to complain about the good ol' days, but I'd rather face the world as it is and find the joy in it. http://www.catb.org/jargon/html/S/September-that-never-ended... https://en.wikipedia.org/wiki/Eternal_September The advantage of having so many ideas being tried and published is we are exploring the space of possibility faster, and so there's more to learn from.…
(Still plenty of scary stuff, but I should feel like you at least some of the time, healthy balance.)
Yes, it's the September That Never Ended again. It's fun to complain about the good ol' days, but I'd rather face the world as it is and find the joy in it. http://www.catb.org/jargon/html/S/September-that-never-ended... https://en.wikipedia.org/wiki/Eternal_September The advantage of having so many ideas being tried and published is we are exploring the space of possibility faster, and so there's more to learn from.…
Earlier quoted context omitted.
I think accessibility is a really admirable thing and helpful to society (like ramps or parking). But stop shoving your wants on others when you can fix it on your own. Just write a chrome plugin using ai that adjusts css to set contrast ratio of your choice. Can even use a local llm to figure out replacement colors. Accessibility that can be had on client side should not be a concern on server side.
That's a really terrible option for the vast majority of people who simply lack that kind of tech savviness to be able to do it. And in my opinion, it's kind of selfish. It also doesn't solve the issue if somebody is browsing your site on a mobile phone where the extension might not even work properly. WCAG is not difficult - but it does require some modicum of effort.
There's a big difference between vibe-coder and engineer who uses ai to speed up their work.
Indeed, and I don't think there's any reliable signal other than the author saying so that something is "vibe coded" vs. "I used an LLM for some aspect of it."
And then look through the commits -- were they only adding new features, or did the author(s) put effort into improvements on engineering fundamentals (benchmarking, testing, documentation, etc)?