Accessibility Test Cases

A11Y-WCAG-017

WCAG 1.4.10 Reflow

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.

MethodWCAG check
TesterAccessibility tester
Indicative effort33–48 min small scope

At 400% browser zoom, check vertical content at 320 CSS pixels wide and horizontal content at 256 CSS pixels high.

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

At 400% browser zoom, check vertical content at 320 CSS pixels wide and horizontal content at 256 CSS pixels high.

What this result means: This WCAG 1.4.10 Reflow procedure determines whether the recorded targets meet WCAG 1.4.10 on web-desktop-cross-browser in the tested states. A broader conformance decision must also account for every applicable target in the declared scope, complete processes, accessibility-supported use and the other WCAG conformance requirements.

Why it matters

Detect content or controls that require two-dimensional scrolling, become clipped, overlap or disappear when enlarged. People most likely affected: people with low vision who use browser zoom; People who need a narrow viewport or enlarged interface. Users may lose information, controls, validation, navigation or task completion when content reflows. In the recorded web-desktop-cross-browser environment, apply the criterion to every relevant state and named normative exception; failures in critical tasks and complete processes carry the greatest user impact.

When to use it

Apply to web content at the specified equivalents. Isolate only content that genuinely requires a two-dimensional layout; do not exempt the whole page.

Confirm before starting

Mark it not applicable only when

Exceptions

Two-dimensional layout required

Decision condition
A specific content region requires two-dimensional layout for usage or meaning, such as a map, diagram, video, game, presentation, data table or interface that must keep a toolbar visible while manipulating content.
Evidence needed
Region identifier, function/meaning, both-axis dependency and evidence showing why one-dimensional reflow would remove meaning or operation.
Common error
Complexity, wide design, developer effort or the presence of any table does not exempt the entire page.
Scope
Only the qualifying content region; surrounding information and functionality remain subject to reflow.

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

  • Vertically scrolling content at a width equivalent to 320 CSS pixels.
  • Horizontally scrolling content at a height equivalent to 256 CSS pixels.
  • Default, sticky-header/footer, menus, dialogs, validation, long-string, loading, error, recovery and confirmation states.
  • Every selected responsive template and critical complete process.

Clean state

  • Start from a documented clean or known state and record pre-existing preferences, extensions and cached data that can change the result.

Effort estimate

Setup
10 min
Per target
8 min
Evidence
7 min
Technical review
8 min

Assumptions: one page or component state; add another execution block for each materially different template or state

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

Freeze pages, states and starting viewports

Purpose: For WCAG 1.4.10 Reflow, prepare the named scenario: Freeze pages, states and starting viewports. Target: Both reflow targets. The preparation must establish this result: The starting viewport equivalents and selected state inventory are reproducible.

User impact: Users may lose information, controls, validation, navigation or task completion when content reflows. This scenario isolates that risk in the action named Freeze pages, states and starting viewports.

Record every selected page, complete-process step and meaningful state. For the common 400% method, prepare a 1280 CSS-pixel-wide starting viewport for the 320-width branch and a 1024 CSS-pixel-high starting viewport for the 256-height branch.

Expected result

The starting viewport equivalents and selected state inventory are reproducible.

Failure observation

During WCAG 1.4.10 Reflow, the target, starting state, environment or scope record remains ambiguous for the scenario named Freeze pages, states and starting viewports. The preparation result cannot be demonstrated: The starting viewport equivalents and selected state inventory are reproducible.

