Digital Quality Management
cancel
Showing results for 
Search instead for 
Did you mean: 

DQM Checkpoints and Standards

Checkpoints - Do not use meta refresh tags

 

This meta tag sends the user to a new URL after a certain amount of time, and is sometimes used as a simple form of redirection. However, it is not supported by all browsers and can be confusing to the user. See WCAG 1.0, 7.4. The W3C also recommends that this tag not be used.

Meta refresh tags have some drawbacks:

  • There can be a usability problem if the redirect happens quickly (less than 2-3 seconds). This prevents users of older browsers from using the “Back” button.
  • If the redirect happens quickly and goes to a non-existant page, your readers may get stuck in a loop without seeing any content other than a 404 page. 
  • Refreshing the current page can be confusing. If a user didn’t request the reload, they may become concerned about your site's security.

 

Affects Accessibility, SEO Non-compliant pages will fail WCAG 1 Level AA. "Until user agents provide the ability to stop the refresh, do not create periodically auto-refreshing pages" (WCAG 1 Priority 2)
Technical Details For this checkpoint we will scan through the page to see if there is an existence of the meta refresh tags - <meta http-equiv="refresh" content="30"> - if this tag exists then it will be flagged as an error.
References https://www.w3.org/TR/WCAG10/
Labels (1)
Version history
Revision #:
3 of 3
Last update:
‎05-15-2019 09:57 PM
Updated by:
 
Looking for more?
Ask in Discussions
Developers

Peer-to-peer support  and answers on developing CMS templates, modifying privacy scripts or building integrations.

Digital Experience Management

Find answers and ask questions on content management, personalization and targeting.

Digital Quality Management

Find answers and ask questions on WCAG and SEO quality management.

Digital Governance

Find answers and ask questions on consent and monitoring solutions.