Hedra AI All articles
Experiments

Alt Text Is Not a Vibe Check: Auditing What Generative Models Say About Their Own Output

Hedra AI
Alt Text Is Not a Vibe Check: Auditing What Generative Models Say About Their Own Output

Photo: InclusiveGameLab, CC BY-SA 4.0, via Wikimedia Commons

The caption is there. That is not the same as accessible.

A generated image lands in a CMS. The alt text field is filled. A generated video has captions. An audio clip has a transcript. On paper, the accessibility checklist is green. Then a screen reader user hears something like: “A woman smiles in a bright office, symbolizing innovation.” The image might actually show a man in a garage holding a broken drone. The caption is not just unhelpful. It is wrong in a way that sounds authoritative.

That is the alt text problem for synthetic media in 2026. The tools can produce language about their outputs. The language is often fluent, plausible, and detached from what the pixels or waveforms actually contain. Accessibility teams are left to decide whether they are reviewing a description or a hallucination.

At Hedra AI, we have been poking at this in our experiments. The goal was not to crown a winner. It was to figure out where model self-description belongs in an accessible publishing pipeline, and where it absolutely does not.

What we tested, and what we refused to pretend

We assembled a small sample: three image generators, two video tools, and one audio generation tool, all current 2026 builds. For each asset, we asked the tool’s own captioning or description feature to describe the output. We did not prompt it with the original generation prompt. We wanted the model to look at its own result, not repeat what it was asked to make.

Then two human reviewers audited each asset with a simple rubric: objects, actions, spatial relationships, visible text, audio events, speaker identity, and uncertainty. We scored whether the model description was accurate, incomplete, or invented. This was not a benchmark. It was a field test with a small sample, and we are not going to turn six tools into a market map.

The pattern was consistent enough to be useful.

The model describes the prompt it remembers, not the frame it produced

The most common failure was prompt echo. Ask an image model to describe its output and it often gives you a polished version of the brief. If the brief said “minimalist kitchen with warm light,” the description says “minimalist kitchen with warm light,” even when the actual image has a floating kettle and a window that opens into a brick wall.

That is not a small error. Alt text is supposed to tell a non-visual user what is in the image, not what the creative director wanted. A screen reader user does not need the mood board. They need to know there is a person, a product, a chart, a dog, or a confusing pile of objects that the page author should probably fix.

Video tools were worse about time. A model might describe the opening frame accurately and miss that the subject walks out of frame at second four, or that the on-screen text changes halfway through. Audio tools were uneven in a different way: they could transcribe speech, but often missed non-speech events like a door slam, a laugh, or music swelling under dialogue. Those events matter for accessibility and for meaning.

A confident description is a product risk

For US teams, this is not just a craft issue. Public-sector accessibility requirements, Section 508, and ADA-related web accessibility work all push organizations toward meaningful alternatives for non-text content. A blank alt attribute is an obvious failure. A wrong alt attribute is a quieter one, and it can be harder to catch because it looks complete.

The practical risk is reputational and legal, but the human cost is simpler: people who rely on assistive technology get misinformation. If a generated chart is described as “showing growth” when the line is flat, that is not a minor caption problem. It is a false statement delivered with assistive confidence.

The workflow we would actually ship

The useful move is to stop treating model self-description as alt text. Treat it as a draft annotation with a job title: suspect, incomplete, and in need of human review.

Here is the workflow we would use in 2026.

  1. Generate and capture provenance. Store the prompt, model, seed if available, and the model’s own description in a separate metadata field. Do not let it auto-fill the public alt text field.

  2. Audit against the asset, not the prompt. A reviewer should look at or listen to the output with the model description hidden. Write the human description first. Then compare. This sounds slow, but it prevents prompt echo from anchoring the review.

  3. Separate description from interpretation. Alt text should say what is visible or audible. If the page needs to explain meaning, put that in surrounding copy or a longer description. “A red bar chart with three bars, the tallest on the right” is accessible. “A chart proving market dominance” is editorial.

  4. Use uncertainty language deliberately. If the model cannot tell whether a blur is a person or a shadow, the human description should say “a blurry figure” or “an indistinct shape,” not invent a profession. For audio, “unclear speech” is better than a confident wrong transcript.

  5. Handle decorative and complex media differently. Decorative generated textures should have empty alt text and stay out of the accessibility tree. Complex generated infographics need a short alt plus a longer text description. Generated video needs captions, audio description where needed, and a transcript that includes meaningful non-speech audio.

  6. Test with a screen reader before publish. Not a browser preview. Not a checklist. An actual screen reader pass on the page, in context. This catches duplicate announcements, alt text that repeats the caption, and descriptions that make no sense when read aloud.

  7. Log revisions. If a generated asset is replaced, the alt text should change with it. Version the description alongside the asset. A stale description is its own accessibility bug.

The product design part is not optional

The tooling matters. If the CMS makes it easy to paste a model caption into the alt field, teams will do it. A better interface separates “model draft” from “approved accessible description,” requires a reviewer name, and blocks publish when a non-decorative generated asset has no human-approved text. It should also support a simple uncertainty flag and a “decorative” toggle that actually removes the asset from the accessibility tree.

That is less exciting than a new model release. It is also the difference between accessible synthetic media and a compliance theater ticket.

The takeaway

Generative models are useful caption starters. They are not reliable witnesses to their own output. In 2026, the responsible workflow is not “ask the model and ship it.” It is “ask the model, hide the answer, have a human audit the asset, write the accessible description, and test the page.”

Alt text is not a vibe check. It is a claim about reality. For synthetic media, someone has to verify that claim before a screen reader reads it aloud.

All Articles

Related Articles

The Half-Inch Problem: Six Image Models vs. the Ground Plane

The Half-Inch Problem: Six Image Models vs. the Ground Plane

The Invoice After the Invoice: What Generated Media Really Costs in Production

The Invoice After the Invoice: What Generated Media Really Costs in Production

The Weights Are Not the Recipe: Reproducing an Open-Weights Generative Media Paper

The Weights Are Not the Recipe: Reproducing an Open-Weights Generative Media Paper