Zooming checkout hides totals or the payment action

Two observations answer different layout questions

W3C’s Resize Text explanation describes text resizing up to 200 percent without loss of content or functionality, except for captions and images of text. For checkout, the useful observation is whether larger text still leaves the amount due, field instructions and control labels available. Merely seeing larger letters does not establish that the information can be read or the next action reached.

Reflow asks a different question: can vertically scrolling content be used at a width equivalent to 320 CSS pixels without requiring scrolling in two dimensions, subject to the criterion’s exceptions? A layout may enlarge text successfully while pushing the total beyond the side of the page at a narrow width. Conversely, a narrow layout can fit while larger labels are clipped inside fixed boxes. Keep those observations separate.

Browser page zoom, a text-size setting and a window-width change are not interchangeable entries in the record. Write which control you used and its value. Record the available width in CSS pixels if it was measured; otherwise mark it unmeasured. A zoom percentage alone does not establish the reflow width.

Name the lost content and the blocked task

Use the actual checkout state in which the obstacle occurs. Note whether the order summary is expanded, which step is open and whether a fixed header or footer overlaps the form. W3C’s Reflow explanation specifically warns that sticky content can obscure other content. Record the overlap you can see rather than assuming every hidden control was removed from the page.

Distinguish content that moved below the viewport and can be reached by ordinary vertical scrolling from content that remains clipped, covered or unreachable. Record whether horizontal scrolling is also needed to read the total or operate the form. A pay label split over more lines is not by itself the same failure as a pay action that cannot be reached.

Write the consequence in task terms: the amount due cannot be read, the required acknowledgment cannot be operated, or the payment action is covered. Preserve any genuine screenshots with customer and payment details removed. Do not submit an order or a payment to establish a visibility problem.

Assign the containing layout as well as the control

Identify the owner of the affected component and the owner of the space around it. The page’s theme, checkout extension and hosted payment area may have different maintainers. A clipped payment area is evidence of clipping; it does not, on its own, identify which party must change the code. Give the maintainer the setting, width and checkout state that reproduce the observed loss.

The acceptance requirement should say what must remain available: the complete total, the full required wording and the ability to reach and operate the next control. Let the responsible implementer select the layout change after inspection. Hiding information, shortening a material notice or forcing smaller text does not demonstrate that the original task is usable at the reported setting.

If someone invokes a reflow exception, ask which specific content requires a two-dimensional layout and why the exception applies. Do not extend an exception for one component to the whole checkout. This observation sheet does not decide every exception or establish full WCAG conformance.

Verify the repaired task under the recorded conditions

After a change, return to the same enlargement, measured width and checkout state. Confirm the previously lost information is readable and the previously blocked action is reachable, stopping before payment submission. Record the deployed version and result so that a screenshot at ordinary text size is not mistaken for verification of the repair.

If the result is still unusable, return the specific remaining loss to its owner. A successful check of this condition does not establish every accessibility criterion or every device’s behavior. For a Prism consultation, describe the public checkout, the enlargement used and the blocked task. Agree on assessment and implementation scope, responsibilities, fees and terms before work starts.

Enlargement failure record

Complete this for one observed failure on the real checkout. Keep enlargement and measured width separate. The repair is ready to assess when the same task can be repeated at those settings without losing required content or function; this is not a conformance certificate.

Worksheet entries are not submitted by Prism’s worksheet and are not saved by the site. Use record types, availability, anonymized observations, or match/mismatch results. Do not enter government identifiers, customer names or addresses, customer messages, receipt-access links, card or bank details, passwords, or keys. Send sensitive documents only through the provider’s verified secure channel.

These are temporary notes. Leaving or reloading this page may clear them. Worksheet entries are not sent automatically. If you copy notes into the consultation message and submit the form, Prism receives them as part of your request.