Jotform not showing submit button for visitors

An embedded form is drawn inside a frame on your page, and the frame has its own height. The form builder itself has no such limit. If the frame has a fixed height, or your theme caps the height of the container around it, the bottom of the form is cut off, and the button sits in the cut part. A visitor on a phone scrolls the page, reaches the bottom of the box, and finds no button. Scrolling the outer page only moves the box, not the form inside it. The button is in the code, but the visitor never sees it.

• At phone width, scroll to the bottom of the form. If the box ends before the button, its height is too small.
• Open the last page of a multi-page form. A Next button there means Submit sits on another page.
• Check whether a condition sends visitors past the last page, where no Submit appears on that path.
• Compare the button color with the background your page sets behind the form area. A matching color hides it.
• Inspect the spot where the button should sit and see whether a style from your page hides it.

On a laptop the form may fit inside its frame, and the person who built it sees Submit at the bottom of the page. On a phone the fields stack, so the form gets longer, while the frame that holds it can keep the same height. The visitor scrolls through the questions, reaches the bottom, and sees a blank strip with no button. Some visitors try to scroll inside the box, which does nothing in many frames, and then leave. Others never reach the last questions, because the box stops before they end.

The height problem is the first thing to check. A frame with a fixed height shows only that much of the form, however long the form is. A multi-page form has the second problem. Its last page holds the Submit button, and every earlier page shows Next, so a visitor who stops one page early never sees Submit. Check the last page directly, and check which branch leads there, since a condition can skip past it.

The style problem comes from the wrapper around the embed. A theme can set a height limit, an overflow rule or a background on the block that holds the frame. The frame can be fine while the block around it hides the lower part, or while a light button sits on a light background and looks like empty space. Compare the button's color with the background behind the form, and inspect the spot where it should sit.

The simulated visitor fills the fields it can see, scrolls to the bottom, and looks for Submit the way a stranger would. If the button is not there, the run stops at that step, and the report shows the step, a screenshot of the blank bottom of the box, and any console error. If the button is there, the run presses it and records what the visitor sees next. Mimiq visitors use laptop and phone browsers, so one run can cover both widths.

A new section, a larger font or a theme update can narrow the block around the embed or cap its height. Each change can move the bottom of the form out of reach on a phone. Run the same visitors to the last page after every change to the page or the form, and compare the step where they stopped with the run before.