Applicability

Description

The objective of this technique is to enable redirects on the client side
without confusing the user. Redirects are preferably implemented on the
server side (see SVR1: Implementing automatic redirects on the server side instead of on the
client side (SERVER)
), because a server-side
redirect does not cause new content to be displayed before the server sends
the content located at the new URI. However, authors do not always have
control over server-side technologies; in that case, they can use a
client-side redirect. A client-side redirect is implemented by code inside
the content that instructs the user agent to retrieve content from a
different URI. It is important that the redirecting page or Web page
only contains information related to the redirect.

Tests

Procedure

For each link or programmatic reference, check if the referenced
Web page contains code (e.g., meta element or script) that
causes a client-side redirect.

For each link or programmatic reference that causes a
client-side redirect, check if the redirect is implemented
without a time limit or delay and that the page only contains
information related to the redirect.

Expected Results

Step 2 is false or step 3 is true.

If this is a sufficient technique for a success criterion, failing this test procedure does not necessarily mean that the success criterion has not been satisfied in some other way, only that this technique has not been successfully implemented and can not be used to claim conformance.

Techniques are Informative

Techniques are informative—that means they are not required. The basis for determining conformance to WCAG 2.0 is the success criteria from the WCAG 2.0 standard—not the techniques. For important information about techniques, please see the Understanding Techniques for WCAG Success Criteria section of Understanding WCAG 2.0.