Images, video, colour and motion: making every picture, sound and animation work for everyone

TL;DR

Difficulty: Intermediate

Every piece of media needs a second way in for the customer who cannot use the first.

  • Images: alt text says what the image is for; decorative images get an empty alt; text stays real text (WCAG 1.1.1, 1.4.5).
  • Video: edited captions (1.2.2, live 1.2.4), a transcript, and audio description where the picture says something on its own (1.2.5).
  • Colour: 4.5:1 for text, 3:1 for large text and controls (1.4.3, 1.4.11), and never colour alone (1.4.1).
  • Motion: a pause button for anything that moves on its own for more than five seconds (2.2.2), never more than three flashes a second (2.3.1), and respect the reduce motion setting.

Pictures, video, colour and movement make a shop feel alive, and each of them can quietly shut a customer out. This chapter takes them one at a time, with the WCAG criteria behind each rule and a worked example from an invented Brighton bookshop, so you can fix your own homepage in an afternoon.

The question: can every customer see, hear and sit through your pages?

Most of what makes a shop feel alive is visual. A cover photo that sells the book before anyone reads the blurb. A sale banner. A carousel of new releases. A short video of an author talking about her novel. A colour palette that looks like the brand. A little animation when something lands in the basket.

Each of them can shut a customer out without anyone noticing, usually because the person who built the page could see, hear and watch it without trouble. This chapter takes the four kinds of media on almost every site, pictures, video, colour and motion, one at a time.

The yardstick is the Web Content Accessibility Guidelines (WCAG) 2.1 at level AA, the standard the European accessibility rules point to1. WCAG 2.2 keeps every criterion in this chapter with the same number and level, so nothing here changes if you aim for 2.2. If WCAG itself is new to you, read WCAG 2.1 AA explained first. If you wonder why a plugin cannot do this for you, that is chapter one of this series. Charts get their own article, accessible charts, colour contrast and screen readers, so I only touch them here.

Meet the shop and four of its customers

The example in this series is made up. Brightwater Books is an independent bookshop in Brighton with an online shop at brightwaterbooks.example. Ruth owns it. Ade is the developer who looks after the site. In this chapter Ade works through the homepage, the product pages and one video.

Four customers, also invented, help us test every idea:

  • Priya is blind and uses a screen reader, software that reads the page aloud and lets her move through it by headings, links and images.
  • Tom is deaf. He watches video with captions on, always.
  • Malcolm has low vision. He zooms the browser to 200% and finds faint grey text hard to read.
  • Helen has a vestibular disorder, a condition of the inner ear and balance system. Movement on a screen, such as parallax scrolling or sliding panels, can leave her dizzy and nauseous for hours.

Example: how common these failures are

Most sites do not get this right yet. Every year WebAIM, a non profit at Utah State University, runs an automated check over the home pages of the top one million websites. The February 2026 run found low contrast text on 83.9% of those home pages and images without alternative text on 53.1%2. Those were the two most common failures of all, ahead of missing form labels, empty links, empty buttons and missing page language.

Bar chart of the share of the top one million home pages with each detected failure in the WebAIM Million report, February 2026: low contrast text 83.9%, missing alternative text for images 53.1%, missing form input labels 51%, empty links 46.3%, empty buttons 30.6%, missing document language 13.5%. The two failures this chapter covers, contrast and alternative text, are the two most common. Tap or click to open full screen and move around

Automated tools see only part of the picture, as chapter five on testing explains, so the real figures are worse. The good news: the two most common failures are also two of the easiest to fix.

Alt text says what the picture is for, not what it looks like

A screen reader cannot see an image. It reads out the image's text alternative, the alt attribute in HTML. WCAG success criterion 1.1.1, Non text Content, at level A, asks that every image that carries information has a text alternative that serves the same purpose, and that purely decorative images are marked so that assistive technology can ignore them3.

The words that matter are "the same purpose". Alt text is not a caption and not a description for its own sake. It answers one question: if this image vanished, what would the customer miss?

The W3C, the body behind WCAG, publishes a short decision tree for exactly this question4. In plain terms:

  • If the image sits inside a link or a button, the alt text says where the link goes or what the button does.
  • If the image adds meaning that is not already in the text around it, the alt text gives that meaning, briefly.
  • If the image is a chart or another complex graphic, a short alt text names it and the full information sits in text nearby.
  • If the image only decorates, or repeats what the text next to it already says, it gets an empty alt attribute, alt="".

