Separate the brand mark from the sales message
A pale wordmark can be recognizable while the pale offer beneath it is difficult to read. When reviewing an AI logo concept on a product banner, do not treat the entire composition as one exempt logo. Identify which text actually forms the mark and which text tells shoppers what they can buy, what it costs or what to do next.
WCAG 2.2 Success Criterion 1.4.3 sets minimum contrast for text and images of text, generally 4.5:1, with 3:1 for qualifying large text. It exempts text that is part of a logo or brand name under that criterion. This is a specific contrast exception, not a declaration that the whole banner, website or interactive control satisfies accessibility requirements.
Classify text by its role
| Element in a fictional launch banner | Role | Review decision |
|---|---|---|
| Approved brand wordmark | Logo identity | Consider the logotype exception within SC1.4.3; still assess practical legibility |
| Two bottles included | Offer information | Evaluate applicable text contrast; proximity to a logo is not an exception |
| Shop the collection | Control label | Review as an action label and assess other applicable control requirements separately |
| Packaging claim inside a product photograph | Context-dependent photographed content | Identify its role before applying a rule; do not assume one universal classification |
Work through the boundary before recoloring
In an invented campaign, a merchant's approved cream-colored wordmark appears over a light photograph. Below it, the same cream color is used for “Two bottles included.” The designer argues that the brand color makes both lines exempt. That reasoning fails: brand styling does not turn ordinary sales information into the brand name.
Keep the actual wordmark and offer text as separate review objects. The designer could retain the identity while placing the offer on an appropriately contrasting panel. Alternatively, the brand owner may approve a more legible version of the mark for that background. These are proposed design choices, not measured contrast results or completed visual tests.
Do not solve the problem by merging every sentence into a single raster logo file. Images of text are within the criterion's scope; the file container does not determine whether the sentence is a brand name. Record the text's purpose and its actual placement rather than using the filename as evidence.
Measure the actual rendered presentation
Inspect text and its immediate background at the delivered size. A logo generator preview and the final responsive banner can differ in scale, crop and background position. Determine whether a large-text exception actually applies instead of assuming that a headline in the design editor remains large on a phone. A photograph may require checking several local backgrounds behind the letters.
The text-over-photography guide addresses that spatial contrast problem. The logo sourcing guide addresses permission and exclusive identity. Neither issue is resolved merely by the logotype exception.
Keep the scope of approval explicit
Record the exact mark, ordinary text, background and layout that were reviewed. If the banner changes, reopen the affected checks. A successful SC1.4.3 assessment does not certify all WCAG criteria, establish legal compliance or prove that every shopper can read the design comfortably. The exception removes one requirement for a defined text role; it does not make unreadable branding a good user experience.
CartVisual can support raster logo-concept exploration. It does not certify accessibility, decide the legal status of a mark or automatically evaluate a complete storefront. Keep final identity and accessibility decisions with the appropriate reviewers.