Proposed Meta viewport allows for zoom

Description

This rule checks that the meta element retains the user agent ability to zoom.

Applicability

This rule applies to each content attribute on a meta element with a name attribute value of viewport.

Expectation 1

For each test target, the attribute value does hot have a user-scalable property with a value of no.

Expectation 2

For each test target, the attribute value does not have a maximum-scale property with a value less than 2.

Assumptions

Pages for which any of the following is true may satisfy success criteria Success Criteria 1.4.4 Resize text and 1.4.10 Reflow, even if the rule results in a failed outcome.

The page has no visible content; or
There is another mechanism available to resize the text content; or
The content does not need to reflow in order to fit in an area of 320 by 256 CSS pixels.

Accessibility Support

Desktop browsers ignore the viewport meta element, and most modern mobile browsers either ignore it by default or have an accessibility option which will allow zooming. This rule is not relevant for desktop browsers, nor for most modern mobile browsers. Only users with older mobile browsers can experience issues tested by this rule.

Background

This rule is designed specifically for 1.4.4 Resize text, which requires that text can be resized up to 200%. Because text that can not be resized up to 200% can not fit in an area of 320 by 256 CSS pixels, this rule maps to 1.4.10 Reflow as well. All passed examples in this rule satisfy both success criteria.

Bibliography

Accessibility Requirements Mapping

1.4.4 Resize text (Level AA)
- Learn more about 1.4.4 Resize text
- Required for conformance to WCAG 2.0 and later on level AA and higher.
- Outcome mapping:
  - Any failed outcomes: success criterion is not satisfied
  - All passed outcomes: success criterion needs further testing
  - An inapplicable outcome: success criterion needs further testing

Input Aspects

The following aspects are required in using this rule.

DOM Tree

Test Cases

Passed

Passed Example 1

Open in a new tab

This viewport meta element does not prevent user scaling because it does not specify the maximum-scale and user-scalable values.

<html>
	<head>
		<title>Simple page showing random text</title>
		<meta name="viewport" content="width=device-width" />
	</head>
	<body>
		<p>
			Lorem ipsum
		</p>
	</body>
</html>

Passed Example 2

Open in a new tab

This viewport meta element does not prevent user scaling because it has user-scalable set to yes.

<html>
	<head>
		<title>Simple page showing random text</title>
		<meta name="viewport" content="user-scalable=yes" />
	</head>
	<body>
		<p>
			Lorem ipsum
		</p>
	</body>
</html>

Passed Example 3

Open in a new tab

This viewport meta element allows users to scale content up to 600% because it has maximum-scale set to 6.0.

<html>
	<head>
		<title>Simple page showing random text</title>
		<meta name="viewport" content="maximum-scale=6.0" />
	</head>
	<body>
		<p>
			Lorem ipsum
		</p>
	</body>
</html>

Passed Example 4

Open in a new tab

This viewport meta element does not prevent user scaling because it does not specify the maximum-scale and user-scalable values.

<html>
	<head>
		<title>Simple page showing random text</title>
		<meta name="viewport" content="" />
	</head>
	<body>
		<p>
			Lorem ipsum
		</p>
	</body>
</html>

Passed Example 5

Open in a new tab

This viewport meta element does not prevent user scaling because it has maximum-scale set to -1 which results in this value being dropped.

<html>
	<head>
		<title>Simple page showing random text</title>
		<meta name="viewport" content="maximum-scale=-1" />
	</head>
	<body>
		<p>
			Lorem ipsum
		</p>
	</body>
</html>

Failed

Failed Example 1

Open in a new tab

This viewport meta element prevents user scaling because it has user-scalable set to no.

<html>
	<head>
		<title>Simple page showing random text</title>
		<meta name="viewport" content="user-scalable=no" />
	</head>
	<body>
		<p>
			Lorem ipsum
		</p>
	</body>
</html>

Failed Example 2

Open in a new tab

This viewport meta element prevents users to scale content up to 200% because it has maximum-scale set to 1.5.

<html>
	<head>
		<title>Simple page showing random text</title>
		<meta name="viewport" content="user-scalable=yes, initial-scale=0.8, maximum-scale=1.5" />
	</head>
	<body>
		<p>
			Lorem ipsum
		</p>
	</body>
</html>

Failed Example 3

Open in a new tab

