Accessibility in creative operations: build it into content production
How to build accessibility into creative operations and content production: from WCAG 2.2 and the EAA 2025 to criteria that fit into briefing, templates, and review.

Accessibility means that people with disabilities can perceive, understand, and use content and its controls. Across web, video, social media, and presentations, it depends on both the piece and how it is published and played. A single file property cannot establish it.
Legal requirements depend on country, sector, service, and applicable exceptions. In the EU, EAA application from June 2025 concerns defined products and services; it did not automatically bring every digital item within that directive.
This article walks through what the principle really means, its theoretical history, what current regulation says, how it applies across different formats, and how to integrate it into creative operations so it stops being a dead PDF.
Who formulated it and how
Universal design considers a broad range of users from the outset. Ronald Mace advanced this approach at NC State. The center was established in 1989 as the Center for Accessible Housing; a group of specialists developed the seven principles, with version 2.0 published in 1997. NC State history and principles:
- Equitable use: usable by people with diverse abilities.
- Flexibility in use: it adapts to individual preferences and abilities.
- Simple and intuitive: easy to understand regardless of experience, knowledge, or concentration level.
- Perceptible information: it communicates effectively to the user, given ambient conditions or sensory abilities.
- Tolerance for error: it minimizes hazards and the adverse consequences of accidental actions.
- Low physical effort: usable comfortably, with minimal fatigue.
- Adequate size and space: to approach and use it regardless of body size or posture.
These principles carried over into industrial design, architecture, and, over time, digital design.
The curb cut effect illustrates how an adaptation may benefit people beyond its intended users. UC Berkeley's history records access modifications in 1958 and a curb-ramp agreement in 1970. Benefits need evaluation: one solution does not necessarily improve everyone's experience.
Captions can also help someone watching without sound; suitable contrast can help reading under different lighting conditions. These additional uses do not replace evaluation with people with disabilities.
The legal history
Different legal frameworks have their own scope and requirements.
United States: Section 508 concerns covered technology that federal agencies develop, procure, maintain, or use. The update was published in January 2017, with compliance required from January 2018 subject to exceptions; it incorporates WCAG 2.0 A/AA. It does not automatically cover every contractor's technology. U.S. Access Board.
The Convention on the Rights of Persons with Disabilities includes accessibility obligations for States Parties. Distinguish those obligations from the specific rule applying to a company or piece of content.
European Union: the EAA covers specified products and services, including e-commerce, consumer banking services, and e-books. It does not cover every private website or every vending machine. The Web Accessibility Directive has a different scope, focused on the public sector. European Commission coverage overview.
Spain: Title I of Law 11/2023 transposes requirements for specified products and services. Article 3.3 provides an exemption for microenterprises supplying services; scope, transition provisions, and other applicable laws also need checking. This exemption does not remove every accessibility obligation.
Technical standards: WCAG and EN 301 549 are not equivalent to a universal legal obligation. To claim a presumption of conformity, check which version is officially cited, under which legislation, and for what scope. Publishing a new technical version does not automatically harmonize it. Commission explanation of harmonization.
Identify the service, audience, and applicable rule before choosing the technical version and evaluation level for a deliverable.
WCAG and the POUR principles
The world's reference technical standard is the Web Content Accessibility Guidelines published by the W3C. The timeline:
- WCAG 1.0 (1999): pioneering, based on technical checkpoints.
- WCAG 2.0 (2008): organization around the POUR principles.
- WCAG 2.1 (2018): adds criteria for mobile, low vision, and cognitive disabilities.
- WCAG 2.2 (October 2023): adds nine criteria and removes 4.1.1 Parsing. Additions cover focus, dragging, target size, help, and authentication. W3C change overview.
The POUR principles are the conceptual foundation:
P: Perceivable. Information and interface components must be presented in ways users can perceive. Alternative text for images, transcripts for audio, captions for video, sufficient contrast, content adaptable to different presentations.
O: Operable. The interface and navigation must be operable. Keyboard accessible, enough time to read and use content, avoiding content that causes seizures, navigation aids.
U: Understandable. Information and interface operation must be understandable. Readable text, predictable behavior, help with data entry.
R: Robust. Content must be robust enough to be interpreted by a wide variety of user agents, including assistive technologies. Compatibility with current and future technologies.
Success criteria are grouped into levels A, AA, and AAA. An evaluation needs to state the version, level, and pages or processes covered. The required level depends on the applicable framework, not simply on which version is newest.
The real size of the problem
The WHO estimates 1.3 billion people with significant disability, 16% of the global population. Spain's INE EDAD 2020 survey recorded 4.38 million people living in households who reported disability or limitation. These estimates have different scopes.
In February 2026, WebAIM Million detected automated failures on 95.9% of the million home pages analyzed, averaging 56.1 errors per page. This sample and automated analysis are not an audit of the entire web; no detected errors does not establish conformance.
These figures do not predict a brand's commercial performance. Identify barriers in a particular deliverable and check how its intended users interact with it.
How it's applied, format by format
Jumping from theory to practice.
Web pages:
- Correct semantic HTML structure (hierarchical headings, lists, regions).
- Alternative text on informative images (alt text); decorative images with
alt=""so screen readers ignore them. - Text contrast under WCAG 1.4.3: normally 4.5:1, or 3:1 for large text —at least 18 points, or 14 bold— subject to the criterion's exceptions. W3C explanation.
- Keyboard navigability: visible focus, logical order, no keyboard traps.
- Forms with labels (
<label>) associated with each field. - Descriptive error messages linked to the relevant field.
- ARIA (Accessible Rich Internet Applications, W3C 2014/2017) for complex components when semantic HTML isn't enough, but "no ARIA" is better than "ARIA used badly."
Video:
- Captions including speech and sounds needed to understand the content, according to the media type. W3C caption guidance.
- Description of necessary visual information not already conveyed in the audio. Requirements depend on the medium and level; a transcript does not always replace audio description. W3C description guidance.
- A transcript where it forms part of the required alternatives or agreed deliverables, including the information needed for that use.
- A keyboard-accessible player.
Social media:
- Alternative text on images (Instagram, Twitter/X, and LinkedIn allow it).
- Open or selectable captions according to the destination. Check player support, timing, readability, and relevant sounds; do not assume every platform has the same limitation.
- Capitalizing separate words in hashtags can help readability; check the result with the screen readers being used.
- Provide an alternative for relevant text inside images; do not depend on automatic recognition.
- Avoid replacing essential information with emojis and check how they are read; names and repetition can make comprehension harder.
Presentations and documents:
- Legible typography, a reasonable minimum size.
- Sufficient contrast between text and background.
- Structure with headings (not just "bold and big").
- An accessible version or transcript available for complex presentations.
- Review tags, reading order, alternatives, and other PDF requirements; tags alone do not establish accessibility.
Mobile apps:
- Compatibility with VoiceOver (iOS) and TalkBack (Android).
- Touch targets and spacing appropriate to the platform. Apple distinguishes default and minimum sizes; Android recommends 48×48 dp. These are not a universal WCAG minimum.
- Support for the system's large type, dark mode, and high contrast.
Packaging and physical product:
- Legible text, reasonable contrast.
- Essential information in braille in specific sectors (medications, elevators).
- Package designs that can be opened with mobility limitations.
The tooling ecosystem
The tools a serious team uses to maintain accessibility without turning it into bureaucracy:
Automation in development:
- axe DevTools (Deque) and Lighthouse (Google, built into Chrome): check accessibility on pages in real time.
- WAVE (WebAIM): a browser plugin with visual analysis.
- Pa11y, axe-core: tools for CI/CD that detect regressions automatically.
There is no universal percentage of problems detectable automatically. Tools must be combined with human evaluation; they do not determine conformance on their own. W3C evaluation guidance.
Manual testing:
- Keyboard-only navigation (Tab, Shift+Tab, Enter, Space, arrow keys).
- Testing with screen readers: NVDA (free, Windows), VoiceOver (free, built into macOS/iOS), TalkBack (Android), JAWS (commercial).
- Test text enlargement and content reflow; the reflow criterion covers the equivalent of 320 CSS pixels in width, normally 400% zoom from 1280, with exceptions. WCAG 1.4.10.
- Testing with color blindness and low vision simulators.
Professional audits:
- An audit should state scope, criteria, method, and limitations. Hiring a provider does not by itself guarantee legal compliance.
- Testing with real users with disabilities: the most valuable complement, often the most informative.
Mistakes that keep happening
Treating accessibility as a final check. Auditing in the last week of the project, finding 200 errors, ignoring most of them for lack of time. The fix: integrate criteria from the briefing, not after building.
Relying only on automated tools. They detect some barriers, but not every difficulty in use. A tool may fail to detect that the tab order is illogical, that the alt text is useless ("image1"), or that error messages are confusing.
Alt text without context. An informative image needs its information conveyed; a graphical button needs its function; a purely decorative image may use an empty alternative. The same photo may need different alternatives in different uses. W3C image tutorial.
Text inside images. If a message exists only as pixels without an equivalent alternative, some people cannot access it. Do not depend on automatic text recognition.
Contrast for aesthetics. Light text on a light background can be difficult to read. Measure contrast and check readability in the publishing context.
Buttons that don't look like buttons. Minimalist designs where interactive elements look decorative. If it looks like text, people won't discover it's a button.
Forms without labels. Placeholders that disappear when you start typing, leaving the user with no clue what that field was for.
Hidden error messages. "Error in the form" without saying which one or where. For a sighted user with time, irritating; for a screen reader user, blocking.
Animations that can't be stopped. Carousels, gifs, and autoplay videos with no pause option. They cause problems for people with vestibular and attention disorders.
Inaccessible captchas. Visual captchas with no accessible alternative are an insurmountable barrier for many people.
Confusing an error-free scan with conformance. An automated tool does not evaluate every criterion or user experience. Document the evaluation's scope and limitations.
Treating accessibility as a minority case. The "it's for a few, it's not worth it" argument is both morally weak and technically wrong: it ignores the curb cut effect, temporary disabilities, aging, legal risk, and the general improvement in UX.
How to fit accessibility into creative operations
A team producing many pieces needs review criteria from the briefing and clear responsibilities. Templates and automation help but do not eliminate contextual evaluation of each deliverable.
In the briefing: define accessibility requirements by piece type (audio and video alternatives, alternative text according to function, contrast, and keyboard navigation).
In the templates: a visual identity with validated contrast palettes, legible typography, minimum sizes, motion graphics with reduced-motion options.
In production: prepare required alternatives for audio and visual information; choose alternative text according to each image's context and function. A generic description stored in the library is not automatically suitable alt text for every publication.
In review: an accessibility check as part of the approval process, not optional.
In the team: initial and periodic training, someone designated as the accessibility point person (not necessarily full-time, but with clear responsibility).
In creative operations, the team sets requirements and evaluates deliverables. The Polimake cloud library stores and retrieves images and videos through its interface, API, or MCP. Locating a version does not establish accessibility: the team must check the file, alternatives, and publishing environment.
See why caption a video for audio-related work, brand asset stewardship for current references, and Gestalt applied to creative reviews for visual criteria.
To close
Accessibility requires checking content and the user experience. A template, library, or automated test may support the work, but does not itself establish that a deliverable meets its requirements.
Set criteria from the briefing, identify owners, and combine tools with human evaluation. When reusing a piece, check whether the new context changes its alternatives, playback, or requirements.
Quick reference
- Universal design: Mace and NC State's work; principles published by a specialist group in 1997.
- Curb cut effect: possible additional benefits that need evaluation.
- WCAG: state version, level, and evaluation scope.
- POUR: Perceivable, Operable, Understandable, Robust.
- EAA: specified products and services, with exceptions and transition provisions.
- Minimum contrast 4.5:1 normal text / 3:1 large text.
- Alt text for informative images; empty for decorative ones.
- Full keyboard navigation, visible focus.
- Audio and video alternatives according to the content and applicable requirements.
- Hashtags in CamelCase on social media.
- Human and automated evaluation: no universal detection percentage.
- Test with screen readers (NVDA, VoiceOver, TalkBack).
- Accessibility from the briefing, not as a final check.
Frequently asked questions
What is the principle of accessibility?
The principle of accessibility holds that a product, space, or piece of content should be perceivable, understandable, and usable by anyone, including people with disabilities, without relying on after-the-fact adaptations. In digital design, it takes shape in the W3C's WCAG guidelines and their four principles: perceivable, operable, understandable, and robust.
What is the difference between accessibility and usability?
Accessibility makes sure everyone, including people with a disability, can use something; usability measures how easy and efficient it is to use. A form can be convenient for most people and still impossible with a screen reader. The two are worked on together but evaluated separately.
Is web accessibility mandatory in Spain?
It is for the public sector and, since June 28, 2025, for certain private products and services covered by Spain's Law 11/2023, such as e-commerce or consumer banking services, with exceptions like microenterprises that provide services. Not every private website falls under that law, so each case needs to be reviewed.
Which WCAG level do you need to meet?
The usual benchmark is level AA, which is the one adopted by the European standard EN 301 549 for the web. Level A covers the minimum, and the W3C does not recommend requiring AAA as a general policy, because some of its criteria cannot be met for every type of content. Always state which WCAG version you're evaluating against.