An exclusion can exist in the source and disappear from the buyer's view.
Enlarge the page. Read the service conditions. Open the FAQ. Follow the next action. Record whether the information survives those steps.
A narrow screenshot tells you what one frame looks like. A useful review records the enlargement method, available space, component state, and buying task.
The method below follows a fictional service page. Its worksheet and retest rules are editorial proposals. No example describes this portfolio, a real accessibility audit, or a measured business result.
Define the Page and the Buying Question
The fictional page describes a documentation review. It has primary navigation, introductory paragraphs, a list of accepted inputs, service exclusions, an expandable FAQ, and a standalone “Discuss the review” button.
The buyer's question is whether the service includes rewriting source documents. The exclusion paragraph answers it. The FAQ explains how the buyer prepares files. The button leads to a separate next-step destination.
Keep that question attached to the review. Merely finding the button would leave the scope question unanswered. A buyer who cannot read the exclusion cannot complete this task as defined.
Use a permitted test environment for a real session. Record its release identifier, page address, browser and full version, operating system, zoom mechanism, and effective viewport. Keep personal records and live submissions out of the example.
For the fictional walkthrough, assume a desktop Chromium browser with whole-page zoom. Start with a content viewport of twelve hundred eighty CSS pixels at one hundred percent. Record actual measurements during a real review. Outer window dimensions are a different field.
The review also includes a narrow-layout observation. If another browser supplies a separate text-only resizing mechanism, record that as a distinct attempt with its own environment. Do not label every enlargement mechanism text-only resizing.
Keep Resize Text and Reflow Distinct
WCAG 2.2 Success Criterion 1.4.4, Resize Text, addresses resizing text without assistive technology up to two hundred percent without losing content or functionality. Captions and images of text are exceptions. W3C: Understanding Resize Text.
Whole-page zoom can provide a text scaling mechanism. Text-only resizing changes a different condition. Record which supported mechanism you used and any intermediate levels examined. Resize Text guidance.
Success Criterion 1.4.10, Reflow, addresses information and functionality without two-dimensional scrolling. Its conditions are three hundred twenty CSS pixels wide for vertically scrolling content, or two hundred fifty-six CSS pixels high for horizontally scrolling content. Parts requiring two-dimensional layout are excepted. W3C: Understanding Reflow.
For ordinary vertically scrolling English content, examine the width condition. A twelve hundred eighty CSS-pixel starting viewport at four hundred percent zoom corresponds to three hundred twenty CSS pixels. Reflow conditions.
These criteria overlap in practice but ask different questions. Keep the enlargement record and the layout record separate. Passing one observation does not settle the other criterion.
Neither criterion supplies a prediction about search position, buyer response, or commercial results. This article uses them to define review conditions.
Record Conditions Before Interpreting the Screen
Start with a baseline at one hundred percent. Write down the content and controls required for the buying task. Expand the FAQ and note where its answer appears.
Return the FAQ to its initial state before the next attempt. Record any change in layout or state between attempts. Comparing an open answer with a closed answer could manufacture a missing-content finding.
Use the following condition record for each attempt:
- Page and release: Address, version identifier, review date, and reviewer.
- Environment: Browser version, operating system, display settings, and assistive technology used or absent.
- Viewport: Measured content width and height, with CSS pixels identified explicitly.
- Enlargement: Whole-page zoom, text-only resizing, or narrow viewport, including the selected level.
- Starting state: Navigation expanded or collapsed, FAQ open or closed, and current scroll position.
- Task evidence: Scope answer found, preparation instructions read, and next action reached.
- Observed loss: Clipped words, hidden controls, overlap, or sideways movement needed to read ordinary text.
- Untested conditions: Other mechanisms, browsers, components, and content states.
This is a proposed record format. Add fields when the implementation needs them. Avoid filling an unknown version or viewport value from memory.
Keep display scale distinct from browser zoom. The record should allow another reviewer to reconstruct the condition without guessing what “large text” meant.
Read the Content After Every Layout Change
At two hundred percent whole-page zoom, repeat the buying task. Read the complete exclusion, including the final clause. Open the FAQ. Read its answer through the last sentence.
Inspect text-bearing controls too. A button may remain visible while its label loses the word that distinguishes its action. Record the full approved label and the visible result.
Check neighboring sections for overlap. A heading might cover the first line of the next paragraph. A fixed panel might obscure the final FAQ answer. Describe which information is unavailable in the tested state.
Where incremental resizing levels are available, include them in the review. W3C explains that content and functionality must remain available through the supported increments up to two hundred percent. Resize Text guidance.
Do not infer readability from the absence of a horizontal scrollbar. Text can disappear inside a fixed-height region without creating page overflow. Read the words against the approved content inventory.
Do not infer loss merely because an element moves. Navigation may change presentation while preserving access. Record whether the buyer can still use it. W3C permits rearrangement when information and functionality remain available. Reflow guidance.
Leave implementation choices with the responsible team. This review records the lost condition and task consequence. It does not prescribe a stylesheet change.
Follow Ordinary Content Through Reflow
For the separate reflow attempt, use the stated equivalent width and repeat the service-information task. Record the effective viewport rather than relying only on a zoom menu label.
Read ordinary paragraphs from beginning to end. Note whether a line requires sideways scrolling before the reader can continue downward. Identify the section causing that movement.
Check navigation in its narrow state. If it becomes a disclosure, examine its open and closed states. A clean screenshot with navigation closed leaves the expanded content untested.
Open each FAQ needed for the task. Check both the question control and answer. Keep the standalone next-action button separate from nearby qualifications and explanatory text.
A mobile viewport observation can expose a narrow-layout problem. It does not reproduce every consequence of desktop enlargement, browser controls, text scaling, or changed component states. Record it as the condition examined.
Use a short content inventory to prevent omissions: service purpose, accepted inputs, exclusions, preparation answer, and next action. Mark each item found, unavailable, or untested. A layout review is incomplete when the reviewer cannot say which information was sought.
For information architecture decisions beyond enlargement, use the B2B landing-page guide. Keep this worksheet focused on whether approved buying information remains usable.
Work Through a Fictional Clipped Section
Suppose the exclusion reads: “The review identifies documentation issues. Rewriting source documents is outside the service.” At baseline, both sentences are visible.
In the invented two hundred percent zoom attempt, the section's visible region shows the first sentence and clips the second. There is no visible way to reveal the remainder within that section.
The buyer can still reach the next-action button. The scope question remains unanswered. Write that task failure explicitly instead of calling the page generally unreadable.
A before record might contain these fields:
Condition: Desktop Chromium, whole-page zoom at two hundred percent, FAQ initially closed, same service-page revision as baseline. A real record also supplies the full version and measured viewport.
Expected result: Read whether rewriting is included before choosing the next action.
Actual result: The exclusion's second sentence is clipped. The visible text does not state whether rewriting is included.
Reproduction: Load the identified revision. Set the recorded zoom level. Navigate to exclusions. Compare the displayed paragraph with the approved content inventory.
Impact and owner: The buyer cannot recover the scope boundary through the examined section. Assign reproduction to the implementation owner and wording verification to the content owner.
All these observations are fictional. They illustrate a bounded handoff, not proof that a particular layout technique causes clipping.
Keep the Two-Dimensional Exception Local
W3C lists data tables, maps, and other content requiring two-dimensional layout among its reflow examples. Individual table cells still need to reflow. Reflow exceptions.
The exception concerns the part that requires that layout. It does not excuse ordinary service paragraphs, navigation, or FAQ answers from the review.
Ask what relationship needs two dimensions. A map may need spatial relationships. A simple exclusion sentence does not gain that need because the page designer placed it beside a diagram.
Record the component boundary in the observation. Distinguish scrolling within an excepted part from sideways movement across the entire page. Keep the specialist's assessment attached to the specific content and criterion.
Use the separate guide to accessible B2B comparison tables when the buying information is a grid. This article does not redesign that grid or establish whether every complex component qualifies for an exception.
Do not remove qualifications or replace text with unexplained symbols to make the screenshot fit. Preserve the buyer's question and its complete answer while the implementation owner evaluates the presentation.
Record the After State Without Expanding the Claim
Suppose the implementation owner supplies a revised test page. Repeat the original clipped-section attempt with the same recorded browser, viewport, zoom mechanism, level, and starting state.
In the fictional retest, both exclusion sentences are visible. The reviewer reads the boundary, opens the preparation FAQ, closes it, and reaches the next action.
Write the after record against the original finding: “The exclusion's second sentence remains available in the repeated two hundred percent attempt.” Identify the revised page and attach evidence.
Then repeat the separate reflow condition. A correction observed at two hundred percent does not establish the outcome at the equivalent three hundred twenty CSS-pixel width.
If the ordinary paragraphs require only vertical scrolling in that second attempt, record that observation separately. Keep any residual overlap, clipped control, or untested state open.
Use a narrow status vocabulary for the worksheet: reproduced, awaiting change, retested in stated conditions, or unresolved. These labels describe evidence. They are not certification levels.
Keep the original failure and after record together. Another reviewer should be able to identify what changed and what remains unknown without reconstructing the session from screenshots.
A broader conversion review can use this evidence when planning further work. This check establishes neither site-wide accessibility nor legal conformance, ranking changes, or improved conversion.
Keep the complete answer available.
Sources
- W3C Understanding SC 1.4.4: Resize Text. Text scaling, two hundred percent, exceptions, and intermediate levels. Checked 2026.10.28.
- W3C Understanding SC 1.4.10: Reflow. CSS-pixel conditions, zoom equivalence, rearrangement, and local two-dimensional exceptions. Checked 2026.10.28.