That last point surprises people. An empty alt is not a mistake. It tells the screen reader to skip the image. Leaving the attribute out altogether is the mistake, because some screen readers then read the file name instead5. Priya does not want to hear "IMG underscore 4471 dot JPEG".

Tap or click to open full screen and move around

Example: three images on one product card

On the Brightwater Books listing page, each book sits on a small card. Ade opens the card for an invented novel, The Glasshouse Year by Hannah Keel, and finds three images.

  1. The cover photo. The whole card is a link to the book's page, and the title and author are already written as text inside that link.
  2. A small leaf graphic in the corner, part of the autumn theme.
  3. A heart icon button that adds the book to a wish list. It has no visible text.

Here is what Ade found, with what Priya heard:

<!-- Before -->
<a href="/books/the-glasshouse-year">
  <img src="glasshouse-year-cover.jpg">
  <h3>The Glasshouse Year</h3>
  <p>Hannah Keel</p>
</a>
<img src="leaf.svg">
<button><img src="heart.svg"></button>

Priya heard the file name of the cover, then the title and the author, then "leaf dot svg", then "button" with nothing after it. She had no way to know what the heart button does.

Ade walks each image through the decision tree.

  1. The cover is inside a link, but the link already has text: the title and the author. The image adds nothing the text does not say, so it gets alt="". Priya now hears the link once, as "The Glasshouse Year, Hannah Keel".
  2. The leaf is pure decoration, so it also gets alt="".
  3. The heart is the only content of a button. Without it, the button means nothing. So its alt text says what the button does, not what the icon looks like: "Add The Glasshouse Year to your wish list". "Heart" would be accurate and useless.
<!-- After -->
<a href="/books/the-glasshouse-year">
  <img src="glasshouse-year-cover.jpg" alt="">
  <h3>The Glasshouse Year</h3>
  <p>Hannah Keel</p>
</a>
<img src="leaf.svg" alt="">
<button type="button">
  <img src="heart.svg" alt="Add The Glasshouse Year to your wish list">
</button>

type="button" tells the browser this button does not submit a form. The alt texts are written in the shop's own voice, short and specific. The site runs on Rails, so Ade makes the same change once in the shared card partial, and every card on the site follows:

<%# app/views/books/_card.html.erb %>
<%= link_to book_path(book) do %>
  <%= image_tag book.cover_url, alt: "" %>
  <h3><%= book.title %></h3>
  <p><%= book.author_name %></p>
<% end %>
<button type="button">
  <%= image_tag "heart.svg", alt: "Add #{book.title} to your wish list" %>
</button>

Product photos: describe what the customer needs to decide

On the book's own page, the images do a different job. Here they are the product. A sighted customer looks at the cover, flips to the back, and glances at a sample spread of illustrations before deciding. The alt text has to give Priya the same basis for her decision.

Good product alt text answers what a shop assistant would say if asked "what does it look like?". It names what matters for buying, does not repeat the title the heading already gives, and does not begin with "image of", because the screen reader already announces an image.

The page for The Glasshouse Year shows four images. Ade writes alt text for each one by asking what Priya would need to choose this book, or this edition, over another.

  1. Front cover: alt="Hardback cover: a glasshouse at dusk with a single lit lamp, title in gold foil". The binding and the foil matter to someone buying a gift.
  2. Back cover: the back is mostly the blurb and two review quotes. That text is already on the page as real text, so repeating it in the alt would make Priya hear it twice. Ade writes alt="Back cover, with the blurb and reviews shown in full below" and makes sure that is true.
  3. A sample spread: alt="Inside pages: full colour botanical illustrations facing each chapter opening". The illustrations are a reason to buy this edition, so they go into words.
  4. A photo of the book on a café table with a cup of tea. It sets a mood and adds no information. alt="".

Priya now learns everything a sighted customer learns from the gallery, in four short sentences, and nothing twice.

Text belongs in text, not in pictures

