Accessibility Test Cases

A11Y-ZOOM-006

Two-dimensional layout exception

Generated file current Authoring: Content complete
What file status means

This status reports only whether the generated procedure matches the current controlled source hash. It is not independent content verification, regulatory approval, product evidence or a conformance decision.

Recorded standards review: No optional specialist review recorded. Next review: Not scheduled.

MethodZoom and reflow check
TesterGeneral QA tester
Indicative effort43–62 min small scope

Checks two-dimensional layout exception using real browser or operating-system controls.

Available formats

Use this test in the format you need

The HTML procedure includes the working worksheet. JSON provides the structured source data. Editable Markdown files are delivered inside package downloads.

Purpose

What this test checks

Checks two-dimensional layout exception using real browser or operating-system controls.

What this result means: This procedure records how Two-dimensional layout exception behaves on desktop-zoom-reflow. It can expose evidence relevant to WCAG 1.4.10 for the tested task and environment. Use the linked conformance procedures for WCAG 1.4.10 to assess the complete requirements across the declared conformance scope.

Why it matters

Checks two-dimensional layout exception using real browser or operating-system controls. People most likely affected: people with low vision who enlarge text or content and people who use narrow viewports. Content, controls, focus or validation may be clipped, overlap or require avoidable two-dimensional scrolling. In the recorded desktop-zoom-reflow environment, inspect navigation, dialogs, validation, sticky regions and horizontal movement at the required magnification; clipped or overlapping content can remove both information and operable controls.

When to use it

Apply Two-dimensional layout exception when the frozen page or document presentation at the genuine zoom, viewport and text settings named by the procedure. The selected focus is Two-dimensional layout exception.

Confirm before starting

Mark it not applicable only when

Exceptions

Two-dimensional layout required for usage or meaning

Decision condition
The specific content requires a two-dimensional layout for its usage or meaning; only that content is excepted from one-dimensional reflow.
Evidence needed
Identify the exact region, its task or meaning, and why one-dimensional presentation would invalidate it; verify surrounding content still reflows.
Common error
Complexity, width, a toolbar or developer preference does not automatically make the whole page an exception.
Scope
Only the qualifying two-dimensional region.

Prepare

What you need

  • The product area and test targets are agreed before testing starts.
  • The operating system, browser, viewport and input method are recorded.
  • Test data is safe to use and does not expose unnecessary personal information.

Targets and required variations

  • Each selected page, component and state relevant to Two-dimensional layout exception.
  • Default, revealed, loading, empty, validation error, interruption, recovery and confirmation where meaningful.
  • Every required environment, viewport, orientation, language and authenticated state recorded in the frozen scope.

Clean state

  • Complete a known-good calibration in the same environment before product testing.
  • Start from a recorded clean or known state and preserve any prior preferences, extensions, cache or profile settings that can affect output.

Effort estimate

Setup
12 min
Per target
15 min
Evidence
8 min
Technical review
8 min

Assumptions: one responsive page at the required zoom or viewport settings; repeat for fixed regions and breakpoint-specific layouts

Variation: Add a new per-target execution and evidence allowance for each additional target class or state that could produce a different result. Add setup time for each distinct environment.

Excluded: Client coordination, inaccessible-environment recovery, recruitment, legal review, remediation implementation and waiting time unless the procedure states otherwise.

Execute

Test steps

Follow each action in order. The expected result is always visible; open the guidance when you need setup, tool, evidence, decision or repeat details. Step-level recording is optional while work is in progress and required only to export a completed execution.

Step 1

Prepare the scope, target and environment

Purpose: For Two-dimensional layout exception, prepare the named scenario: Prepare the scope, target and environment. Target: Each selected page, component and state relevant to Two-dimensional layout exception. The preparation must establish this result: The selected targets, states, test data, environment and any scope limitations are complete enough for another qualified tester to reproduce the setup.

User impact: Content, controls, focus or validation may be clipped, overlap or require avoidable two-dimensional scrolling. This scenario isolates that risk in the action named Prepare the scope, target and environment.

Before executing Two-dimensional layout exception, freeze the product version and scope. Inventory each applicable target, select the required starting states, prepare safe test data and record every required environment value. Complete any named known-good calibration before attributing an observation to the product.

Expected result

The selected targets, states, test data, environment and any scope limitations are complete enough for another qualified tester to reproduce the setup.

Failure observation

During Two-dimensional layout exception, the target, starting state, environment or scope record remains ambiguous for the scenario named Prepare the scope, target and environment. The preparation result cannot be demonstrated: The selected targets, states, test data, environment and any scope limitations are complete enough for another qualified tester to reproduce the setup.

