February 24, 2026 · 4 min read
An Image Captioning Use Case Nobody Expected to Actually Work
We built image captioning for accessibility compliance as a checkbox requirement. It ended up solving a completely different, more valuable problem nobody had scoped.
The ask was narrow: auto-generate alt text for product images to meet accessibility requirements before an audit deadline. It was treated internally as a compliance checkbox, not a feature anyone expected to matter beyond screen readers. We scoped it, built it with an off-the-shelf captioning model fine-tuned lightly on the client's product taxonomy, and shipped it ahead of the deadline.
Where it accidentally got useful
A few weeks later, someone on the merchandising team noticed the generated alt text was accurate enough to be indexed by the internal product search tool, and customers searching for vague descriptive terms — 'blue striped linen shirt' rather than a SKU or brand name — were suddenly getting much better results, because the alt text was now carrying descriptive detail the original product titles never had.
The accessibility checkbox feature ended up doing more for product discoverability than two prior quarters of deliberate search tuning.
Nobody had scoped image captioning as a search-relevance feature. It became one because the generated captions happened to contain exactly the kind of descriptive, attribute-rich language that search queries use and that terse product titles never did.
- Compliance-driven features often produce usable byproducts nobody scoped for — worth a deliberate look after shipping, not just a shrug.
- Generated alt text is effectively free structured description data if you're willing to index it elsewhere.
- A feature's measured value can live entirely outside the reason it got funded in the first place.
- Don't assume a checkbox requirement is low-value just because it was framed as a compliance task.
We went back and explicitly tuned the captioning model for search-relevant descriptive detail, on top of its original accessibility job. It now does both, deliberately, but it got there by accident first. Worth remembering next time a 'boring compliance requirement' lands on your desk.