A picture of words is a trap. A screen reader cannot read it unless the alt text repeats it. Malcolm cannot enlarge it cleanly, because a zoomed image blurs. Nobody can change its colours with a high contrast setting. WCAG success criterion 1.4.5, Images of Text, at level AA, says that if the technology can show the text as real text, use real text, except where a particular look is essential, such as a logo6.

Example: the autumn sale banner

The homepage banner at Brightwater Books was a single JPEG made in a design tool. It reads "Autumn sale. 20% off all fiction until 30 November" in white letters on a photo of a beach at sunset. Its alt text was "banner".

Priya heard "banner" and never learnt there was a sale. Malcolm zoomed in and the letters went soft at the edges. Ade rebuilt it:

<section class="hero">
  <img src="beach-sunset.jpg" alt="">
  <div class="hero-text">
    <h2>Autumn sale</h2>
    <p>20% off all fiction until 30 November.</p>
    <a href="/sale">Browse the fiction sale</a>
  </div>
</section>

The photo is now decoration, so alt="". The offer is a real heading, a real paragraph and a real link with a descriptive name. The text sits on a dark panel inside the banner, so its contrast no longer depends on which part of the sunset happens to be behind it. The contrast section comes back to that number.

One more thing: when the sale ends, Ruth edits a sentence, not a picture.

Captions and transcripts: video that works without sound

Captions are the spoken words and the important sounds of a video, shown as text in sync with the picture. They serve people who are deaf or hard of hearing, and anyone watching on a train with the sound off. Hearing loss is common: the World Health Organization puts the number of people worldwide who need rehabilitation for disabling hearing loss at over 430 million, more than 5% of the world's population7.

WCAG sets out several levels for video with sound:

  • Captions for prerecorded video, criterion 1.2.2, level A8.
  • Captions for live video, criterion 1.2.4, level AA9. A live stream of a book launch needs captions too.
  • Audio only content, such as a podcast, needs a transcript under criterion 1.2.1, level A1.

Automatic captions, the kind a video platform generates on its own, are a starting point and nothing more. The W3C says plainly that automatically generated captions do not meet user needs or accessibility requirements unless someone has confirmed they are fully accurate, and that they usually need significant editing10. Check names and book titles first, because speech recognition has no way of knowing them.

A transcript is the whole thing in text: the speech, the important sounds and, in a descriptive transcript, what you see. It serves people who prefer to read, and a descriptive transcript is the only way a person who is both deaf and blind can get the content of a video at all, through a braille display11.

Example: the author interview

Ruth recorded a twelve minute interview with Hannah Keel in the shop and put it on the book page. The video started playing on its own, with sound, and had platform captions that turned "Hannah Keel" into "Hannah keel boat" twice.

Ade's fix, step by step:

  1. He downloads the automatic captions as a WebVTT file, the plain text caption format browsers read, and corrects every line against the recording. That takes him about an hour. He adds the sounds that matter, such as [laughter] and [shop bell rings], and names the speaker when it changes.
  2. He removes autoplay. More on why below.
  3. He serves the video with the corrected captions attached:
<figure>
  <video controls preload="metadata" poster="interview-poster.jpg">
    <source src="hannah-keel-interview.mp4" type="video/mp4">
    <track kind="captions" src="hannah-keel-interview.en.vtt"
           srclang="en" label="English captions" default>
  </video>
  <figcaption>
    Hannah Keel on writing The Glasshouse Year, recorded at Brightwater Books.
    <a href="/interviews/hannah-keel/transcript">Read the full transcript</a>
  </figcaption>
</figure>

controls gives every customer the browser's own play, pause, volume and captions buttons, which work with a keyboard and a screen reader. <track kind="captions"> attaches the caption file. srclang names its language, label is what the captions menu shows, and default switches them on unless the customer turns them off12. preload="metadata" loads only the length and first frame, not the whole film. The figcaption says what the video is and links to the transcript.

  1. He publishes the transcript as a normal page, built from the corrected caption file with the visual details added in.

Tom now gets every word and every laugh. Priya can read the whole interview at her own speed.

Audio description: say out loud what only the eye can see

Captions turn sound into text. Audio description does the opposite: it turns the important visual information into speech, for people who cannot see the picture. WCAG criterion 1.2.3, at level A, asks for either audio description or a full text alternative for prerecorded video. Criterion 1.2.5, Audio Description (Prerecorded), at level AA, asks for audio description itself13.