Setup, evidence and decision guidance
Target
Each selected page, component and state relevant to Two-dimensional layout exception.
Required state
For Two-dimensional layout exception, the product version and scope are frozen; every selected target and material starting state is uniquely identified.
Tool or command
Use the scope record and worksheet environment fields for Two-dimensional layout exception: operating_system, operating_system_version, browser, browser_version, viewport_css_pixels, input_method, zoom_level.
Record
Scope/version reference; target inventory; starting states; safe-data reference; every required environment value; calibration result or reason it is not required.
Pass
Record passed for the Two-dimensional layout exception scenario named Prepare the scope, target and environment only when the evidence (Scope/version reference; target inventory; starting states; safe-data reference; every required environment value; calibration result or reason it is not required.) supports: The selected targets, states, test data, environment and any scope limitations are complete enough for another qualified tester to reproduce the setup.
Fail
Record failed when the action is completed and this failure observation is reproduced: During Two-dimensional layout exception, the target, starting state, environment or scope record remains ambiguous for the scenario named Prepare the scope, target and environment. The preparation result cannot be demonstrated: The selected targets, states, test data, environment and any scope limitations are complete enough for another qualified tester to reproduce the setup.
Not applicable
The frozen scope contains no content or state to which Two-dimensional layout exception can be applied.
Blocked
Record blocked, not passed, when An applicable target, required state, complete process or named real environment was not executed.
Repeat or recover
For Two-dimensional layout exception, correct the setup gap, preserve the original blocked record and start a new execution observation before proceeding.
Limitations
This scenario records the action named Prepare the scope, target and environment for Two-dimensional layout exception in desktop-zoom-reflow. It does not establish behaviour for another target, state or environment and does not set a WCAG conformance decision.
If you are new to this test
For Two-dimensional layout exception, do not begin from an undocumented browser tab, document copy, device state, participant plan or evidence set. Record the exact item you will test first.
Record this step

Step 2

At 400%, inspect data tables, diagrams, maps, games and other claimed exceptions

Purpose: For Two-dimensional layout exception, execute the named scenario: At 400%, inspect data tables, diagrams, maps, games and other claimed exceptions. Target: Each selected page, component and state relevant to Two-dimensional layout exception. Compare the observation with this result: Only content whose meaning requires two dimensions scrolls in two dimensions, and surrounding content still reflows.

User impact: Content, controls, focus or validation may be clipped, overlap or require avoidable two-dimensional scrolling. This scenario isolates that risk in the action named At 400%, inspect data tables, diagrams, maps, games and other claimed exceptions.

At 400%, inspect data tables, diagrams, maps, games and other claimed exceptions; isolate the exception and test surrounding content and available alternatives.

Expected result

Only content whose meaning requires two dimensions scrolls in two dimensions, and surrounding content still reflows.

Failure observation

After the tester completes the Two-dimensional layout exception scenario named At 400%, inspect data tables, diagrams, maps, games and other claimed exceptions, the recorded observation for the target is inconsistent with the required result: Only content whose meaning requires two dimensions scrolls in two dimensions, and surrounding content still reflows.

Setup, evidence and decision guidance
Target
Each selected page, component and state relevant to Two-dimensional layout exception.
Required state
For Two-dimensional layout exception, begin in keyboard focus on the last confirmed target before the action, with no pointer assistance; preserve the exact content, account, platform and configuration used.
Tool or command
In desktop-zoom-reflow, Use the browser's genuine zoom control and measure the resulting CSS-pixel viewport; use text-only zoom only when the action explicitly asks for it. Developer-tool emulation may diagnose a defect but is not execution evidence.
Record
Exact two-dimensional-layout target and evidence that its use or meaning requires that presentation. Capture full-page and viewport evidence at the actual zoom level, including any exempt two-dimensional region and its justification.
Pass
Record passed for the Two-dimensional layout exception scenario named At 400%, inspect data tables, diagrams, maps, games and other claimed exceptions only when the evidence (Exact two-dimensional-layout target and evidence that its use or meaning requires that presentation. Capture full-page and viewport evidence at the actual zoom level, including any exempt two-dimensional region and its justification.) supports: Only content whose meaning requires two dimensions scrolls in two dimensions, and surrounding content still reflows.
Fail
Record failed when the action is completed and this failure observation is reproduced: After the tester completes the Two-dimensional layout exception scenario named At 400%, inspect data tables, diagrams, maps, games and other claimed exceptions, the recorded observation for the target is inconsistent with the required result: Only content whose meaning requires two dimensions scrolls in two dimensions, and surrounding content still reflows.
Not applicable
The frozen scope contains no content or state to which Two-dimensional layout exception can be applied.
Blocked
Record blocked, not passed, when An applicable target, required state, complete process or named real environment was not executed.
Repeat or recover
Repeat on each representative template and in opened menus, dialogs, errors, sticky regions and other states that can change layout. Preserve the first Two-dimensional layout exception observation when repeating.
Limitations
This scenario records the action named At 400%, inspect data tables, diagrams, maps, games and other claimed exceptions for Two-dimensional layout exception in desktop-zoom-reflow. It does not establish behaviour for another target, state or environment and does not set a WCAG conformance decision.
If you are new to this test
For Two-dimensional layout exception: Record the starting viewport, browser zoom, operating-system scale and resulting CSS viewport before judging clipping or two-dimensional scrolling.
Record this step

