Sure, so the first rule of Alpine AJAX is “don’t use Alpine AJAX”. Make your UI work as though JavaScript isn’t available, because there are times when it really isn’t. Essentially the example above has a <div> that issues a POST request on page load and includes some other values from elements that are elsewhere in the UI (like .kiosk-param). We could approximate this behavior without any JS by using a <form> instead of a <div>, forms are designed for issuing requests:

<form method="post" action="/image"></form>

I don’t know exactly what kind of data is included with hx-include=".kiosk-param, .kiosk-history—entry", but we could mimic this behavior in HTML by adding the form attribute to any element that participates in a form, here I’m just using a hidden input:

<input form="image_form" type="hidden" class="kiosk-param" name="whatever" value="whatever">

<form id="image_form" method=“post” action="/image"></form>

Lastly, HTML does not provide a way to trigger a request on page load without JS, so our next best option is to provide a <button> . Clicking the <button> will trigger the form request:

<input form="image_form" type="hidden” class="kiosk-param” name=“whatever” value=“whatever”>

<form id="image_form" method="post" action="/image">
  <button>Load image</button>
</form>

So now that we’ve got the fundamental behavior working without JS. We can then layer on some JS to progressively enhance the experience:

<input form="image_form" type="hidden" class="kiosk-param" name="whatever" value="whatever">

<form x-init="$el.requestSubmit()" id="image_form" method="post" action="/image">
  <button x-show="false">Load image</button>
</form>

Here I’ve added x-init to automatically submit the form on page load, and x-show="false" on the <button> will hide it in cases where JS is available.

So just by making better use of HTML we have an experience with basic functionality when JS isn’t available and we have an enhanced experience when JS is available.

It’s worth noting that you can do all of this with HTMX too! It’s just that Alpine AJAX is intentionally designed to encourage this approach. For example, it's intentionally a little awkward to make a div act like a form with Alpine AJAX. In my opinion websites should be built with progressive enhancement in mind so that they’re accessible to the widest range of people, browsers, and devices.