That sounds expensive. Often it is not, because the simplest form of description costs nothing at all. The W3C calls it integrated description: the people on screen simply say what matters as part of the script14. "Here is the first draft, covered in green ink" is description. "Look at this" is not.

Example: describing the interview without a second soundtrack

Ade and Ruth watch the interview with the screen turned away and note every moment where something important happens only on screen.

  1. Minute two: Hannah holds up her first notebook and smiles. Nothing is said. Priya would miss it.
  2. Minute seven: a slide shows the three illustrations that inspired the cover.
  3. Everything else is two people talking in a bookshop, which the conversation already makes clear.

For this video, Ade adds the two moments to the transcript and records a short spoken line for each, placed in natural pauses, as a described version offered next to the player. For the next interview, Ruth plans the script so that guests say what they show ("this is my first notebook, every page in pencil"). Priya now hears what the notebook is and what the illustrations show.

Contrast: 4.5:1 for text, 3:1 for large text and controls

Contrast is the difference in brightness between text and its background. WCAG measures it as a ratio from 1:1 (no difference) to 21:1 (black on white). The rules are short:

  • Normal text needs at least 4.5:1, criterion 1.4.3, level AA15.
  • Large text needs at least 3:1. Large means at least 18 point, or 14 point bold, which on screen is roughly 24 pixels, or about 18.7 pixels in bold15.
  • The parts of the interface you need to see to use it, such as the border of an input box, a checkbox, or the focus outline that shows where you are, need at least 3:1 against what sits next to them, criterion 1.4.11, Non text Contrast, level AA16.

Any contrast checker gives you the number from two colour codes. The formula is worked through once in the charts article. Read the result strictly: 4.49:1 is a fail for normal text, not "nearly".

Example: the brand colour on buttons and prices

Brightwater's brand colour is a warm marigold, #f0a04b. Ade checks the places where it meets text.

  1. "Add to basket" button, white text on marigold. Ratio 2.14:1. Fails 1.4.3 for normal text, and even fails the 3:1 for large text. Malcolm sees a yellow blob with a pale shimmer in it.
  2. Price and author name, light grey #999999 on white. Ratio 2.85:1. Fails.
  3. Search box border, #dddddd on white. Ratio 1.36:1. Fails 1.4.11, so Malcolm cannot see where the search box is.
  4. The new banner heading, "Autumn sale", 32 pixels bold, white on the dark panel #1f2937. Ratio 14.68:1. Passes easily.

Ade's fixes keep the brand and change only what fails:

:root {
  --brand-marigold: #f0a04b;   /* decoration, borders, illustrations */
  --button-bg: #b45309;        /* deeper amber: white text 5.02:1 */
  --text-muted: #595959;       /* prices and author names: 7.0:1 on white */
  --field-border: #8a8a8a;     /* input borders: 3.45:1 on white */
}

The marigold stays as the brand colour for illustrations and decorative edges, where no text sits on it. Buttons move to a deeper amber that still reads as the same family, and white text on it reaches 5.02:1. Grey text moves from #999999 to #595959, which gives 7.0:1. The search border moves to #8a8a8a at 3.45:1. Malcolm now sees every price, every button and the search box, and Ruth's site still looks like Ruth's site.

Ade also checks the same tokens in dark mode, because a pair that passes on white can fail on near black. The charts article walks through that check in full.

Colour is never the only signal

Some customers cannot tell certain colours apart, and a screen reader does not announce colour at all. WCAG criterion 1.4.1, Use of Color, at level A, says colour must not be the only way information is shown, an action is indicated or an element is told apart17. Colour can be one signal. It must not be the only one.

The two places this fails most on a shop are status markers and links. A green dot for "in stock" and a red dot for "out of stock" mean nothing to someone who sees both as the same muddy brown, and nothing at all to a screen reader. Links that differ from the text around them only by colour disappear for the same customers.

Ade finds both on the book page.

  1. Next to the price, a 10 pixel dot shows stock: green, amber or red. There is no text. Ade replaces it with words and keeps the colour as a second signal:
<!-- Before -->
<span class="dot dot-green"></span>