Step 3

Inspect top, middle and end of every representative page and complete critical success, error and recovery journeys using keyboard and pointer

Purpose: For Two-dimensional layout exception, execute the named scenario: Inspect top, middle and end of every representative page and complete critical success, error and recovery journeys using keyboard and pointer. Target: Each selected page, component and state relevant to Two-dimensional layout exception. Compare the observation with this result: No off-screen, clipped or unreachable content is missed by a static screenshot.

User impact: Content, controls, focus or validation may be clipped, overlap or require avoidable two-dimensional scrolling. This scenario isolates that risk in the action named Inspect top, middle and end of every representative page and complete critical success, error and recovery journeys using keyboard and pointer.

Inspect top, middle and end of every representative page and complete critical success, error and recovery journeys using keyboard and pointer.

Expected result

No off-screen, clipped or unreachable content is missed by a static screenshot.

Failure observation

After the tester completes the Two-dimensional layout exception scenario named Inspect top, middle and end of every representative page and complete critical success, error and recovery journeys using keyboard and pointer, the recorded observation for the target is inconsistent with the required result: No off-screen, clipped or unreachable content is missed by a static screenshot.

Setup, evidence and decision guidance
Target
Each selected page, component and state relevant to Two-dimensional layout exception.
Required state
For Two-dimensional layout exception, begin in the validation-error state immediately after submitting representative invalid input; preserve the exact content, account, platform and configuration used.
Tool or command
In desktop-zoom-reflow, Use the browser's genuine zoom control and measure the resulting CSS-pixel viewport; use text-only zoom only when the action explicitly asks for it. Developer-tool emulation may diagnose a defect but is not execution evidence.
Record
Viewport and full-page evidence for default, revealed, validation, sticky and dialog states. Capture full-page and viewport evidence at the actual zoom level, including any exempt two-dimensional region and its justification.
Pass
Record passed for the Two-dimensional layout exception scenario named Inspect top, middle and end of every representative page and complete critical success, error and recovery journeys using keyboard and pointer only when the evidence (Viewport and full-page evidence for default, revealed, validation, sticky and dialog states. Capture full-page and viewport evidence at the actual zoom level, including any exempt two-dimensional region and its justification.) supports: No off-screen, clipped or unreachable content is missed by a static screenshot.
Fail
Record failed when the action is completed and this failure observation is reproduced: After the tester completes the Two-dimensional layout exception scenario named Inspect top, middle and end of every representative page and complete critical success, error and recovery journeys using keyboard and pointer, the recorded observation for the target is inconsistent with the required result: No off-screen, clipped or unreachable content is missed by a static screenshot.
Not applicable
The frozen scope contains no content or state to which Two-dimensional layout exception can be applied.
Blocked
Record blocked, not passed, when An applicable target, required state, complete process or named real environment was not executed.
Repeat or recover
Repeat on each representative template and in opened menus, dialogs, errors, sticky regions and other states that can change layout. Preserve the first Two-dimensional layout exception observation when repeating.
Limitations
This scenario records the action named Inspect top, middle and end of every representative page and complete critical success, error and recovery journeys using keyboard and pointer for Two-dimensional layout exception in desktop-zoom-reflow. It does not establish behaviour for another target, state or environment and does not set a WCAG conformance decision.
If you are new to this test
For Two-dimensional layout exception: Record the starting viewport, browser zoom, operating-system scale and resulting CSS viewport before judging clipping or two-dimensional scrolling.
Record this step

Decide

How to decide

Passed

Only content whose meaning requires two dimensions scrolls in two dimensions, and surrounding content still reflows.

Failed

An applicable Two-dimensional layout exception target has a reproducible material barrier against one or more stated expectations; identify the exact expectation, state and evidence.

