By platform
Adobe Portfolio contact form not sending email
A visitor types a message, taps Send, and either sees the text still sitting in the box or a confirmation that never turns into a message in your inbox. Mimiq sends simulated visitors through the same form and shows what each one saw.
Why is my Adobe Portfolio contact form not sending email?
A contact form on a portfolio site can fail in three ways: the message never leaves because a phone keyboard covered the Send button, the message goes to an address you do not read, or it reaches the inbox and is filed as spam. Each one looks different to the visitor, and the first looks like nothing happened at all. A simulated test fills the form, presses Send, and reports whether the text cleared, whether a reply appeared, and where the visitor stopped.
What this looks like in a report
“I finished the last field and the keyboard covered the Send button. I tapped where it should be and got the keyboard again. I gave up, and I am not sure the message would have gone anyway.”
The fix. In the site's editor, leave space below the contact form's Send button so the page can scroll past it when the keyboard is open. Then type in the last field on a phone and tap Send with the keyboard still up, and confirm the form submits.
An illustration. Run a test to see your own.See a real sample report
The keyboard can cover Send, so the press never happens
On a phone, an open field raises the on-screen keyboard, and the keyboard takes up the lower part of the screen. A contact form whose Send button sits just below the last field can end up under the keyboard, so a tap on Send lands on the keyboard or on the field, and nothing is submitted. The visitor sees the text still sitting in the boxes and the page unchanged. They may assume the form failed and write to you another way, or leave. An owner who tests from a desktop never raises the keyboard, so the button always looks reachable.
- On a phone, type in the last field, then tap Send without closing the keyboard. Note whether the form submits.
- After a tap on Send, check whether the text stays in the boxes. If it does, nothing was submitted.
- Look at the contact section at phone width. Is there space below the Send button before the page ends?
- Check the address set for contact messages against the inbox you read every day.
- Send one test to that address from a second mail provider, then look in its spam folder.
Where the keyboard leaves the visitor
When a visitor taps a field on a phone, the keyboard opens and the page slides to keep that field in view. The Send button can end up hidden under the keyboard or pushed to the edge of the screen. A tap where Send was drawn then lands on the keyboard or on the field above it, and nothing is submitted. The visitor sees the same form with the same text in it, and cannot tell whether the message went.
Layout decides how often this happens. A tall message box, a field added late, or a form that sits close to the bottom of the page leaves the button little room above the keyboard. Space below the button, so the page can scroll past it, is often enough. Check that space on a real phone, because a desktop window never raises the keyboard.
Messages that leave and never reach the reader
When the text clears and a confirmation appears, the message has been handed to the site, which sends it to the address in your contact settings. That address may be an old one, a typo, or an inbox you stopped reading. The receiving provider can also file the message as spam, so it sits out of sight. Look in the spam folder before you decide the form is broken, and send one test from a different mail provider to see whether the fault follows the address or the sender.
What a run can and cannot show about the keyboard
A simulated visitor fills the fields in order, presses Send, and records what the page shows next. If the text stays in the boxes, the report gives the step, a screenshot, and the state of the form at that moment. A simulated visitor runs in a browser, and it may not raise an on-screen keyboard the way a phone does, so a tap under the keyboard may not reproduce. Use the run for the form's reply and the steps around it, and use a real phone for the keyboard check.
Mimiq is independent and not affiliated with the platforms it names. Names belong to their owners.
What you get with Mimiq
- 01
Run it by hand, or on every pull request
Paste a link and a task in the app and watch the visitors work. Or run them on every preview deploy: the GitHub Action comments on the pull request, any other CI can call the MCP endpoint, and your coding agent can run it too.
- 02
Bugs and usability problems in one report
The browser records errors and failed or slow requests on the step they happened. The visitors say where the wording or the steps confused them, and where they left.
- 03
Visitors that behave like your audience
Each visitor is a different profile with a reason to be there, matched to who the page is for, described by you, or built from your own customers.
- 04
A prompt to fix each problem
Every problem comes with a fix to paste into Cursor, Claude Code, Lovable or any coding agent, and one prompt hands over the top problems at once. Then send the same visitors through again.
- 05
Follow every visitor
See each visitor's whole path, step by step with screenshots, and what it was thinking at every step. Ask any visitor a question.
The browser records relevant JavaScript errors and failed or slow app requests encountered during the run, attached to the step where they occurred. The visitors are simulated: they find problems, they do not predict how many real people will convert.
A longer message box can push Send back under the keyboard
Each change to the contact section can move the Send button. A longer message box, a new field or a block added above the form can bring the button back under the keyboard on a phone, even though it worked before. After each edit, type in the last field on a real phone and tap Send with the keyboard still open.
Starter
Try it on one launch
About 4 tests of 5 visitors
- Visitors on your landing page, signup and checkout
- Where they left and why, with a fix to copy for each problem
- Run it in the app or on every pull request
- Ask any visitor a question, included
- Test accounts and protected previews
Builder
Test every build
About 20 tests of 5 visitors
- Everything in Starter
- Credits refill each month, and what is left rolls over once
- Cancel anytime
Pro
Test every release, as a team
About 60 tests of 5 visitors
- Everything in Starter
- Credits refill each month, and what is left rolls over once
- Cancel anytime
Scale
Test at scale, every day
About 240 tests of 5 visitors
- Everything in Starter
- Credits refill each month, and what is left rolls over once
- Priority support
- Cancel anytime
Questions
Why does the form work on my computer?
A desktop browser has no on-screen keyboard, so Send is always visible and clickable. A phone covers part of the page whenever a field is open. Test on a phone, type in the last field, and tap Send without closing the keyboard.
Can the test show the on-screen keyboard?
Not reliably. A simulated visitor runs in a browser, and it may not raise a keyboard the way a phone does. Use a real phone for the keyboard check, and use the run for the form's reply and the steps after the tap.
Can the test tell me whether messages reach my inbox?
No. It cannot tell you how many messages reach your inbox, and it cannot read that inbox. Send one test to the address set for contact messages, then check its spam folder yourself after each change.
Does the test judge how my portfolio looks?
Only in part. The report shows whether the form can be used, with the step, the screen and any blocked script. It does not judge the design, and it does not predict how many visitors will send a message. Treat it as a usability check, not a sales forecast.
Keep reading
Send visitors and see what breaks first.
Your first test is free: sign in with Google and it starts right away. Last checked 2026-11-02.