Setup, evidence and decision guidance
Target
Both reflow targets.
Required state
Browser at 100% before each branch; browser chrome and OS scaling recorded.
Tool or command
Browser viewport measurement and genuine browser zoom controls.
Record
Browser/version, OS scaling, starting CSS viewport, page/state and process step.
Pass
Record passed for the WCAG 1.4.10 Reflow scenario named Freeze pages, states and starting viewports only when the evidence (Browser/version, OS scaling, starting CSS viewport, page/state and process step.) supports: The starting viewport equivalents and selected state inventory are reproducible.
Fail
Record failed when the action is completed and this failure observation is reproduced: During WCAG 1.4.10 Reflow, the target, starting state, environment or scope record remains ambiguous for the scenario named Freeze pages, states and starting viewports. The preparation result cannot be demonstrated: The starting viewport equivalents and selected state inventory are reproducible.
Not applicable
No web content exists in the selected subject.
Blocked
Record blocked, not passed, when The target is applicable, but a required state, environment, action or evidence item was not completed.
Repeat or recover
Reset zoom and viewport before switching branches.
Limitations
This WCAG 1.4.10 Reflow scenario covers only the action named Freeze pages, states and starting viewports for the recorded target and state. It contributes evidence to 1.4.10; apply the procedure's aggregation, complete-process and conformance-scope rules before making a broader decision.
If you are new to this test
Device emulation can help diagnosis, but the reference execution uses genuine browser zoom unless an equivalent method is justified and recorded.
Record this step

Step 2

Test the 320 CSS-pixel-width branch

Purpose: For WCAG 1.4.10 Reflow, execute the named scenario: Test the 320 CSS-pixel-width branch. Target: Vertically scrolling content at a width equivalent to 320 CSS pixels. Compare the observation with this result: Information and functionality remain available, and applicable content needs only vertical scrolling.

User impact: Users may lose information, controls, validation, navigation or task completion when content reflows. This scenario isolates that risk in the action named Test the 320 CSS-pixel-width branch.

At a 1280 CSS-pixel-wide starting viewport, apply genuine 400% browser zoom to obtain the 320 CSS-pixel-width equivalent. Read and operate vertically scrolling content without horizontal page scrolling, except within a documented two-dimensional region.

Expected result

Information and functionality remain available, and applicable content needs only vertical scrolling.

Failure observation

After the tester completes the WCAG 1.4.10 Reflow scenario named Test the 320 CSS-pixel-width branch, the recorded observation for the target is inconsistent with the required result: Information and functionality remain available, and applicable content needs only vertical scrolling.

Setup, evidence and decision guidance
Target
Vertically scrolling content at a width equivalent to 320 CSS pixels.
Required state
Each selected state at the 320 CSS-pixel-width equivalent.
Tool or command
Genuine browser zoom, keyboard and pointer or the input modes required by the process.
Record
Viewport/zoom evidence, screenshots, horizontal-overflow location and task result.
Pass
Record passed for the WCAG 1.4.10 Reflow scenario named Test the 320 CSS-pixel-width branch only when the evidence (Viewport/zoom evidence, screenshots, horizontal-overflow location and task result.) supports: Information and functionality remain available, and applicable content needs only vertical scrolling.
Fail
Record failed when the action is completed and this failure observation is reproduced: After the tester completes the WCAG 1.4.10 Reflow scenario named Test the 320 CSS-pixel-width branch, the recorded observation for the target is inconsistent with the required result: Information and functionality remain available, and applicable content needs only vertical scrolling.
Not applicable
No web content exists in the selected subject.
Blocked
Record blocked, not passed, when The target is applicable, but a required state, environment, action or evidence item was not completed.
Repeat or recover
Repeat for each responsive template and state; reload only when documented because reload can change responsive behaviour.
Limitations
This WCAG 1.4.10 Reflow scenario covers only the action named Test the 320 CSS-pixel-width branch for the recorded target and state. It contributes evidence to 1.4.10; apply the procedure's aggregation, complete-process and conformance-scope rules before making a broader decision.
If you are new to this test
Check the full document width and every opened layer, not just the initially visible region.
Record this step

Step 3

Test the 256 CSS-pixel-height branch

Purpose: For WCAG 1.4.10 Reflow, execute the named scenario: Test the 256 CSS-pixel-height branch. Target: Horizontally scrolling content at a height equivalent to 256 CSS pixels. Compare the observation with this result: Information and functionality remain available, and applicable content needs only horizontal scrolling.

