Skip to main content
WCAGrules
Quick navigation

Glossary · Accessibility term

Conforming alternate version

A conforming alternate version is a second version of a page that does meet WCAG, standing in for one that does not, and it is a route through the standard rather than a workaround. Conformance at any level is satisfied either by the page itself meeting the criteria or by an alternate version that does. Four requirements come with it. It has to conform at the level being claimed. It has to carry the same information and the same functionality, in the same human language. It has to be as up to date as the content it stands in for. And one of three things has to be true about how the two versions connect. Either the conforming version can be reached from the non-conforming page by a mechanism that is accessibility supported. Or the non-conforming version can only be reached from the conforming version. Or it can only be reached from a conforming page that also offers a way to the conforming one.

In practice

The two routes nobody quotes are the ones that put the accessible version at the front door. WCAG explains what it means for the non-conforming version to be reachable only from the conforming one. The answer is a mechanism such as a conditional redirect, which stops anybody loading the non-conforming page unless they arrived from the conforming version. So a site can lead with the version that conforms and keep the other one behind it, and no link on the non-conforming page is needed at all. That pattern is sanctioned rather than tolerated.

The modern shape of this is a setting rather than a second site. Setting a user preference inside the content to produce a conforming version counts as a way of reaching one, as long as the control that sets the preference is itself accessibility supported. A simplified view or a high-contrast scheme that produces a conforming page, reached by a toggle a keyboard can operate and a screen reader can name, is a conforming alternate version. That is a long way from the text-only mirror the phrase usually conjures.

The rest of the conditions are looser than people assume and the upkeep is worse. It does not have to match page for page. It does not even have to sit on your own site, as long as it is as freely available as the version it replaces. That rules out putting the accessible one behind a login while the other one is public. Several alternate versions can exist for different environments and only one of them has to be fully conformant. Where it gets expensive is language, because every language you publish in needs its own alternate version. An auditor has to test it too, so a claim resting on one hands them a second product to evaluate. And a UK public body that offers one has to describe it in its accessibility statement.

One thing it is not is a summary. Supplemental content sits alongside a page to help people understand it, and a plain-language summary next to a dense article is exactly that. That summary is not doing nothing, because supplemental content is one of the two ways to satisfy the reading level rule at Level AAA. What it is not doing is standing in for the page, and standing in is the whole job of an alternate version.

Why it matters

This is the one place the standard lets a page fail and still conform, so it is worth knowing precisely rather than roughly. State the fourth requirement too narrowly and you rule out two legitimate patterns, including the conditional redirect W3C explicitly sanctions. Drop the same-language condition from the second requirement and you can ship one alternate version for a site that publishes in five, which leaves the other four languages with nothing standing in for them. Our own position sits next to the standard rather than inside it, and we will say it plainly. Building one version of the thing that works for everybody beats building a lesser second one. The second one is another product to keep current, and it tells disabled customers which of the two they were offered.

The requirement people state as one thing

Reachable from the inaccessible page is one of three routes, not the requirement. The other two run the other way round. Put the conforming version at the front door, and let a conditional redirect keep anybody from landing on the other one unless they came from it. The fourth requirement is then met with no link on the non-conforming page at all.

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