Captive portal Custom splash page email collection

[Bartell_eng]

I am setting up a splash page that collects emails for public access to wifi. I am wondering how I can prevent people from clicking through with out filling in the email field in the splash page. Click through is good but it does not stop someone from checking box without an email to get access. Any ideas how to prevent this? Cannot find a good white paper on it.

[LasseBang]

Do you need to store the email?

[Bartell_eng]

Yes and we already have that part. The issue is how do you keep them from clicking through with out entering an email. need some way to stop the click through until the field is entered or a way to stop the moving on or opening another page without hitting submit.

[LasseBang]

@Bartell_eng you could make a custome page https://documentation.meraki.com/zGeneral_Administration/Cross-Platform_Content/Configuring_a_Custom...

[Bartell_eng]

We have and not sure how to stop them from opening another page without clicking submit or button to get access to internet.

[PhilipDAth]

I'd use a third party commercial splash page service like Splash Access.

https://www.splashaccess.com/ 

[Bartell_eng]

We are looking at third parties but we already have the means and backend for what we want to do with the data.

[boundless-digit · Accepted solution]

Is this a page you've developed yourself and have access to the HTML?

Will adding a 'required' attribute to the input work?

https://www.w3schools.com/tags/att_input_required.asp

[Bartell_eng]

I am not sure at this point and was hoping someone out there has already done something similar who could tell me. If we have built our own and yes it is easy to do this for your own site but not sure how meraki interacts and will see to allow traffic after someone hits the submit button or what ever we put. If we make it a click through page the same. How does our custom page just get bypassed as I believe it is built into the clickthrough page built by Meraki Like a banner or something which the attribute would be ignored.

[Bartell_eng]

After reading more in white papers I believe that is what would be needed. I will follow up with our testing to let you know.

[boundless-digit]

Awesome... let me know if I can help in any way... this is the technique we've used to require fields in our captive portal pages

[colinster]

You just want to gray out / disable the button until the field is completed. This can be done with JavaScript validation. 

https://www.w3schools.com/js/js_validation.asp

https://www.w3resource.com/javascript/form/email-validation.php

https://html5-tutorial.net/form-validation/validating-email/

Also, I love Splash Access:

https://www.splashaccess.com/ 

[Martin-cantwell]

I used this is a splash page that I've have setup,

<input required name="username" id="username" style="width: 300px" type="email"></input></p>