User impact: Users may lose information, controls, validation, navigation or task completion when content reflows. This scenario isolates that risk in the action named Test the 256 CSS-pixel-height branch.

At a 1024 CSS-pixel-high starting viewport, apply genuine 400% browser zoom to obtain the 256 CSS-pixel-height equivalent. Read and operate horizontally scrolling content without vertical page scrolling, except within a documented two-dimensional region.

Expected result

Information and functionality remain available, and applicable content needs only horizontal scrolling.

Failure observation

After the tester completes the WCAG 1.4.10 Reflow scenario named Test the 256 CSS-pixel-height branch, the recorded observation for the target is inconsistent with the required result: Information and functionality remain available, and applicable content needs only horizontal scrolling.

Setup, evidence and decision guidance
Target
Horizontally scrolling content at a height equivalent to 256 CSS pixels.
Required state
Each selected horizontally scrolling presentation at the 256 CSS-pixel-height equivalent.
Tool or command
Genuine browser zoom and the inputs required by the content.
Record
Viewport/zoom evidence, screenshots, vertical-overflow location and task result.
Pass
Record passed for the WCAG 1.4.10 Reflow scenario named Test the 256 CSS-pixel-height branch only when the evidence (Viewport/zoom evidence, screenshots, vertical-overflow location and task result.) supports: Information and functionality remain available, and applicable content needs only horizontal scrolling.
Fail
Record failed when the action is completed and this failure observation is reproduced: After the tester completes the WCAG 1.4.10 Reflow scenario named Test the 256 CSS-pixel-height branch, the recorded observation for the target is inconsistent with the required result: Information and functionality remain available, and applicable content needs only horizontal scrolling.
Not applicable
No web content exists in the selected subject.
Blocked
Record blocked, not passed, when The target is applicable, but a required state, environment, action or evidence item was not completed.
Repeat or recover
Run this branch for content designed to scroll horizontally; do not omit it merely because most pages scroll vertically.
Limitations
This WCAG 1.4.10 Reflow scenario covers only the action named Test the 256 CSS-pixel-height branch for the recorded target and state. It contributes evidence to 1.4.10; apply the procedure's aggregation, complete-process and conformance-scope rules before making a broader decision.
If you are new to this test
The height branch is a separate normative branch, not optional wording attached to the width test.
Record this step

Step 4

Exercise obstruction and critical states

Purpose: For WCAG 1.4.10 Reflow, execute the named scenario: Exercise obstruction and critical states. Target: Every applicable target in the selected process. Compare the observation with this result: No information or function is clipped, overlapped, hidden behind sticky content or made unreachable.

User impact: Users may lose information, controls, validation, navigation or task completion when content reflows. This scenario isolates that risk in the action named Exercise obstruction and critical states.

At the relevant equivalent, open sticky content, navigation, dialogs and menus; trigger validation; test long unbroken strings; and complete critical success, interruption, recovery and confirmation paths.

Expected result

No information or function is clipped, overlapped, hidden behind sticky content or made unreachable.

Failure observation

After the tester completes the WCAG 1.4.10 Reflow scenario named Exercise obstruction and critical states, the recorded observation for the target is inconsistent with the required result: No information or function is clipped, overlapped, hidden behind sticky content or made unreachable.

