Decorative Images Hidden
Group: images-and-media • Guideline: image-alternatives
Summary in Plain English
Images that are purely decorative are hidden from assistive technology.
Why It Matters
Announcing every decorative image buries the content in noise, and for a screen reader user that noise costs real time on every pass through the page.
Test Procedure from the W3C Draft
Quoted from the provision's informative document, informative/guidelines/images-and-media/image-alternatives/decorative-images-hidden.md. It is the group's own procedure, not an editorial testing guide.
(General) No accessible name
Procedure
- Check for any images that add no information to the content.
- Check that the image has no accessible name.
Expected results
- #2 is true.
(HTML) Using an empty alt attribute for an image element
Procedure
For any image that adds no information to the content:
- Check that
title,aria-label,aria-labelledbyis either absent or empty. - Check that an
altattribute is present and empty.
Expected results
- #1 and #2 are true.
W3C Working Group Status
The draft records no open editors' notes on this provision.
W3C Threads on This Provision
11 GitHub threads carrying 76 comments, fetched from w3c/wcag3 by the tracker. Titles, numbers and states are the threads' own.
What the Argument Is About
Whether WCAG 3's "decorative" has quietly widened WCAG 2's "pure decoration" into a loophole, and whether the fix is a tighter definition, a second tier of decorative images that may carry alt text, or abolishing the exemption entirely.
Positions taken in the thread
The starting point is ericwbailey's framing in #238 that an abled content author deciding what counts as decorative removes agency from the person using assistive technology, with a case he met in the wild (photos of amenities for luxury housing classed as decorative even though they communicate the benefit of living there); ericwbailey himself did not call for abolition, and suggested tempering the point by testing with the intended audience. brett-oppegaard goes further in #369 โ a designer told him a stock photo of a diverse group reading books in front of a university building was decorative and therefore not legally required to be described, and he has heard the same claim made about portrait photos of organizational leaders. His argument is that visual designers always have the option not to include an image, so every included image has a rhetorical purpose; that a screen reader user can skip alt text with a single keypress, so the audience should decide, not millions of decentralized, busy, often untrained site managers; and that the loophole is why Instagram alone emits 70,000 mostly undescribed images a minute. He also wants the term "alt text" retired in favour of static Audio Description, which he argues separately in #371 (see image-alternatives-available). charleshalldesign takes the same line in #878, proposing to retire the concept completely on the grounds that all images convey information, and that an image next to text, in a control or not, supplements the text rather than duplicating it.
TestPartners reports content creators over-compensating with literal descriptions of decorative images running to several sentences and as much as 50 words, which a screen reader user must sit through a large proportion of before concluding it is fluff they did not need; he puts community opinion at roughly 50:50 and says a substantial majority should exist before anything changes. He half-seriously proposed a CSS prefers-reduced-fluff property as the only way to satisfy both camps, and rejects the premise that undescribed decorative images discriminate โ you may as well argue that hanging wallpaper discriminates against people who cannot see it. patrickhlauke's reductio in #238 is that if every non-text piece of information must be conveyed, authors would have to describe colour and sizing choices and ultimately the entire CSS of the page, so a pragmatic and admittedly subjective cut-off is unavoidable; he adds that where a flourish exists to convey a mood, prose carrying the same tone can already be an acceptable alternative. bruce-usab makes the placement argument against Myndex's paisley example: the fact that paisley patterns descend from Jacquard-loom punch cards is compelling trivia that belongs in the footer or on an About page available to everyone, not buried in an alt attribute forced only on screen reader users.
yatil's objection in #369 is that WCAG has said "pure decoration" since 2008 and merely being decorative never qualified for the exception โ WCAG comes from the era of image-rendered container shadows and image-replacement headings, and most genuinely pure decoration can now be done in CSS. He argues the draft's test, whether removing the image would impact how people understand the page, is far too low a bar: under it a portrait in a staff index is decorative and so is a news article photo, and neither "impact" nor "understand" is defined. lauracarlson opened #238 on the narrower charge that "Decorative Images" is broader than "Pure Decoration" and that conflating them is a mistake; her specific target is the Method's "Illustrative of adjacent text but not contributing information (eye-candy)" line, and she proposed renaming "Decorative" to "Purely Decorative" throughout. She calls null alt a hangover from the spacer-gif era; bruce-usab agrees null alt is overused, though he says his own sampling shows missing alt and low-information alt attempted as textual equivalence remain the bigger problems, while allowing this may be sampling bias. In #878 yatil asks the group to stick to WCAG 2's pure decoration definition, since both standards will be used in parallel for years, and says the linked-card examples raised there fall under the Controls, Input exception instead.
MakotoUeki opened #466 proposing an explicit split: purely decorative images (an icon alongside text, a thumbnail inside a link) need no text alternative and should have no accessible name, while decorative images (a photo, an illustration) may usefully carry one as a best practice. The user need he cites is a person who lost their sight later in life and wants the description in order to picture the image, and his position in #238 is that the user, not the author, should decide whether something is meaningless. fstrr points at a ready-made middle category: the HTML spec's ancillary images, where an image is neither purely decorative nor entirely redundant with the text, the alt attribute must be present, its value may be the empty string or a textual representation, and it must not be empty when the image has a caption.
grace-snow's reply in #466 is that if an image adds meaning it is not decorative at all, so naming a class of "decorative" images that do need alternative text is highly likely to confuse; whether a photo or illustration is decorative depends on the surrounding content and context, not on the image type. Finnberrys agrees and offers the substitution test she applies: a swirly line at the bottom of a page could be swapped for a wiggly rainbow line with no effect on content, whereas a photo of her dog on a page about assistance dogs could not be swapped for a unicorn without becoming confusing and weird. sydneycolemanfromgoogle filed the same objection independently in #518 โ the distinction is not useful without a clear and mostly objective means of telling the two apart.
mraccess77 reports that Internet Explorer's exposure of alt as a tooltip let him learn things about images he could not distinguish visually โ essentially audio description for the web, the nuances low-vision users miss โ and notes that captions today are available to everyone rather than only to deaf users, while accessible name and description are not. Myndex makes the adoption argument: alt text is effectively unreachable outside screen reader use, and if it surfaced through a standard user-agent affordance it would serve people with prosopagnosia or other cognitive and contextual needs, reader mode, and failed image loads, and the broader demand would drive adoption. bruce-usab counters from history that IE's tooltip behaviour is precisely what trained authors to write tooltips into alt for years, that the TITLE attribute only partly separated them, and that the practice only corrected when touch UIs removed the tooltip, though after mraccess77's reply he allowed he was probably overstating the harm and that some human-written alt is almost always better than none. Myndex also flags that CSS background images accept no alt text at all, which he treats as a missing platform property rather than an author failing.
#878, opened by alastc on 2026-09-29 after vavroom's article on retiring decorative images, is where the definition argument now runs. alastc floated redefining it as not contributing to the information, functionality, meaning, mood or context, then asked whether not relied on would be better after patrickhlauke noted that mood can also be carried by the tone of the text. lauracarlson revived her purely decorative proposal, with a definition excluding anything that provides meaning, context, mood or user understanding, and with alastc reframed generic card images and linked thumbnails as duplicative rather than decorative. MakotoUeki, facilitating the subgroup, said it will not stick to WCAG 2's definitions and wants to gather concrete examples. On verbosity, alastc reports screen reader users split between wanting descriptions and wanting to get on with the task; patrickhlauke warns that requiring alternatives for most images will produce LLM-generated descriptions and distinguishes an alternative from an on-demand description; mraccess77 argues that alt on every image without importance metadata, such as an aria-important attribute, would leave users no way to control verbosity, and cites invisible email tracking images as genuinely ignorable. LJWatson and vavroom answer that content that is present can be skipped while absent content cannot.
Agreed
- Null alt is overused and "decorative" gets stretched to cover images that inform โ bruce-usab and MakotoUeki both concede this to lauracarlson, though TestPartners, and in #878 alastc and mraccess77, warn about the verbosity cost of describing more images.
- Several participants treat applying the exemption as subjective: TestPartners says there is no right answer and patrickhlauke describes a pragmatic, subjective cut-off. jake-abma's example is the WCAG 2.1 CSS-fitting-images working example, which shipped with alt="" and which he says mraccess77 wanted described during sanity-checking; jake-abma's conclusion was that a judgement call may not be the best approach and that it comes down to the user.
- The overlap with Images detectable that scottaohara raised via #357 โ how can an image be hidden and detectable at once, and where do CSS background images land โ was resolved editorially; scottaohara accepted the reworked text in the Jan 5 draft preview and adampage closed the issue on 2026-04-01.
Still open
- Whether "decorative" should be one category or two. MakotoUeki (#466) wants the split; grace-snow, Finnberrys and sydneycolemanfromgoogle want one term defined well. adampage marked sydneycolemanfromgoogle's #518 as a duplicate of #466 rather than answering it (the issue is still open), and the question is now argued mainly in #878, where lauracarlson and MakotoUeki back purely decorative, vavroom is undecided on wording, charleshalldesign wants no category at all, and yatil wants WCAG 2's pure decoration kept.
- Whether the exemption should exist at all. brett-oppegaard's #369 poses it as five direct questions โ what the exemption is for and whether WCAG serves designers or the audience, how blind people can be included in societal discussions if excluded from these elements, what the downside of removing it is, and whether the old page-loading rationale still applies, plus a demand that, if kept, WCAG define "decorative" in a legal sense โ and none has been answered on the record.
- Whether the author or the user decides an image is meaningless. ericwbailey, MakotoUeki and jake-abma all land on the user, as do LJWatson and vavroom in #878. Mechanisms have been floated but not pursued: TestPartners' prefers-reduced-fluff property, mraccess77's importance metadata, and patrickhlauke's and yatil's on-demand generic descriptions carried with the image.
- What research supports widening "pure decoration" to "decorative". lauracarlson asked for the data in January 2022 and again in her follow-up; jake-abma's answer was that data is not always available and the judgement is inherently subjective. In #878 lauracarlson cited TetraLogical research on images as cognitive anchors for neurodivergent users and user testing summarized by David MacDonald; no other study has been cited.
- Whether CSS background images can carry alternatives at all โ Myndex raised it in #238 and it is the same hole scottaohara found from the Images detectable side in #357.
- Whether authors should be describing emotionally rich images and, if so, how. lauracarlson pointed at Lรฉonie Watson's and Jake Archibald's writing on emotion in text descriptions; #238 did not take it up, though LJWatson pointed to the same writing in #878.
- Whether yatil's asymmetry argument holds: information that is present can be skipped by the user, information that was never provided cannot be recovered. LJWatson and vavroom make the same point in #878; mraccess77 counters that without metadata the user has no way to know what to skip.
- Whether the drafted test procedure gets fixed. grace-snow (#573) shows it is written only for img, ignores svg and role="img", omits that role="img" must be absent from a decorative image, and omits aria-hidden="true" as a technique; JasonAment (#607) shows the first procedure's help text duplicates a condition of the second; janBeniaminKwiek (#614) asks that "add no information to the content" become "add no information or functionality". None of these has drawn a reply.
- The self-contradiction WilcoFiers raises in #495 is unanswered: if content is what is communicated to the user and a decorative image is by definition not that, then a decorative image cannot have programmatically determinable properties and therefore cannot be programmatically hidden. He recommends reverting to WCAG 2.0's definition of programmatically determined, which lacks the word "important".
- Whether programmatically hidden is the right term at all: mcking65 (#884) says it is generally understood to mean hidden from every user, as with display:none or the hidden attribute, and proposes WCAG 2.2-style wording such as ignored by, or hidden from, assistive technology. MakotoUeki replied that the subgroup will address it when its review begins, as early as the first half of next year.
Note
This provision's history runs in disconnected phases. #238 was argued out in January 2022, bruce-usab took the concrete fix to EOWG as a pull request against the WAI tutorial (wai-tutorials#635), it was considered and declined, and he asked lauracarlson to close; she declined in September 2022 on the grounds that the full AG Working Group should consider it and that WCAG 3 should not inherit the tutorial's examples. The issue then sat untouched for three years until brett-oppegaard revived the argument in September 2025. Several of the more consequential recent filings โ #495, #573, #607, #614 โ are single unanswered comments, so the quality of the current draft text has had far less scrutiny than the definition has. The definition argument restarted in #878, opened by alastc on 2026-09-29, which drew 34 comments in five days and is unresolved; #884 (mcking65, 2026-10-02) separately challenges the term programmatically hidden. Note also that brett-oppegaard participates by email, so his comments arrive with quoted reply chains attached.
- #238 Method: "Decorative Images" Section of the WCAG 3 vs WCAG 2.x "Pure Decoration" open 26 comments · updated 2026-04-01
- #272 Requirements: Image alternatives open 2 comments · updated 2026-04-02
- #357 Detectable Image and CSS background images closed 2 comments · updated 2026-04-01
- #369 Decoration is still information, of course ... Guideline 2.1.1 Image alternatives open 9 comments · updated 2026-04-01
- #466 "purely decorative" vs "decorative" - Decorative images (Foundational) open 2 comments · updated 2026-04-08
- #495 Decorative image requirement has self-contradicting definition open 0 comments · updated 2026-03-29
- #573 Decorative images may be discoverable but still pass Tests - Decorative images (Foundational) open 0 comments · updated 2026-03-27
- #607 2.1.1 - Decorative images hidden - Test procedure update. open 0 comments · updated 2026-03-27
- #614 Clarify that decorative images must add no information or functionality open 0 comments · updated 2026-03-27
- #878 Definition of decorative images update open 34 comments · updated 2026-10-03
- #884 Decorative images should NOT be "programmatically hidden" open 1 comment · updated 2026-10-03
WCAG 2.2 Criteria That Map Here
From this site's reviewed WCAG 2.2 → WCAG 3 map. The map is an interpretation, not a W3C mapping: W3C has not published one yet.
W3C Raw Source Text
Verbatim from guidelines/groups/images-and-media/image-alternatives/decorative-images-hidden.md · informative document: informative/guidelines/images-and-media/image-alternatives/decorative-images-hidden.md
Decorative images are programmatically hidden.