ACT-R1: Meta refresh and redirect is not used
Important Information for reviewing ACT Rules
Important: The ACT Rules on this page are a demonstration of how they might be published by the W3C. The goal of this page is to add concrete examples for the Accessibility Conformance Testing Rules Format (DRAFT). Neither the ACT Rules, or the way they are presented here has been approved by the Accessibility Guidelines Working Group. If you have feedback, please comment by filing GitHub issues in the WCAG ACT repository, if this is not feasible, by email to firstname.lastname@example.org.
This conformance rule relates to:
- Success Criterion 2.2.1 (Timing Adjustable)
- Success Criterion 3.2.5 (Change on Request)
This test checks if meta element is not used for delayed redirecting or refreshing.
- H76: Using meta refresh to create an instant client-side redirect
- F40: Failure of Success Criterion 2.2.1 and 2.2.4 due to using meta redirect with a time limit
- F41: Failure of Success Criterion 2.2.1, 2.2.4, and 3.2.5 due to using meta refresh with a time-out
- This test assumes no functionality was provided by the website for the user to adjust the timer.
Aspects Under Test
The rule applies to any
meta element with the value of the
http-equiv attribute set to
refresh. This can be found using the following CSS selector:
The text before the first comma or semicolon is either
0 or not a number (ignore any whitespace characters).
Changes since the previous version
- Rule is updated to applicability / expectations format
This ACT rule was created by Wilco Fiers.
To validate the implementation of this rule, all test cases for ACT-R1 must be passed.