✅ The extends: 'recommended' property in a configuration file enables this rule.
This rule checks for these meta tag issues:
- a meta with a redirect- if it exists, it checks for a timed delay greater than 0.
- a meta with a timed refresh- the timed delay should be greater than 72,000 seconds.
- a meta that locks orientation to landscape or portrait view
- a meta with a content attribute when neither the name nor http-equiv attributes are present
- a meta without a content attribute when either the name or http-equiv attributes are present
Sometimes a page automatically redirects to a different page. When this happens after a timed delay, it is an unexpected change of context that may interrupt the user. Redirects without timed delays are okay, but please consider a server-side method for redirecting instead (method will vary based on your server type).
When content is presented with a restriction to a specific orientation, users must orient their devices to view the content in the orientation that the author imposed. Some users have their devices mounted in a fixed orientation (e.g. on the arm of a power wheelchair), and if the content cannot be viewed in that orientation it creates problems for the user.
This rule forbids the following:
This rule allows the following:
- To fix, reduce the timed delay to zero, or use the appropriate server-side redirect method for your server type.
- To fix orientation issues, remove references to
maximum-scale=1.0and changeuser-scalable=notouser-scalable=yes.
- HTML meta tag doc
- F40: Failure due to using meta redirect with a time limit
- F41: Failure due to using meta refresh to reload the page
- Success Criterion 2.2.1: Timing Adjustable
- Success Criterion 2.2.4: Interruptions
- Success Criterion 3.2.5: Change on Request
- Failure due to locking the orientation to landscape or portrait view