The Accessibility Principle: What It Is and How to Apply It

There's an idea that's easy to accept and hard to apply: that a digital product, a video, a building, or a service should be usable by as many people as possible, without demanding extraordinary adaptations from them. That's the simplest formulation of the accessibility principle. Public agreement on the idea is broad. Its everyday, systematic application, in every piece a team produces, remains the exception.

In 2026 the conversation changed. What for years was treated as "added value" or a "special case" became an enforceable legal obligation in the EU, a minimum quality standard in serious digital product work, and a decisive factor in how a significant share of the audience gets access. Brands that still treat accessibility as a final checklist on the last day of a project expose themselves to complaints, fines, and lost market share.

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

The modern concept of universal design, of which the accessibility principle is part, has a name, a place, and a date. Ronald Mace, an architect and professor at North Carolina State University, coined the term "universal design" in 1985. Mace, who had contracted polio at age nine and used a wheelchair throughout his adult life, observed that traditional "accessibility" solutions, additional ramps, separate restrooms, specialized products, stigmatized rather than included. His proposal: design from the start for the widest possible range of people, with no need for later adaptations.

In 1989 he founded the Center for Universal Design at NC State. In 1997, together with colleagues, he published the seven principles of universal design, which remain a reference:

1. Equitable use: usable by people with diverse abilities.
2. Flexibility in use: it adapts to individual preferences and abilities.
3. Simple and intuitive: easy to understand regardless of experience, knowledge, or concentration level.
4. Perceptible information: it communicates effectively to the user, given ambient conditions or sensory abilities.
5. Tolerance for error: it minimizes hazards and the adverse consequences of accidental actions.
6. Low physical effort: usable comfortably, with minimal fatigue.
7. 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.

There's another concept worth keeping in mind: the curb cut effect. In 1972, Berkeley installed the first sidewalk curb cuts, pushed by Vietnam War veterans returning in wheelchairs and by the disability rights movement. What was designed with wheelchairs in mind ended up benefiting everyone: parents with strollers, delivery workers with carts, travelers with suitcases, cyclists, older people. The metaphor generalized: well-designed accessibility solutions improve the experience for everyone, not just the group originally identified.

Subtitles meant for deaf people end up benefiting anyone watching without sound on public transit. High contrast meant for people with low vision benefits anyone reading in direct sunlight on their phone. Plain language meant for people with cognitive difficulties benefits anyone reading quickly under work pressure. Accessibility isn't a sacrifice for a minority; it's an upgrade for everyone.

The legal history

Legally, the 20th century brought four milestones that defined today's framework.

The United States was a pioneer. The Americans with Disabilities Act (ADA) was signed on July 26, 1990 by President George H. W. Bush. The law established civil rights for people with disabilities and laid the foundation for all later case law. Section 508 of the Rehabilitation Act, in its 1998 amendment, required accessibility in federal government technology and that of those who contract with it. The Section 508 refresh in January 2018 aligned federal requirements with WCAG 2.0 level AA, unifying the criteria.

Internationally, the United Nations Convention on the Rights of Persons with Disabilities, adopted in 2006 and in force since 2008, established accessibility obligations for the signatory states (more than 180 countries).

Europe moved later but more systematically. The Web Accessibility Directive (Directive 2016/2102) required public sector bodies to comply with WCAG. The European Accessibility Act (Directive 2019/882) came into effect on June 28, 2025 and extends accessibility obligations to a wide range of private products and services (e-commerce, banking services, transport, e-books, terminal equipment, vending machines, smartphones). The harmonized European technical standard is EN 301 549, aligned with WCAG.

Spain complemented this with the General Law on the rights of persons with disabilities and their social inclusion (Royal Legislative Decree 1/2013) and Law 11/2023, which transposed the EAA into Spanish law.

In terms of case law, cases such as NAD v. Netflix (2012, which required Netflix to caption its catalog in the U.S.) and Robles v. Domino's (2019, in which the U.S. Supreme Court declined to review and left standing the ruling that extends the ADA to websites) have broadened the scope of these obligations to digital content.

The consequence for 2026: any company with a significant digital presence in European, Anglophone, or Latin American markets has real legal obligations regarding accessibility. Ignoring them can translate into complaints, administrative sanctions, and litigation.

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): a rethink around the POUR principles. The version most regulations reference.
• WCAG 2.1 (2018): adds criteria for mobile, low vision, and cognitive disabilities.
• WCAG 2.2 (October 2023): adds nine criteria on authentication interaction, contextual help, and visible focus.

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.

Each principle breaks down into guidelines, and each guideline into success criteria at three levels: A (minimum), AA (the usual standard for legal and voluntary compliance), AAA (excellence, rarely required in full). WCAG 2.1 level AA is the compliance standard most regulations reference today.

The real size of the problem

The figures to keep in mind:

• The WHO estimates that more than 1 billion people worldwide have some form of disability, roughly 16% of the world's population.
• In Spain, according to the INE, around 4.3 million people report having some disability.
• Approximately 8% of men and 0.5% of women have some form of color blindness.
• More than 200 million people worldwide have low vision that can't be fully corrected.
• Disability is temporary for many people at some point (injuries, pregnancy, surgery) and permanent for a large minority.
• Age brings disabilities: presbyopia, presbycusis, reduced mobility. An aging society is a society with greater accessibility needs.

And the data from the digital market itself:

• The WebAIM Million, an annual analysis of the accessibility of the million most popular websites in the world, has consistently found since 2019 that more than 96% of home pages have automatically detectable accessibility errors. The average has hovered around 50-60 errors per home page. The situation improves very slowly.
• The most common errors are the easiest to avoid: low text contrast, images without alt text, empty links, buttons without a label, forms without a label.

The consequence: most current sites are not accessible. That means any brand that takes care of accessibility gains a real advantage, not just regulatory compliance.

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.
• Minimum contrast: 4.5:1 for normal text, 3:1 for large text (WCAG 2.1 AA).
• 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 for spoken audio (covered in detail in another article).
• Audio description for visual action relevant to the plot, where applicable.
• A full transcript available.
• A keyboard-accessible player.

Social media:

• Alternative text on images (Instagram, Twitter/X, and LinkedIn allow it).
• Captions on videos: burned in for Reels/TikTok where the player doesn't expose CC, an SRT file where it does.
• Hashtags in CamelCase (#CreativeOperations instead of #creativeoperations) so screen readers pronounce them correctly.
• Avoid text only inside images: screen readers don't read it.
• Limit emojis that substitute for words: each emoji is read aloud ("fire emoji, fire emoji, fire emoji").

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.
• Tagged PDFs ("accessible PDF") with a correct reading order.

Mobile apps:

• Compatibility with VoiceOver (iOS) and TalkBack (Android).
• Touch targets of sufficient size (minimum 44×44 points on iOS, 48×48 dp on Android).
• 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.

Important: automated tools detect around 30% of real problems. They're indispensable as a first line, but they don't replace manual testing.

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, dominant in professional environments).
• Testing zoom up to 200%.
• Testing with color blindness and low vision simulators.

Professional audits:

• Specialized firms (Deque, Level Access, Siteimprove, AbilityNet) carry out formal audits with a report that meets legal criteria.
• 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 technical problems but not real-use problems. 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 that's descriptive, not functional. "Image of a gray cat sitting on a couch" when the image illustrates "a state of relaxation." Better to think about what function the image serves, not what it literally shows.

Text inside images. Social media graphics with the whole message in an image and no alt text. To a screen reader, that post is blank text.

Contrast for aesthetics. Light gray on white because "it looks elegant." The result: illegible for low vision, bad for people with direct sunlight on their screen, worse for everyone.

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.

Assuming compliance = accessible. A site can pass automated tools and be horrible to use for someone with a disability. Regulatory compliance is a minimum, not the final goal.

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 brand that produces a lot of content, web, video, social, presentations, can't maintain accessibility by manually reviewing each piece. It needs a system.

In the briefing: define accessibility requirements by piece type (captions yes/no, alt text required, minimum contrast, keyboard navigation).

In the templates: a visual identity with validated contrast palettes, legible typography, minimum sizes, motion graphics with reduced-motion options.

In production: video always with captions (open or closed depending on the destination), images with required alt text before approval, social templates with reserved areas for descriptive text.

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).

Creative operations are what sustain this discipline. At Polimake, Studio defines accessibility criteria by piece type and maintains compliant templates; Media runs production with those criteria built in (captions, alt text, contrast); Studio coordinates approvals that include an accessibility review as a mandatory check.

This relates to the heading hierarchy for SEO, which is both accessibility and ranking, to why subtitle a video as a specific application of the principle, and to corporate image, which must take care of contrast and legibility natively. It also connects with the aesthetic-usability effect, where contrast and clarity reinforce the perception of quality, and with Gestalt in marketing for designing clearer campaigns and assets.

To close

The accessibility principle isn't a favor to a minority or a concession to regulation. It's the practice that separates well-made design from half-done design. Applied well, it multiplies your audience, improves UX for everyone, meets growing regulation, and builds reputation. Applied badly or ignored, it exposes you to complaints, loses market share, and signals a brand that doesn't care about its real users.

The practice that ages best: integrate accessibility as a criterion from the briefing, equip the team with tools and training, audit periodically with humans and not just automation, and recognize that "universal design" has forty years of theory behind it; it's not a fad. Brands that take it this way tend to produce better design on every front, not just in accessibility.

Quick reference

• Universal design: Ronald Mace, NC State, 1985. Seven formal principles in 1997.
• Curb cut effect: what's accessible for minorities improves everything for everyone.
• WCAG 2.1 AA is the compliance standard referenced by most regulations.
• POUR: Perceivable, Operable, Understandable, Robust.
• EAA applicable since June 28, 2025 in the European market.
• 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.
• Always caption video.
• Hashtags in CamelCase on social media.
• Automated tools detect ~30%: complement with manual testing.
• Test with screen readers (NVDA, VoiceOver, TalkBack).
• Accessibility from the briefing, not as a final check.