<!-- After -->
<p class="stock stock-in">
  <img src="tick.svg" alt="" class="icon">
  In stock, ready to post today
</p>
<p class="stock stock-low">
  <img src="clock.svg" alt="" class="icon">
  Only 2 left
</p>

The icon gets an empty alt, because the words next to it already say everything. Priya now hears "In stock, ready to post today". Customers who cannot tell green from red read the same words.

  1. In the book description, links to other titles are marigold text with no underline. Ade adds the underline back with text-decoration: underline, so the link is recognisable by its shape, not only its colour.

Motion that starts on its own needs a pause button

Movement grabs attention, which is why shops love carousels, and why it can make a page unusable. Some people cannot read while something moves nearby, and screen readers lose track when content changes under them.

WCAG criterion 2.2.2, Pause, Stop, Hide, at level A, sets a clear rule. Anything that moves, blinks or scrolls, starts automatically, lasts more than five seconds and sits alongside other content needs a way for the customer to pause, stop or hide it. Content that updates on its own, such as a ticker, needs the same18. Five seconds was chosen because it is long enough to catch attention and short enough to wait out18.

Sound has its own rule. Criterion 1.4.2, Audio Control, at level A, says that if audio plays automatically for more than three seconds, the customer must be able to pause or stop it, or turn it down separately from the system volume19. Autoplaying sound also talks over a screen reader, which is why Priya dreads it.

Tap or click to open full screen and move around

The W3C's carousel tutorial gives the practical pattern: a visible button to stop and start the rotation, and the rotation pauses whenever the mouse is over the carousel or keyboard focus is inside it20.

The Brightwater homepage has a carousel of five new releases. It slides every four seconds, forever, with no control. Helen feels sick within a few rotations. Priya's screen reader starts reading one slide and finds itself on another.

Ade's first question is whether it should move at all. A row of five covers that the customer scrolls through by hand does the same job with no motion. Ruth wants the movement, so Ade keeps it and makes it controllable:

  1. A real button, first in the carousel, that stops and starts the rotation. Its text changes with its state, so Priya always hears what pressing it will do.
  2. The rotation pauses on mouse hover and whenever focus is inside the carousel, so a keyboard customer never has a slide pulled away mid read.
  3. The rotation does not start at all if the customer's system asks for reduced motion (the next section).
  4. Each slide is a list item with a real heading and link, so the content is readable even when nothing moves.
<section class="carousel" aria-label="New releases">
  <button type="button" class="carousel-toggle">
    Pause the slides
  </button>
  <ul class="slides">
    <li><h3><a href="/books/the-glasshouse-year">The Glasshouse Year</a></h3></li>
    <!-- four more slides -->
  </ul>
</section>
const carousel = document.querySelector('.carousel')
const toggle = carousel.querySelector('.carousel-toggle')
const reduce = window.matchMedia('(prefers-reduced-motion: reduce)')
let timer = null
let stoppedByUser = reduce.matches

function start() { if (!timer && !stoppedByUser) timer = setInterval(nextSlide, 6000) }
function stop() { clearInterval(timer); timer = null }
function render() {
  toggle.textContent = stoppedByUser ? 'Play the slides' : 'Pause the slides'
}

toggle.addEventListener('click', () => {
  stoppedByUser = !stoppedByUser
  render()
  stoppedByUser ? stop() : start()
})
carousel.addEventListener('mouseenter', stop)
carousel.addEventListener('mouseleave', start)
carousel.addEventListener('focusin', stop)
carousel.addEventListener('focusout', start)
render()
start()

aria-label="New releases" gives the section a name screen readers announce. The script only changes the text of the existing button, never replaces the button, so keyboard focus stays where it was, as the W3C tutorial advises20. Ade also slows the rotation to six seconds, so even someone who never touches the button has time to read a slide.

Flashing: three flashes a second is the limit

Flashing is different from other motion, because it can cause harm, not just discomfort. For people with photosensitive epilepsy, flashing light can trigger a seizure. Epilepsy Action, the UK charity, says around 3 to 5 in every 100 people with epilepsy are photosensitive, and that flashing between 10 and 25 times a second is the most common trigger21.

