The Common Dilemma
You're conducting a WCAG 2.2 audit, and your developer asks if the homepage hero image needs alt text. Your QA lead calls it "just branding," while your remediation vendor marks it decorative and moves on. These questions arise in every accessibility review. Teams often treat the decorative image label as an easy out. WCAG allows some images to be hidden from screen readers if they're decorative, but this is overused, leading to gaps in the user experience.
Here's what you and your team need to know.
What Counts as Decorative Under WCAG?
WCAG defines decorative images as those that don't add necessary information to understand the content. A flourish or border pattern is a classic example. However, teams often interpret "doesn't add information" too narrowly. An image might not convey specific facts but still influence how a user perceives the page's purpose, tone, or trustworthiness.
For instance, a homepage image showing a diverse team collaborating signals company culture and values. If you mark it decorative and hide it from screen readers, sighted users get context and emotional framing, while screen reader users do not. The standard allows you to hide these images only if they truly add nothing. Most teams skip this crucial evaluation.
Should We Write Alt Text for All Product Photos?
Not necessarily, but you need a better framework than "it's just a photo." Consider these questions:
- Does the image help users decide whether to engage with the content?
- Does it establish context affecting how the surrounding text is interpreted?
- Would a screen reader user miss something meaningful if unaware of the image?
Product photos on a catalog page with text descriptions might be redundant. However, a hero image on your accessibility statement page showing someone using assistive technology is not decorative; it establishes credibility and signals the page's audience.
Your conformance testing should document the rationale, not just the aria-hidden attribute. When your Accessibility Conformance Report lists numerous decorative images, auditors and attorneys will ask why. "We followed WCAG" isn't enough without explaining each decision.
How to Classify Images That "Set the Mood"
Mood, tone, and emotional context are information. They affect comprehension and user confidence. Write concise alt text describing the image's function, not every visual detail. "Team collaborating in modern office" is more informative than a decorative label.
If you can't articulate what the image contributes in one sentence, that's a design issue. Either the image isn't earning its bandwidth, or you haven't defined its purpose. Both are fixable.
Compliance Risks of Overusing Decorative Labels
Overusing decorative labels creates a paper trail showing accessibility decisions made without considering user impact. ADA Title III litigation often hinges on whether your program demonstrates good faith. If your documentation shows you marked 80% of images decorative without analysis, you're documenting mechanical labeling rather than evaluating each image's role.
The DOJ Final Rule (2024) doesn't credit you for technically conforming to WCAG if it results in a degraded experience for users with disabilities. If your screen reader experience omits context that sighted users rely on, you've created a separate and unequal experience.
Updating Your Image Accessibility Workflow
Start with your governance documentation. If it says "mark as decorative if the image doesn't convey unique information," rewrite it. New standard: "Mark as decorative only if removing the image wouldn't change a user's understanding of the page's purpose, tone, or content. Document the rationale."
Include alt text review in your content approval workflow. Your content strategist should ask "what does this image accomplish?" before it goes into the CMS. If the answer is "it looks nice," either write alt text that captures what "nice" means in context or reconsider the image's necessity.
Update your Voluntary Product Accessibility Template process to include image classification methodology. When evaluating third-party tools, ask vendors how they determine which images are decorative. If they can't explain their framework, that's a red flag.
Handling Decorative Icons in UI Components
Icons with adjacent text labels are usually suitable for decorative treatment. If a trash can icon is next to "Delete," the icon is redundant. But ensure the text label is present and properly associated. I've seen teams mark icons decorative because "the button says delete," then remove the text label for mobile layouts, resulting in an unlabeled button.
Use aria-hidden="true" on the icon and ensure the button or link has accessible text through aria-label, aria-labelledby, or visible text content. Test with screen reader software, not just automated tools. Functional icons without text labels are never decorative; they're either properly labeled interactive elements or WCAG failures.
Next Steps
Review the W3C's Images Tutorial for a detailed decision tree on image types. It's more nuanced than most teams realize.
If you're building an Accessibility Conformance Report, document your image classification methodology in the conformance claims section. Explain how you distinguish decorative from informative and what review process you used.
Your next accessibility governance review should include an image audit. Pull a sample of pages, list every image marked decorative, and ask your content team to justify each one. If they can't, you've found your remediation backlog.
The decorative label exists for a reason, but it's been used as an excuse to avoid hard decisions about what images contribute to user experience. Stop hiding behind the standard and start asking what your users need to know.
