Decorative images aren’t a thing
In a series of posts dating from Eric Bailey’s June 2021 essay to Nicolas Steenhout’s September 2026 column, a coalition of accessibility experts argues that the notion of a purely decorative picture is obsolete. Bailey’s updated decision tree, now built on the CSS :has() selector, forces authors to ask whether an image would be missed if removed or swapped with something absurd, like a picture of feces. The latest WCAG 3 issue #878, opened on 29 September 2026, formally revises the definition of “decorative” to require explicit justification, echoing the same practical checklist. The push is not merely semantic; it compels designers to replace filler graphics with intentional layout or functional content, and to provide meaningful alt text whenever an image conveys mood, theme, or information.
This debate reflects a broader shift in web and app design toward tighter accessibility compliance and reduced visual clutter. As design systems such as Material Design and Apple’s Human Interface Guidelines tighten their accessibility requirements, the industry is moving away from “fluff” graphics that serve only aesthetic purposes. The emergence of CSS :has() and similar selector capabilities gives developers granular control to detect and label images programmatically, aligning with the WCAG 3 revision cycle that aims to close loopholes exploited by “decorative” exceptions. Simultaneously, design tools like Figma and Adobe XD are adding automated alt‑text suggestions, signaling that the market is responding to these heightened expectations.
If the decorative‑image category is fully retired, teams will need to audit legacy content, replace empty‑alt placeholders, and redesign layouts to avoid empty whitespace. This could increase development effort and raise the risk of over‑describing images, potentially confusing screen‑reader users. However, it also opens opportunities for more purposeful visual storytelling and may reduce legal exposure under accessibility legislation. Watch for adoption metrics from major CMS platforms, updates to WCAG 3 compliance checklists, and any pushback from designers who view the move as an unnecessary constraint.
Key Takeaways
WCAG 3 issue #878 officially challenges the decorative‑image exemption, demanding explicit functional justification for every visual element.
Eric Bailey’s CSS :has()‑based decision tree provides a concrete, code‑level method for evaluating image purpose and alt‑text requirements.
Design systems are beginning to embed automated alt‑text checks, indicating industry‑wide alignment with the new accessibility stance.
Organizations must inventory existing “decorative” assets now to avoid costly retrofits and potential compliance violations later.
About the Source
This analysis is based on reporting by Sidebar. Here is a short excerpt for context:
Adding an image to a design, email, document, page, app, etc. is done for a reason.Read the original at Sidebar
