HTML and XHTML
This technique relates to Success Criterion 3.2.5: Change on Request (Sufficient as a way to meet G110: Using an instant client-side redirect).
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), but authors do not always have control over server-side technologies.
In HTML and XHTML, one can use the
meta element with the value of
http-equiv attribute set to "Refresh" and the value of the
content attribute set to "0" (meaning zero seconds), followed by the URI
that the browser should request. It is important that the time-out is set to zero,
avoid that content is displayed before the new page is loaded. The page containing
redirect code should only contain information related to the redirect.
<html xmlns="http://www.w3.org/1999/xhtml"> <head> <title>The Tudors</title> <meta http-equiv="refresh" content="0;URL='http://thetudors.example.com/'" /> </head> <body> <p>This page has moved to a <a href="http://thetudors.example.com/"> theTudors.example.com</a>.</p> </body> </html>
Resources are for information purposes only, no endorsement implied.
- Find all
metaelements in the document.
- For each meta element, check if it contains the attribute
http-equivwith value "refresh" (case-insensitive) and the
contentattribute with a number greater than 0 followed by ;'URL=anyURL' (where anyURL stands for the URI that should replace the current page).
Step 2 is false.