Vent: A simple form label issue ate up my whole Friday

I was checking a signup form for a local non-profit's site, thinking it would be a quick pass. The visual labels looked fine, but my screen reader test kept skipping a required field. Turns out, the developer used a placeholder as the only label, which is a huge no-go for accessibility. What I thought was a 30-minute review turned into a 6-hour deep dive with the dev to trace the styling and rebuild the component properly. We had to redo the HTML structure and test with three different assistive tools. Has anyone else been blindsided by a seemingly small markup choice that caused a major time sink?

3 comments

3 Comments

victor_robinson362mo ago

Honestly, I get why you're mad but sometimes you have to pick your battles. That six hour deep dive sounds like overkill for a non-profit's signup form. Most people can see the placeholder text just fine and it looks cleaner without all the extra labels. Spending that much time on a tiny part of the site that maybe one person uses with a screen reader seems like a bad use of a dev's time. Tbh, perfect accessibility can wait when you have bigger problems to fix.

robert_bennett291mo ago

Feel that pain deep in my bones. Watched a junior dev spend a whole day trying to make a color picker "accessible" while the main donation page was broken. It's not about one person with a screen reader, it's about building the habit right so it doesn't become a huge rework later. But you're also right, you can't fix everything at once and sometimes clean placeholder text is the compromise that lets you ship. Still hurts to see it though.

gibson.nathan2mo ago

Placeholder labels are the worst, I've definitely lost a weekend to something similar.