Accessibility in Visual Journalism

What you need to know

The Web Content Accessibility Guidelines (WCAG) 2.1 published by the W3C set the international standard for accessible digital content. Level AA is the minimum benchmark required by UK law for public sector websites under the Public Sector Bodies Accessibility Regulations 2018. For visual journalists, the most relevant criteria govern colour contrast (1.4.3 and 1.4.11), the use of colour as the sole means of conveying information (1.4.1), text alternatives for non-text content (1.1.1), and captions for video (1.2.2).

Accessible visuals benefit a wide audience: approximately one in five people in the UK has a disability, including an estimated two million people living with sight loss according to the Royal National Institute of Blind People (RNIB). Colour vision deficiency affects around 4.5% of the population. Accessible design also improves comprehension for readers using mobile devices in bright sunlight, viewers watching video without sound, and users relying on translation tools.

Organisations including AbilityNet and the A11Y Projectpublish practical resources to help publishers audit and improve their visual content. The W3C's WAI (Web Accessibility Initiative) maintains comprehensive tutorials covering images, charts, and multimedia that apply directly to visual journalism workflows.

When accessibility issues arise

• 1Publishing a data visualisation that uses colour alone to distinguish between datasets, making it unreadable for colour-blind readers.
• 2Embedding a chart or infographic as a flat image without alt text, leaving screen reader users with no access to the data.
• 3Using low-contrast text overlaid on a photograph in a graphic, failing the 4.5:1 WCAG AA text contrast requirement.
• 4Publishing video content without captions or subtitles, excluding deaf and hard-of-hearing viewers and non-native speakers.
• 5Producing an animated or auto-playing graphic that flashes more than three times per second, risking seizures for photosensitive viewers.
• 6Relying on hover tooltips as the only way to access data values in an interactive chart, making those values inaccessible to keyboard-only users.
• 7Using icon-only buttons in an interactive graphic without accessible labels, leaving screen reader users unable to identify controls.
• 8Distributing infographics on social media without descriptive alt text in the image caption or thread, bypassing the platform's built-in alt text fields.

Red flags

• ⚠A chart uses red and green to distinguish two data series — the most common form of colour vision deficiency is red-green, making these indistinguishable for affected readers.
• ⚠An infographic template from a third-party tool has been published without checking contrast ratios — many default design templates fail WCAG AA thresholds.
• ⚠The alt text for a graph simply repeats the headline rather than summarising the key data finding — this provides no additional information to screen reader users.
• ⚠Video has been published with auto-generated captions only, without review — automated captions regularly misidentify proper nouns, technical terms, and accents common in UK news.
• ⚠A public sector news site has received an accessibility complaint but has no published accessibility statement — the Regulations require a statement explaining known issues and remediation plans.
• ⚠An animated graphic has no pause button — WCAG 2.1 Success Criterion 2.2.2 requires that moving content lasting more than five seconds can be paused, stopped, or hidden.

Accessibility checklist for visual journalists

• I have checked text-on-graphic contrast using a tool such as the WebAIM Contrast Checker and confirmed it meets 4.5:1 (normal text) or 3:1 (large text).
• I have verified that graphical elements such as chart lines, icons, and borders meet the 3:1 non-text contrast ratio against adjacent colours.
• I have confirmed that colour is not the only means of distinguishing data series — direct labels, patterns, or shapes are also used.
• I have previewed the graphic using a colour-blind simulator (Coblis, Viz Palette, or browser DevTools vision deficiency emulation) and adjusted the palette if needed.
• I have written descriptive alt text for every image and chart that conveys the key information, not just the visual type.
• For complex infographics, I have provided a text alternative in the article body or linked to a structured data table.
• All video content has accurate human-reviewed captions or subtitles, not solely auto-generated text.
• Any animated or auto-playing graphic has a visible pause or stop control accessible to keyboard-only users.

Common mistakes

• ›Writing alt text as a literal description of the visual (“blue bar chart”) rather than communicating the data insight — alt text should answer the question the graphic is designed to answer.
• ›Treating accessibility as a final QA step rather than a design constraint — choosing an accessible colour palette at the outset is faster than retrofitting contrast fixes before publication.
• ›Assuming that publishing an accessible HTML article alongside an embedded image satisfies WCAG — the image itself must also carry an appropriate text alternative.
• ›Using decorative images without marking them as decorative (alt=“”) — screen readers will announce the file name if alt text is absent, confusing users.
• ›Copying captions verbatim from a video transcript without editing for readability — good captions include speaker identification, sound descriptions, and natural line breaks.
• ›Failing to test interactive graphics with a keyboard alone — if a chart tooltip or filter cannot be reached via Tab and Enter, keyboard-only users are excluded from the content.

Related guides

Primary sources

Frequently asked questions