14. Page Refreshing
14.1 Periodical page auto-refreshing
Periodical page auto-refreshing is discouraged. However, if deemed necessary, pages must refresh at a refresh rate of 5 minutes or greater (>=5 minutes).
Guide to this standard
This standard covers the W3C WAI checkpoint 7.4 (http://www.w3.org/TR/WCAG10-TECHS/#tech-no-periodic-refresh) for NZ government agencies.
Rationale for this standard
It can be disruptive and frustrating for users if a page refreshes (particularly if the content and/or structure also changes) before they have had time to finish reading content of their interest on the page.
Screen readers also have difficulty with refreshed web pages.
If an auto refresh has been incorporated into the code (at a refresh rate less than specified in the standard), users who find the refreshing disruptive and/or frustrating have little control over this functionality.
If it is deemed necessary to auto refresh web pages, a period of 5 minutes has been determined as sufficient time for most users to have completed their interest in a page (including if they are utilising assistive technology), such that a page refresh would cause minimal concern to the user.
14.2 Page auto-redirecting
Do not use mark-up (META or scripting) to automatically redirect pages. Instead, configure the server to perform redirects.
Guide to this standard
The need to introduce page redirects occasionally (i.e. pages being superseded etc.) is acknowledged.
If and when the need arises to do this, it should be done by configuring the appropriate server to do so.
This standard is in place, due to the inability of user agents to stop auto-redirect.
This standard covers the W3C WAI checkpoint 7.5 (http://www.w3.org/TR/WCAG10-TECHS/#tech-no-auto-forward) for NZ government agencies.
Rationale for this standard
It can be disruptive and frustrating for users if a page auto-redirects, as they can get disorientated with the site and feel that they are not in control of navigation within the site.
[ Previous | Next ]