Setup, evidence and decision guidance
Target
Every applicable target in the selected process.
Required state
Both reflow equivalents where the content's scrolling direction makes them applicable.
Tool or command
Keyboard plus any other input required by the process; browser layout inspection for overflow diagnosis.
Record
State, action, viewport, affected content, actual result and screenshot or recording.
Pass
Record passed for the WCAG 1.4.10 Reflow scenario named Exercise obstruction and critical states only when the evidence (State, action, viewport, affected content, actual result and screenshot or recording.) supports: No information or function is clipped, overlapped, hidden behind sticky content or made unreachable.
Fail
Record failed when the action is completed and this failure observation is reproduced: After the tester completes the WCAG 1.4.10 Reflow scenario named Exercise obstruction and critical states, the recorded observation for the target is inconsistent with the required result: No information or function is clipped, overlapped, hidden behind sticky content or made unreachable.
Not applicable
No web content exists in the selected subject.
Blocked
Record blocked, not passed, when The target is applicable, but a required state, environment, action or evidence item was not completed.
Repeat or recover
Repeat this action for every required variation of Check reflow in both scrolling directions and after a material target, content, state, environment or configuration change. Preserve the original observation.
Limitations
This WCAG 1.4.10 Reflow scenario covers only the action named Exercise obstruction and critical states for the recorded target and state. It contributes evidence to 1.4.10; apply the procedure's aggregation, complete-process and conformance-scope rules before making a broader decision.
If you are new to this test
A page can avoid a scrollbar yet still fail because content is clipped or controls are obscured.
Record this step

Step 5

Repeat material variations and recovery

Purpose: For WCAG 1.4.10 Reflow, execute the named scenario: Repeat material variations and recovery. Target: Both reflow targets. Compare the observation with this result: Every material variation and required recovery path has its own reproducible observation; no unexecuted state is merged into a passing result.

User impact: Users may lose information, controls, validation, navigation or task completion when content reflows. This scenario isolates that risk in the action named Repeat material variations and recovery.

Repeat the WCAG 1.4.10 Reflow action for each inventoried variation that can change the outcome. Include relevant default, revealed, error, interruption, recovery and confirmation states and complete the selected process from start to finish where this test can affect task completion.

Expected result

Every material variation and required recovery path has its own reproducible observation; no unexecuted state is merged into a passing result.

Failure observation

After the tester completes the WCAG 1.4.10 Reflow scenario named Repeat material variations and recovery, the recorded observation for the target is inconsistent with the required result: Every material variation and required recovery path has its own reproducible observation; no unexecuted state is merged into a passing result.

Setup, evidence and decision guidance
Target
Both reflow targets.
Required state
For WCAG 1.4.10 Reflow: Default, sticky-header/footer, menus, dialogs, validation, long-string, loading, error, recovery and confirmation states. Every selected responsive template and critical complete process.
Tool or command
For WCAG 1.4.10 Reflow, use the same recorded method, then change only the state, environment or recovery condition being compared.
Record
Variation identifier; changed state or environment; start and end points; actual observation; recovery result; intervention; evidence reference and target outcome.
Pass
Record passed for the WCAG 1.4.10 Reflow scenario named Repeat material variations and recovery only when the evidence (Variation identifier; changed state or environment; start and end points; actual observation; recovery result; intervention; evidence reference and target outcome.) supports: Every material variation and required recovery path has its own reproducible observation; no unexecuted state is merged into a passing result.
Fail
Record failed when the action is completed and this failure observation is reproduced: After the tester completes the WCAG 1.4.10 Reflow scenario named Repeat material variations and recovery, the recorded observation for the target is inconsistent with the required result: Every material variation and required recovery path has its own reproducible observation; no unexecuted state is merged into a passing result.
Not applicable
No web content exists in the selected subject.
Blocked
Record blocked, not passed, when The target is applicable, but a required state, environment, action or evidence item was not completed.
Repeat or recover
Repeat this action for every required variation of Check reflow in both scrolling directions and after a material target, content, state, environment or configuration change. Preserve the original observation.
Limitations
This WCAG 1.4.10 Reflow scenario covers only the action named Repeat material variations and recovery for the recorded target and state. It contributes evidence to 1.4.10; apply the procedure's aggregation, complete-process and conformance-scope rules before making a broader decision.
If you are new to this test
For WCAG 1.4.10 Reflow, change one material condition at a time where practical. Do not assume that a passing default state covers errors, overlays, orientation changes, interruptions or recovery.
Record this step

