Why is a filename not an image description?
Import, migration, or automated content flows can leave a filename or technical address in the alt field. A value such as “DSC_2048.jpg” identifies the file rather than communicating the information a person should receive about the photograph.
The detector looks for values that resemble filenames or image addresses. W3C guidance makes clear that a filename does not replace a semantic alternative for an informative image; the visual content remains the basis for a useful description.
Examples showing why image context matters
These fictional examples illustrate the difference between an alt value that matches a detectable pattern and a description that communicates information about the image. Final wording always depends on the real image and its role on the page.
Alt: “IMG_4821.jpg”Alt: “White sports shoe, side view”The filename is replaced with a description only when the image actually confirms the object and perspective in the example.
Alt: “https://cdn.../mug-front.png”Alt: “White mug, front view”The technical address does not describe the content; the example shows the kind of information a descriptive alternative can communicate.
Alt: “DSC0007.jpeg”, image unavailable[the image needs review]The detector can flag a filename-like pattern without inventing what the file shows.
What does PROVEN check?
Checks alternative descriptions that resemble a file name or the image address.
Why does it matter?
Such a value describes the technical source rather than the image content.
Why is this useful to a merchant?
The finding is useful in catalogs managed through imports or multiple systems, where technical values can accidentally reach customer-facing fields.
The merchant can quickly separate cases that need a real description from decorative images or cases where the available context is insufficient for a safe rewrite.
What can PROVEN do?
PROVEN can flag the value and prepare a descriptive proposal; the final text requires your review.
How PROVEN handles this check
PROVEN detects the technical shape of the value and keeps image semantics for review.
- Detect the filename or URL patternPROVEN checks whether the alternative description resembles a filename or the image address.
- Connect the finding to affected mediaThe finding shows the product, image, and technical value so the origin of the issue can be reviewed.
- Prepare descriptive wording for reviewPROVEN can prepare a descriptive proposal, but the final content is confirmed by the merchant against the real image.
Why is your review required?
A file extension or URL shape can be detected from text, but what should be described cannot be safely inferred from the filename. “blue-shoe-front.jpg” may provide a hint, not sufficient evidence for publication.
Review should avoid turning a filename into a cosmetically rewritten sentence. The alternative text must be justified by the real image and context.
What this page does not tell you
- The existence of this detector does not mean your store contains this problem; the catalog state must be established by checking real data.
- Examples on this page are fictional explanations. They are not measurements from a store and do not promise a particular remediation.
- The criteria for this check support review and triage. They should not be reinterpreted as a universal requirement imposed by Shopify, Google, or W3C.
- This check does not claim that every string containing a dot or slash is wrong and does not treat a filename as sufficient evidence to invent visual description.
- Decorative, informative, and functional images can require different treatment; a catalog detector cannot decide the final role of an image in a specific theme by itself.
Frequently asked questions
Why is “IMG_1234.jpg” weak alt text?
The value identifies the file rather than the visual information. For an informative image, the alternative should communicate relevant meaning or content.
Can PROVEN use the filename to generate the description?
A filename can provide technical context but is not sufficient evidence about the image. Final wording still needs visual review.
What if the image is decorative?
W3C explains that decorative images can use a null alternative. A catalog detector cannot decide the final image role in a theme by itself.
Does the detector also find URLs in the alt field?
The check covers values that resemble a filename or image address and shows the value for review.
Sources about alternative text and image context
These sources provide independent context about alt text and why the appropriate text depends on the image purpose. They do not define PROVEN technical detection details or turn a finding into an automatic verdict.
- Shopify — Adding alt text to mediaShopify explains the role of alt text for product media, accessibility, and SEO and recommends brief, descriptive wording.
- W3C WAI — Images TutorialW3C explains that text alternatives depend on the information or function represented by an image and distinguishes informative, functional, and decorative images.
- W3C WAI — Informative ImagesW3C explains that informative-image alternatives should convey relevant meaning or information rather than a generic label.