WCAG criterion 2.3.1, Three Flashes or Below Threshold, at level A, says a page must not contain anything that flashes more than three times in any one second, unless the flash is below defined size and brightness thresholds22. This criterion applies to everything on the page, even content that is not otherwise meant to meet WCAG, because one flashing advert can make the whole page unsafe22.

Example: the Black Friday banner

A publisher sends Ruth an animated GIF for a Black Friday promotion. It flashes between white and red, fast. Ade counts it frame by frame in an image editor: eight full changes in one second.

  1. Eight flashes in one second is more than three. It fails 2.3.1. There is no fix that keeps the flashing.
  2. Ade replaces the GIF with a still image in the same colours and puts the offer in real text beside it, as he did with the autumn banner.
  3. He adds a note to the shop's checklist: no supplier artwork goes live until someone has checked it for flashing.

Nobody on the Brightwater team has epilepsy, as far as Ruth knows. That is exactly the point: the customer this protects is one the shop will never hear from.

Respect "reduce motion": the setting is already on their device

Every major operating system has a setting that asks apps to cut down on motion. On a Mac it is Reduce motion in the accessibility settings, on an iPhone it sits under Accessibility and Motion, Windows 11 calls it Animation effects, and Android calls it Remove animations. Browsers pass that wish on to websites through a CSS media feature, prefers-reduced-motion, which MDN describes as widely available across browsers since January 202023.

WCAG criterion 2.3.3, Animation from Interactions, asks that motion animation triggered by an interaction, such as scrolling or a click, can be switched off unless it is essential. It is level AAA, so it is above the AA line the law points to24. It is still worth doing, because the W3C's own explanation names the people it protects: for those with vestibular disorders, motion such as parallax scrolling can trigger dizziness, nausea and headaches, and the reaction can be severe enough to need bed rest24. Helen is one of them.

The cost is a few lines of CSS. You do not need to remove all animation. Fades and colour changes are usually fine. Movement across the screen, zooming, spinning and parallax are what to switch off.

Example: Ade's reduced motion rules

The Brightwater site has three moving effects: the carousel, a parallax effect on the banner photo, and a small book that flies into the basket icon when you add something.

/* Default: gentle movement for those who want it */
.hero img { transform: translateY(var(--parallax-offset)); }
.basket-fly { animation: fly-to-basket 600ms ease-out; }

/* The customer has asked for less motion */
@media (prefers-reduced-motion: reduce) {
  .hero img { transform: none; }
  .basket-fly { animation: none; }
  html { scroll-behavior: auto; }
  *, *::before, *::after {
    transition-duration: 0.01ms !important;
  }
}

Step by step, for Helen with Reduce Motion turned on:

  1. The banner photo stays still while she scrolls.
  2. The flying book is gone. The basket count still changes, and the shop already announces "Added to your basket" in text, so she loses no information.
  3. Page jumps to a section happen at once instead of a smooth scroll.
  4. The carousel never starts, because the script checks the same setting with matchMedia.

Everyone else still gets the movement. Helen gets a still page without having to find a setting on the site, because she already set it once on her phone.

The law: the duty sits with whoever runs the shop

Everything in this chapter maps to the European standard EN 301 549, whose web requirements in clause 9 follow WCAG 2.1 at level AA25. That standard is the yardstick behind the European Accessibility Act, which since 28 June 2025 covers online shops selling to consumers in the EU. The Act's Annex I asks for services that present information in fonts with sufficient contrast, supplement non text content with an alternative, and make websites perceivable, operable, understandable and robust26. Very small businesses, with fewer than 10 staff and no more than €2 million in turnover or balance sheet, are exempt from the service requirements, and the law article explains who is covered in detail.

In the UK, the Equality Act 2010 applies to every business that provides services to the public, whatever its size. It requires reasonable adjustments, so that disabled customers are not put at a substantial disadvantage, and that duty applies to the way a business provides its services, which for a shop includes its website2728. The Act names no technical standard, which is why WCAG 2.1 AA is the practical benchmark.

Example: what applies to Brightwater Books

Ruth sells mainly in the UK, so the Equality Act applies to her online shop today. A customer who cannot use the site because the sale exists only in a picture, or because the video has no captions, is being put at a disadvantage the shop could easily have avoided.