Step 6

Decide each region and branch

Purpose: For WCAG 1.4.10 Reflow, complete the record for the scenario named Decide each region and branch and preserve evidence that demonstrates this result: The result shows which branch, region and process each decision covers.

User impact: Users may lose information, controls, validation, navigation or task completion when content reflows. This scenario isolates that risk in the action named Decide each region and branch.

Record outcomes separately for the width branch, height branch, each exceptional region and each selected complete process. Preserve cantTell and untested results.

Expected result

The result shows which branch, region and process each decision covers.

Failure observation

The WCAG 1.4.10 Reflow evidence or decision record for the scenario named Decide each region and branch does not demonstrate the required result: The result shows which branch, region and process each decision covers.

Setup, evidence and decision guidance
Target
Both reflow targets and any excepted region.
Required state
All selected states completed.
Tool or command
Execution worksheet and evidence references.
Record
Target outcomes, exception rationale, viewport evidence, limitations and issue references.
Pass
Record passed for the WCAG 1.4.10 Reflow scenario named Decide each region and branch only when the evidence (Target outcomes, exception rationale, viewport evidence, limitations and issue references.) supports: The result shows which branch, region and process each decision covers.
Fail
Record failed when the action is completed and this failure observation is reproduced: The WCAG 1.4.10 Reflow evidence or decision record for the scenario named Decide each region and branch does not demonstrate the required result: The result shows which branch, region and process each decision covers.
Not applicable
No web content exists in the selected subject.
Blocked
Record blocked, not passed, when The target is applicable, but a required state, environment, action or evidence item was not completed.
Repeat or recover
Reopen affected results after layout, browser-support or content changes.
Limitations
This WCAG 1.4.10 Reflow scenario covers only the action named Decide each region and branch for the recorded target and state. It contributes evidence to 1.4.10; apply the procedure's aggregation, complete-process and conformance-scope rules before making a broader decision.
If you are new to this test
Do not average a passing width branch with an untested height branch.
Record this step

Decide

How to decide

Passed

At the applicable 320 CSS-pixel-width and 256 CSS-pixel-height equivalents, information and functionality remain available without two-dimensional page scrolling, except within a specifically evidenced region that requires a two-dimensional layout for usage or meaning.

Failed

Applicable content requires scrolling in two dimensions, or information or functionality is clipped, overlaps, becomes obscured or is unavailable, and no two-dimensional-layout exception applies.

Not applicable
No web content exists in the selected subject.
Cannot tell
The viewport equivalent, overflow source or necessity of a two-dimensional layout cannot be determined after reasonable inspection.
Not tested
The target is applicable, but a required state, environment, action or evidence item was not completed.
Aggregation and reporting boundaries

Aggregation: Preserve results for both branches, every page/state and each excepted region. A failure prevents a passed aggregate; cantTell and untested remain unresolved.

WCAG decision: A satisfied WCAG 1.4.10 decision requires all applicable content in the conformance scope and all conformance requirements to be considered. Sampled results disclose their coverage limitations.

Automation: Automated overflow detection may identify candidates but cannot prove information/function availability or whether a two-dimensional layout is essential. A passed automated or ACT result must never set the criterion to satisfied automatically.

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

Component expectation results

Use these controls only when the procedure has distinct component expectations. The overall outcome must agree with them.

E1 Vertical content reflows at the 320 CSS-pixel-width equivalent without horizontal page scrolling or loss.

E2 Horizontal content reflows at the 256 CSS-pixel-height equivalent without vertical page scrolling or loss.

WCAG report decisions

