Use an accessible, alternative version of your web pages

• May 22, 2020
• Ivar Illing
• 4 minutes

According to Dutch law, the content of the websites of government agencies must be accessible. WCAG 2.1 is leading for this. Dutch government wil also introduce stricter legislation on accessibility for other organizations. But what if it is not possible to make your website entirely accessible? Then you can still fulfill your obligation by creating an alternative version of certain pages that is accessible. There are only some conditions attached to that. We will share the possibilities of an accessible, alternative version of your webpages with you.

When is an accessible, alternative version of your webpages useful?

It is sometimes impossible to make a page accessible. There are a variety of reasons for that:

• Sometimes a page uses a technology that does not (yet) provide proper accessibility support. This occurs regularly, especially with new technologies. Do you still want to use such a technology? For example, because it offers advantages in terms of speed or ease of use for other visitors? An alternative page for people with challenges is a solution. You then omit the used technology.
• Sometimes it is not possible to change certain content. For example, because an exact copy of a document must be available on the website, for legal or historical reasons. It also happens that a page is on your website, but you do not have the right to edit it. To make this type of content accessible, you can use an alternative page.
• Sometimes visitors with certain challenges need special adjustments that get in the way of the adjustment needs of other visitors. In that case, an alternative page can also be a good idea.

Substantive requirements for the alternative version

There are a number of requirements that the alternative version of a page must meet by law. Namely:

1. The accessible version of a page must meet the same requirements as the rest of your website. For government agencies, this page must therefore comply with WCAG 2.1.
2. The accessible version must be as up to date as the original. So you will have to maintain both versions with the same frequency.
3. The accessible version must have exactly the same information and functionality as the inaccessible version, in the same language or languages. The two versions may look different.
4. The visitor must be able to reach the accessible version in one of these ways:

• • Through a button or link on the inaccessible version
    Visitors enter the inaccessible version first and can then click through to the accessible version. It is of course important that this button or link for people with challenges is easy to find.
  • The visitor always enters the accessible version first
    In this case, make sure that a visitor will never enter the inaccessible version directly. You can use a conditional redirect for this. As soon as someone wants to visit the inaccessible version, first check where the visitor comes from. Does the visitor come from the accessible version? Then the inaccessible version loads. Is the visitor not coming from the accessible version? Then he will be forwarded to the accessible version.
  • Via a front page
    This is a page where visitors can be split up. This page must be accessible and contain a link to both the inaccessible and the accessible version. It is important that the inaccessible version can only be visited if the user first visited the front page. You can also use conditional redirect for this. Is the visitor coming from the front page? Then the inaccessible version loads. Is the visitor not coming from the front page? Then he will be forwarded to the front page, so that he can make a choice first.

Requirements for the inaccessible version

Do you want to use an alternative, accessible version of your webpages? Then there are still some requirements for the inaccessible version of your page.

1. Provide the option to turn off or mute sound that automatically plays for more than 3 seconds. Otherwise, someone using reading software may be hindered by the sound.
2. Prevent a visitor using only a keyboard from getting stuck and unable to proceed.
3. Allow visitors to stop moving, flashing, auto-refreshing, and scrolling parts. This is very distracting for people who have difficulty reading or concentrating.
4. Do not flash elements in such a way that visitors can have a seizure. People with epilepsy or certain other conditions can have a seizure when looking at something that flashes more than three times per second.

These requirements are important because otherwise visitors with a challenge may not be able to use your website at all.

Aally as an alternative version

Do you want to easily create an alternative version for your inaccessible pages? You can with Aally. Aally puts an extra layer over your website, as it were. Through a button at the top right of the page, visitors with a challenge access the accessible version of your page. Aally is fully aimed at the end user and contains multiple solutions in one. Your website visitor chooses which tools he or she needs.

Curious? We are happy to show you how it works without obligation. Request a demo.