Ruth also posts books to customers in Ireland and France, which brings the European Accessibility Act into view, depending on her size. Her answer is the same either way: build to WCAG 2.1 AA, which covers both. No plugin changes that. The duty sits with Ruth, and the work sits in the site's own code and content. Ade keeps a note of how he checked each fix, because that record is what her accessibility statement will be built on.

How I handle this when I build

I build sites and shops to WCAG 2.1 AA, and I say exactly that: built to WCAG 2.1 AA, never "guaranteed compliant". For this chapter's topics, that means a colour palette chosen once to clear the AA contrast ratios, and automated checks in the test suite on every build, so a regression such as a failing contrast pair fails the build the way a broken test would. On the key journeys I run the keyboard and screen reader passes by hand, because a tool cannot judge whether an alt text actually helps.

On my own website, every chart has a text description and works in light and dark mode. The site also has an accessibility panel built into its own code, where a visitor can set a larger text size, high contrast or reduced motion. That panel is a set of preferences inside a site that is already built accessibly. It is not what makes the site accessible, and it is not a third party overlay that claims to fix a site from the outside. The accessibility comes from the HTML, the CSS and the content, with the panel switched on or off.

Conclusion: pictures, sound, colour and motion, each with a second way in

Every piece of media on a shop page needs a second way in for the customer who cannot use the first one. A picture needs words that say what it is for. Words should stay words, not pictures. A video needs captions, a transcript and, where the picture says something on its own, a description. Colour needs enough contrast and a second signal. Motion needs a pause button, a hard limit on flashing and respect for the customer who has already asked their device for stillness.

Most of it costs an afternoon, not a project. The failures are common because nobody looked, not because the fixes are hard. Look at your homepage with Priya, Tom, Malcolm and Helen in mind, and you will know where to start.

If you want to know what your homepage's images, videos, colours and animations say to a customer who cannot see, hear or tolerate motion, book the free workshop: we go through it together, and the first two weeks of work are on me.

