Hi @dustin1,
I can confirm that the page calling the Accept.js script does need to be served from a server supporting a secure connection. If you're testing locally, that means that the server you're running on your machine needs to support https, although you don't have to have a domain certificate to do that (as Lilith points out).
The Accept.js documentation does list the error message:
| E_WC_02 | A HTTPS connection is required. | The page on which you’re including Accept.js must be served over an HTTPS connection. |
However, it's not explicit in the documentation that you'll get that error message anytime that page is served insecurely, so it's not clear to the reader if this error message is listed as just a possible thing you might see depending on situation.
I'm making a note to put an explicit mention of the requirement on this page to avoid future confusion. Hope that helps!