Not applicable
The frozen scope contains no content or state to which Two-dimensional layout exception can be applied.
Cannot tell
The target is applicable, but conflicting evidence or unresolved responsibility prevents a defensible expectation decision after recorded comparison.
Not tested
An applicable target, required state, complete process or named real environment was not executed.
Aggregation and reporting boundaries

Aggregation: Preserve every target/environment outcome. Any failed target prevents an overall passed procedure result. cantTell and untested remain unresolved; inapplicable is valid only when the completed inventory contains no applicable target.

WCAG decision: This specialist, platform, document, usability or quality result does not set a WCAG success criterion to satisfied or not_satisfied automatically. Use linked atomic and criterion-level procedures for that separate decision.

Automation: A checker, accessibility-tree inspection, emulator or simulated assistive technology is diagnostic evidence only. Complete every required manual, real-platform, contextual and exception check.

Record

Record the result

Record the target, state and observed behaviour. Add evidence or technical details only when needed.

Choose the option that best matches what happened to this target.

Describe the actual behaviour and why it supports the selected result.

When more than one target is recorded, the overall procedure result is calculated from all target results.

Environment: Not set.
Add evidence or details

Choose only the group needed for this record. These fields remain optional for a working draft.

Evidence references

Enter one file name, issue ID or evidence reference per line. Files stay on your device.

Test environment

Save a named profile once to reuse the same product, platform and environment details on other procedures in this browser.

Engagement and tester identifiers

Formal completion and limitations

Identify the frozen list or sampling record used to select every target represented by this execution.

Choose a final result before marking the execution complete. Completed records require the full environment, step, evidence and method-specific information.

Data management

Export before clearing if the record must be retained. Apply the engagement retention schedule and delete browser data when it is no longer needed.

Saved drafts stay in this browser and are not uploaded. Do not enter credentials, secrets or unnecessary personal data.

Reference

Supporting information

Standards and requirement mappings
  • W3C-WCAG22 · 1.4.10 secondary · partial

    This Zoom and reflow check observes Two-dimensional layout exception in the recorded desktop-zoom-reflow environment. Use the linked WCAG 1.4.10 conformance procedure to evaluate all normative parts of WCAG 1.4.10 across the declared scope.

  • W3C-RESIZE-TEXT · W3C-RESIZE-TEXT advisory · supporting

    This source does not override WCAG or create an additional WCAG conformance requirement.

  • W3C-REFLOW · W3C-REFLOW advisory · supporting

    This source does not override WCAG or create an additional WCAG conformance requirement.

  • MICROSOFT-EDGE-A11Y · MICROSOFT-EDGE-A11Y advisory · supporting

    This source does not override WCAG or create an additional WCAG conformance requirement.

  • W3C-WCAG22-TECHNIQUES · W3C-WCAG22-TECHNIQUES advisory · supporting

    This source does not override WCAG or create an additional WCAG conformance requirement.

Supporting and advisory guidance

Supporting sources are identified in the mappings and source register. They do not add conformance requirements.

Evidence specification
  • Presentation measurement

    Starting viewport, resulting CSS viewport, genuine zoom/text setting, orientation and operating-system scale.

    Reference or redact sensitive material. Do not store credentials, secrets, unnecessary personal data or unconsented participant data.

  • Visual record

    Viewport and full-page evidence for default, revealed, validation, sticky and dialog states.

    Reference or redact sensitive material. Do not store credentials, secrets, unnecessary personal data or unconsented participant data.

  • Exception record

    Exact two-dimensional-layout target and evidence that its use or meaning requires that presentation.

    Reference or redact sensitive material. Do not store credentials, secrets, unnecessary personal data or unconsented participant data.

Worked example and outcome calibration

A11Y-ZOOM-006-WORKED-001: representative worked example

Context: Representative synthetic example for Two-dimensional layout exception on a fictional, version-frozen product target; no client or participant execution occurred.

Inspected: The tester follows S2 (At 400%, inspect data tables, diagrams, maps, games and other claimed exceptions) using the target, required state, tool and repeat rule stated in this procedure.

Observed output: After the tester completes the Two-dimensional layout exception scenario named At 400%, inspect data tables, diagrams, maps, games and other claimed exceptions, the recorded observation for the target is inconsistent with the required result: Only content whose meaning requires two dimensions scrolls in two dimensions, and surrounding content still reflows.

Evidence:

  • example-evidence-001: target and state record for Each selected page, component and state relevant to Two-dimensional layout exception.
  • example-evidence-002: contemporaneous observation from the named method — Exact two-dimensional-layout target and evidence that its use or meaning requires that presentation. Capture full-page and viewport evidence at the actual zoom level, including any exempt two-dimensional region and its justification.
  • example-evidence-003: comparison note linking the actual observation to the expected result and claim boundary

