Skip to main content
WCAGrules
Quick navigation

Glossary · Accessibility term

Universal design

Universal design is the idea that one design should work for as many people as possible without anybody needing a special version or a separate adaptation. It started in architecture, where the example everyone reaches for is the curb cut, built for wheelchairs and used by anyone with a stroller, a suitcase or a delivery trolley. It is a treaty definition now as well, and the treaty's version covers programs and services alongside products and environments. That is what brings a website, a booking flow and a support line inside the term at all. The treaty also adds a sentence people miss. Universal design does not mean assistive devices stop being needed, and it was never meant to. Norway named the regulation behind its web accessibility duty after it, and built the phrase into the statute's own section headings.

In practice

On the web it means one site that works, rather than a main site plus a stripped-down accessible version alongside it. WCAG does permit a conforming alternate version, and it is the conditions that make one expensive rather than any objection in principle. The alternate has to conform at the level being claimed, carry the same information and the same functionality, be in the same human language, and stay as up to date as the version it stands in for. Then somebody has to be able to get to it, and WCAG gives three ways rather than one. A supported route to it from the non-conforming page, or an arrangement where the non-conforming page can only be reached from the conforming one, or one where it can only be reached from a conforming page that offers a way across. Meeting all of that continuously, through every release, is the part nobody budgets for.

There is a formal version of the idea, seven principles published in 1997 by a group of ten, and they map onto WCAG more closely than anyone expects. Information communicated whatever the ambient conditions or the user's senses. Use that is simple and intuitive regardless of experience, knowledge, language or concentration. Tolerance for error. Size and space for approach and use. One of the people who compiled that list has been contributing to WCAG ever since, which is a thread between the two rather than a line of descent.

The three words people use interchangeably are not interchangeable. W3C treats universal design and inclusion as the same idea under different regional names, and keeps accessibility deliberately separate from both, with a stated reason. General usability work does not reliably address the needs of people with disabilities, and separating the term is what keeps those specific needs in view rather than averaged away.

Why it matters

It is the argument against the text-only mirror site, which still gets proposed and which has to be maintained release for release or it falls behind the site it stands in for. And the standard makes the curb cut argument about itself, in its own background section. It notes that the guidelines also make content more usable for older people with changing abilities, and often improve usability for everybody. Designing for the edge usually improves the middle, and that is not a slogan we invented.

The test for a separate version

If somebody proposes a text-only accessible site alongside the real one, start with three questions. Will it ship in the same release as the main site, every time? Can a user get to it, by one of the three routes WCAG allows rather than only by a link on the page? Does it carry the same information and the same functions, in the same language, rather than a subset somebody chose? Those come from WCAG's own definition, along with the requirement that the alternate itself conforms at the level you are claiming. A no to any of them means you are building a second site rather than an accessible one.

Where this shows up on the site

Related terms

Knowing the word is the easy part.

Find out where your own site stands. The free scan checks 10 pages in a real browser against all 90 supported automated rules, separates 27 best-practice checks from its WCAG findings, and names the rule behind every result.

Run the free scan

Go somewhere useful

Find tools, resources and your workspace.

29 destinations