The mobile keyboard covers the field or submit control

Measure the space that remains when typing starts

MDN distinguishes the visual viewport from the layout viewport and documents that the on-screen keyboard can shrink the former without affecting the latter. A screenshot taken before anyone focuses an input misses that state. Initial page width and keyboard-open visibility answer different questions.

On the affected phone, keep the checkout step, orientation and zoom setting consistent. Record the device, operating system, browser version, observation time and focused field. Compare the visible page before focus, during keyboard display and after dismissal. If a maintainer can measure visual viewport height, record both heights in CSS pixels with the measurement method. Otherwise describe the visible boundaries and mark the height unmeasured. Do not substitute the phone’s advertised screen resolution for a viewport measurement.

Locate the obstruction and the task it interrupts

Look for the active input, its label or instructions, and the control needed to continue. Record what covers each one: the keyboard itself, a bar belonging to the page, or another visible overlay. W3C’s Reflow guidance warns that sticky content can obscure page content. That supports investigating a persistent header or footer, but it does not establish that your checkout has one.

While the keyboard remains open, observe whether ordinary scrolling can bring the field and its instructions into view. Separately note whether the next control becomes reachable after the keyboard is dismissed. A control below the current view is different from one that cannot be reached at all. A control that is visible but does not respond is another observation; do not label it covered.

Keep the input’s contents out of the record. You can identify a field by its label and location without recording a customer address or payment value. Use an authorized view of the real checkout and stop before order or payment submission.

Use the comparison to choose a bounded repair request

If the obstruction appears only with the keyboard open and clears on dismissal, give the maintainer that sequence and the affected field. If a persistent page bar occupies the space where the field should be visible, identify that bar and its owner. If the control remains unreachable after dismissal, preserve that result too: the problem is broader than keyboard display alone.

Ask for an outcome that can be observed on the affected device: the active field and needed instructions can be brought into view while editing, and the next action can be reached through the intended flow. The maintainer should identify which layout or component owns the behavior before choosing a change. Moving one bar without checking the newly exposed content does not establish that the task is usable.

After an authorized correction, revisit the same field and keyboard state once, then record whether the obstruction remains. This checks the named repair. It does not prove that every phone, orientation or checkout step works, and it provides no evidence about processing eligibility.

Bring the viewport map to a checkout consultation

For a Prism checkout-review consultation, summarize the checkout URL, the device, the field and the visible obstruction. State whether you need help understanding the observation or discussing a proposed change. Prism’s published support includes storefront review and help with a provider’s website questions; scope, responsibilities, fees and terms are agreed before work.

Use the public inquiry for the website, research-only products and question. Leave out passwords, card details and customer records. Follow-up is by email, and the request does not book an appointment, purchase a service or submit a processing application. The provider retains its account and eligibility decisions.

Keyboard-open viewport map

Complete this for one affected field on one real device. Compare closed, open and dismissed states without submitting an order. Blank or unmeasured entries remain unknown; a dated observation is not a universal browser result.

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.