DQM and Experience Optimization
Showing results for 
Show  only  | Search instead for 
Did you mean: 

DQM Checkpoints and Standards

Checkpoints - Do not use meta refresh with a time limit

If the time interval specified is too short, some users - particularly those using screen readers or being destracted - will not have enough time to complete reading the information on the page. Sighted users may also be disoriented by the unexpected refresh and it can also cause mobile users to incur extra charges and download times.

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, Legal (WCAG 2, 2.2.1)
Technical Details:  This checkpoints looks in a page to see if a meta element with a refresh value exists, if so it checks to see if it has a time limit, in case it will be flagged as an error. Please see below for an example:

 <meta http-equiv="refresh" content="30">
References: HTML meta http-equiv Attribute
Labels (1)
Version history
Revision #:
4 of 4
Last update:
‎05-15-2019 09:57 PM
Updated by:
Looking for more?
Ask in Discussions

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.