This viewport meta element prevents users to scale content up to 200% because it has maximum-scale set to 1.0.

<html>
	<head>
		<title>Simple page showing random text</title>
		<meta name="viewport" content="maximum-scale=1.0" />
	</head>
	<body>
		<p>
			Lorem ipsum
		</p>
	</body>
</html>

Failed Example 4

Open in a new tab

This viewport meta element prevents users to scale content up to 200% because it has maximum-scale set to yes which translates to 1.0.

<html>
	<head>
		<title>Simple page showing random text</title>
		<meta name="viewport" content="maximum-scale=yes" />
	</head>
	<body>
		<p>
			Lorem ipsum
		</p>
	</body>
</html>

Inapplicable

Inapplicable Example 1

Open in a new tab

There is no viewport meta element.

<html>
	<head>
		<title>Lorem ipsum</title>
		<meta charset="UTF-8" />
	</head>
	<body>
		<p>
			Lorem ipsum
		</p>
	</body>
</html>

Inapplicable Example 2

Open in a new tab

This viewport meta element does not have a content attribute.

<html>
	<head>
		<title>Simple page showing random text</title>
		<meta name="viewport" />
	</head>
	<body>
		<p>
			Lorem ipsum
		</p>
	</body>
</html>

Glossary

Attribute value

The attribute value of a content attribute set on an HTML element is the value that the attribute gets after being parsed and computed according to specifications. It may differ from the value that is actually written in the HTML code due to trimming whitespace or non-digits characters, default values, or case-insensitivity.

Some notable case of attribute value, among others:

For enumerated attributes, the attribute value is either the state of the attribute, or the keyword that maps to it; even for the default states. Thus <input type="image" /> has an attribute value of either Image Button (the state) or image (the keyword mapping to it), both formulations having the same meaning; similarly, “an input element with a type attribute value of Text” can be either <input type="text" />, <input /> (missing value default), or <input type="invalid" /> (invalid value default).
For boolean attributes, the attribute value is true when the attribute is present and false otherwise. Thus <button disabled>, <button disabled="disabled"> and <button disabled=""> all have a disabled attribute value of true.
For attributes whose value is used in a case-insensitive context, the attribute value is the lowercase version of the value written in the HTML code.
For attributes that accept numbers, the attribute value is the result of parsing the value written in the HTML code according to the rules for parsing this kind of number.
For attributes that accept sets of tokens, whether space separated or comma separated, the attribute value is the set of tokens obtained after parsing the set and, depending on the case, converting its items to lowercase (if the set is used in a case-insensitive context).
For aria-* attributes, the attribute value is computed as indicated in the WAI-ARIA specification and the HTML Accessibility API Mappings.

This list is not exhaustive, and only serves as an illustration for some of the most common cases.

The attribute value of an IDL attribute is the value returned on getting it. Note that when an IDL attribute reflects a content attribute, they have the same attribute value.

Outcome

An outcome is a conclusion that comes from evaluating an ACT Rule on a test subject or one of its constituent test target. An outcome can be one of the three following types:

Inapplicable: No part of the test subject matches the applicability
Passed: A test target meets all expectations
Failed: A test target does not meet all expectations

Note: A rule has one passed or failed outcome for every test target. When there are no test targets the rule has one inapplicable outcome. This means that each test subject will have one or more outcomes.

Note: Implementations using the EARL10-Schema can express the outcome with the outcome property. In addition to passed, failed and inapplicable, EARL 1.0 also defined an incomplete outcome. While this cannot be the outcome of an ACT Rule when applied in its entirety, it often happens that rules are only partially evaluated. For example, when applicability was automated, but the expectations have to be evaluated manually. Such “interim” results can be expressed with the incomplete outcome.

Visible

Content perceivable through sight.

Content is considered visible if making it fully transparent would result in a difference in the pixels rendered for any part of the document that is currently within the viewport or can be brought into the viewport via scrolling.

Content is defined in WCAG.

For more details, see examples of visible.

Implementations

This section is not part of the official rule. It is populated dynamically and not accounted for in the change history or the last modified date.

Implementation	Consistency	Complete	Report
Alfa	Consistent	No	View Report
Axe-core	Consistent	Yes	View Report
QualWeb	Consistent	Yes	View Report
SortSite	Consistent	No	View Report

Changelog

This is the first version of this ACT rule.