Sources

  1. 1.

    W3C, Web Content Accessibility Guidelines (WCAG) 2.1, W3C Recommendation, 5 June 2018, updated 6 May 2025 (conformance levels and success criteria 1.1.1, 1.2.1 to 1.2.5, 1.4.1, 1.4.2, 1.4.3, 1.4.5, 1.4.11, 2.2.2, 2.3.1, 2.3.3), https://www.w3.org/TR/WCAG21/ ; and W3C, Web Content Accessibility Guidelines (WCAG) 2.2, W3C Recommendation, https://www.w3.org/TR/WCAG22/

  2. 2.

    WebAIM (Utah State University), The WebAIM Million: The 2026 report on the accessibility of the top 1,000,000 home pages, results from February 2026, last updated 30 March 2026, https://webaim.org/projects/million/

  3. 3.

    W3C Web Accessibility Initiative, Understanding Success Criterion 1.1.1: Non-text Content, W3C, https://www.w3.org/WAI/WCAG21/Understanding/non-text-content.html

  4. 4.

    W3C Web Accessibility Initiative, An alt Decision Tree, Images Tutorial, W3C, https://www.w3.org/WAI/tutorials/images/decision-tree/

  5. 5.

    W3C Web Accessibility Initiative, Decorative Images, Images Tutorial, W3C, https://www.w3.org/WAI/tutorials/images/decorative/

  6. 6.

    W3C Web Accessibility Initiative, Understanding Success Criterion 1.4.5: Images of Text, W3C, https://www.w3.org/WAI/WCAG21/Understanding/images-of-text.html

  7. 7.

    World Health Organization, Deafness and hearing loss, fact sheet, 3 March 2026, https://www.who.int/news-room/fact-sheets/detail/deafness-and-hearing-loss

  8. 8.

    W3C Web Accessibility Initiative, Understanding Success Criterion 1.2.2: Captions (Prerecorded), W3C, https://www.w3.org/WAI/WCAG21/Understanding/captions-prerecorded.html

  9. 9.

    W3C Web Accessibility Initiative, Understanding Success Criterion 1.2.4: Captions (Live), W3C, https://www.w3.org/WAI/WCAG21/Understanding/captions-live.html

  10. 10.

    W3C Web Accessibility Initiative, Captions/Subtitles, Making Audio and Video Media Accessible, section Automatic Captions are Not Sufficient, W3C, https://www.w3.org/WAI/media/av/captions/

  11. 11.

    W3C Web Accessibility Initiative, Transcripts, Making Audio and Video Media Accessible, W3C, https://www.w3.org/WAI/media/av/transcripts/

  12. 12.

    MDN Web Docs, <track>: The Embed Text Track element, Mozilla, https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Elements/track

  13. 13.

    W3C Web Accessibility Initiative, Understanding Success Criterion 1.2.5: Audio Description (Prerecorded), W3C, https://www.w3.org/WAI/WCAG21/Understanding/audio-description-prerecorded.html ; and Understanding Success Criterion 1.2.3: Audio Description or Media Alternative (Prerecorded), W3C, https://www.w3.org/WAI/WCAG21/Understanding/audio-description-or-media-alternative-prerecorded.html

  14. 14.

    W3C Web Accessibility Initiative, Description of Visual Information, Making Audio and Video Media Accessible, W3C, https://www.w3.org/WAI/media/av/description/

  15. 15.

    W3C Web Accessibility Initiative, Understanding Success Criterion 1.4.3: Contrast (Minimum), W3C, https://www.w3.org/WAI/WCAG21/Understanding/contrast-minimum.html

  16. 16.

    W3C Web Accessibility Initiative, Understanding Success Criterion 1.4.11: Non-text Contrast, W3C, https://www.w3.org/WAI/WCAG21/Understanding/non-text-contrast.html

  17. 17.

    W3C Web Accessibility Initiative, Understanding Success Criterion 1.4.1: Use of Color, W3C, https://www.w3.org/WAI/WCAG21/Understanding/use-of-color.html

  18. 18.

    W3C Web Accessibility Initiative, Understanding Success Criterion 2.2.2: Pause, Stop, Hide, W3C, https://www.w3.org/WAI/WCAG21/Understanding/pause-stop-hide.html

  19. 19.

    W3C Web Accessibility Initiative, Understanding Success Criterion 1.4.2: Audio Control, W3C, https://www.w3.org/WAI/WCAG21/Understanding/audio-control.html

  20. 20.

    W3C Web Accessibility Initiative, Carousel Animations, Carousels Tutorial, W3C, https://www.w3.org/WAI/tutorials/carousels/animations/

  21. 21.

    Epilepsy Action, Photosensitive epilepsy, last modified January 2026, https://www.epilepsy.org.uk/info/triggers/photosensitive-epilepsy

  22. 22.

    W3C Web Accessibility Initiative, Understanding Success Criterion 2.3.1: Three Flashes or Below Threshold, W3C, https://www.w3.org/WAI/WCAG21/Understanding/three-flashes-or-below-threshold.html

  23. 23.

    MDN Web Docs, prefers-reduced-motion, CSS media feature, Mozilla, https://developer.mozilla.org/en-US/docs/Web/CSS/@media/prefers-reduced-motion

  24. 24.

    W3C Web Accessibility Initiative, Understanding Success Criterion 2.3.3: Animation from Interactions, W3C, https://www.w3.org/WAI/WCAG21/Understanding/animation-from-interactions.html

  25. 25.

    CEN, CENELEC and ETSI, EN 301 549 V3.2.1 (2021 03), Harmonised European Standard, Accessibility requirements for ICT products and services, clause 9, ETSI, 2021, https://www.etsi.org/deliver/etsi_en/301500_301599/301549/03.02.01_60/en_301549v030201p.pdf

  26. 26.

    European Parliament and Council, Directive (EU) 2019/882 of 17 April 2019 on the accessibility requirements for products and services (European Accessibility Act), Article 3 point 23, Article 4 paragraph 5 and Annex I Section III, EUR Lex, 2019, https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:32019L0882

  27. 27.

    UK Parliament, Equality Act 2010, section 20, Duty to make adjustments, legislation.gov.uk, https://www.legislation.gov.uk/ukpga/2010/15/section/20

  28. 28.

    UK Parliament, Equality Act 2010, section 29, Provision of services, etc., legislation.gov.uk, https://www.legislation.gov.uk/ukpga/2010/15/section/29