Tester reasoning: The recorded observation does not demonstrate the expected result: Only content whose meaning requires two dimensions scrolls in two dimensions, and surrounding content still reflows. The failed decision is limited to this synthetic target and state; unexecuted coverage is not inferred.

Decision: failed

Finding: A11Y-ZOOM-006-example-finding-001 — Two-dimensional layout exception: expected result is not demonstrated. The represented barrier may affect People with low vision who enlarge text or content and people who use narrow viewports.

Remediation: Change the represented target or process so it demonstrates this result: Only content whose meaning requires two dimensions scrolls in two dimensions, and surrounding content still reflows. Then rerun the affected step and every dependent variation.

Reviewer feedback: The reviewer confirms applicability, environment, actual-versus-expected comparison, evidence references and bounded wording; unsupported product-wide or conformance language is removed.

Final client wording: Synthetic training finding: the sampled Two-dimensional layout exception target does not meet the procedure expectation in the recorded state. User impact and broader scope require evidence from the buyer's real execution.

Retest: Synthetic retest example: after the represented change, repeat the failed step plus material error and recovery states. Close the finding only when new evidence demonstrates the expected result; otherwise retain the non-pass outcome.

Boundary: This is a representative, synthetic worked example for training and calibration. It is not evidence from a client product, participant or real assistive-technology execution.

Outcome calibration

Passed
In desktop-zoom-reflow, the selected Two-dimensional layout exception target completes the recorded action and meets this expectation: Only content whose meaning requires two dimensions scrolls in two dimensions, and surrounding content still reflows.

The example is a calibration scenario, not an execution or approval.

Failed
An applicable Two-dimensional layout exception target produces a reproducible barrier during the named action, with the exact state and affected user task recorded.

A failed target remains failed even if another environment or target passes.

Not applicable
The frozen scope contains no content or state to which Two-dimensional layout exception can be applied.

Inapplicable requires a completed inventory showing that no target matches applicability; a missing environment is not inapplicable.

Cannot tell
The Two-dimensional layout exception target is applicable, but conflicting product/platform evidence or missing authoritative information prevents a defensible responsibility or expectation decision.

Record the conflict, comparisons attempted and person or evidence needed to resolve it.

Not tested
The Two-dimensional layout exception target is applicable, but a required state, complete process or real environment was not executed.

Untested remains incomplete and cannot be converted to passed or inapplicable.

Sampling, complete processes and platform limitations

Test every in-scope instance when practical. For a large population, document a sample that includes each template, content or control type, meaningful state and high-risk task.

If this check is part of a user journey, test the selected journey from start to finish, including relevant errors and recovery. Record any path that was not tested.

  • Emulation can support diagnosis but does not replace the genuine browser or operating-system presentation required by the procedure.
  • Check relevant browser, tool or assistive-technology release notes before assigning unexpected behaviour to the product.
  • If responsibility is unclear, record the reproducible behaviour and use cannot tell until it is resolved.
Related procedures
  • A11Y-WCAG-017
ACT rules and WCAG technique traceability

This is a project-authored manual procedure, not a W3C Approved ACT Rule. An ACT result can support only the part of this procedure covered by that rule. It does not replace the remaining manual or assistive-technology checks.

No supporting W3C Approved ACT Rule is selected for this procedure.

  • Understanding SC 1.4.10. Techniques are examples, not extra requirements. Record any technique or common failure used, but decide the result against the success criterion.
Review history and source register
  1. 2026.08.27-rc.9 — Reworked for plain language, case-focused steps, scoped evidence and transparent draft review status.
  2. 2026.08.27-rc.9 — Migrated to professional catalogue schema v3 with separated outcomes, structured authority, applicability, evidence, decision and review records.
  3. 2026.08.27-rc.9 — Specialist procedure mapped to its task family and current first-party platform guidance and checked for internal consistency; competent review and real execution remain separate.
  4. 2026.08.27-rc.9 — Added explicit preparation and variation/recovery steps plus a bounded representative worked example for paid-template use.
  5. 2026.08.27-rc.9 — Procedure guidance and presentation simplified without changing draft governance status.

Review decision: pending. Open issues: Execute all required real environments and calibration cases.; Complete a distinct competent review and retain any unresolved material finding as blocked or cantTell.

Source historyReport an accuracy issue
WCAG
SC 1.4.10
Execution
Manual test with tool support
Catalogue version
2026.08.27-rc.9