These report-level decisions are separate from the target outcome and require complete declared-scope evidence.

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 conformance · full

    The two-dimensional-layout exception applies only to content that requires that layout for usage or meaning; surrounding content and controls remain applicable.

  • W3C-WCAG22-QUICKREF · W3C-WCAG22-QUICKREF 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.

  • 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
  • Viewport record

    Browser/version, OS scaling, starting CSS viewport and final 400% equivalent for both branches.

    Use a redacted extract or evidence reference. Do not include credentials, secrets or unnecessary personal data.

  • State and process record

    Selected pages, states, sticky layers, dialogs, validation, long strings and complete-process actions.

    Use a redacted extract or evidence reference. Do not include credentials, secrets or unnecessary personal data.

  • Visual and functional evidence

    Screenshots or recording showing overflow, clipping, overlap and task results.

    Use a redacted extract or evidence reference. Do not include credentials, secrets or unnecessary personal data.

  • Exception decision

    Region boundary, two-dimensional dependency and usage/meaning rationale.

    Use a redacted extract or evidence reference. Do not include credentials, secrets or unnecessary personal data.

Worked example and outcome calibration

A11Y-WCAG-017-WORKED-001: representative worked example

Context: Representative synthetic example for WCAG 1.4.10 Reflow on a fictional, version-frozen product target; no client or participant execution occurred.

Inspected: The tester follows S2 (Test the 320 CSS-pixel-width branch) using the target, required state, tool and repeat rule stated in this procedure.

Observed output: After the tester completes the WCAG 1.4.10 Reflow scenario named Test the 320 CSS-pixel-width branch, the recorded observation for the target is inconsistent with the required result: Information and functionality remain available, and applicable content needs only vertical scrolling.

Evidence:

  • example-evidence-001: target and state record for Vertically scrolling content at a width equivalent to 320 CSS pixels.
  • example-evidence-002: contemporaneous observation from the named method — Viewport/zoom evidence, screenshots, horizontal-overflow location and task result.
  • 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: Information and functionality remain available, and applicable content needs only vertical scrolling. The failed decision is limited to this synthetic target and state; unexecuted coverage is not inferred.

Decision: failed

Finding: A11Y-WCAG-017-example-finding-001 — Check reflow in both scrolling directions: expected result is not demonstrated. The represented barrier may affect People with low vision who use browser zoom.; People who need a narrow viewport or enlarged interface.

Remediation: Change the represented target or process so it demonstrates this result: Information and functionality remain available, and applicable content needs only vertical scrolling. 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 Check reflow in both scrolling directions 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
At a 1280 CSS-pixel starting width and 400% zoom, article content reflows to one vertical column and its menu, errors and submit action remain available.

The 320-width branch retains information and function without horizontal page scrolling.

Failed
At the 320-width equivalent, a sticky footer covers the only submit button and cannot be dismissed.

Functionality is unavailable after reflow.

Not applicable
The evaluated subject is an audio file with no rendered web content.

No target matches the web-content applicability.

Cannot tell
A third-party viewer clips content, but the embedding page and provider behaviour cannot be isolated in the available environment.

The behaviour is reproducible but responsibility or exception applicability cannot be determined.

Not tested
The 320-width branch passed, but selected horizontal presentation at the 256-height equivalent was not executed.

One normative branch remains untested.

Passed
A data table retains horizontal and vertical scrolling inside the table region while the page heading, instructions and controls reflow in one dimension.

The exception is limited to a table that requires two-dimensional layout; it does not exempt the page.

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.

  • 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

No related procedure is recorded.

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 — Individually prepared WCAG 1.4.10 procedure content mapped to current normative and informative sources and checked for internal consistency; competent review, real execution and formal claim authority remain separate.
  4. 2026.08.27-rc.9 — Replaced migrated boilerplate with a case-specific reference implementation and completed generated-file integrity review.
  5. 2026.08.27-rc.9 — Added explicit preparation and variation/recovery steps plus a bounded representative worked example for paid-template use.
  6. 2026.08.27-rc.9 — Procedure guidance and presentation simplified without changing draft governance status.

Review decision: pending. Open issues: Independent standards review and manual calibration at genuine browser zoom remain required before status promotion.

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