htmx silently ignores 4xx/5xx responses: how should swap errors be announced to screen-reader users?
Unannounced failure states in an hx-swap workflow I am designing a form workflow that uses hx-post with hx-target and hx-swap to update a results fragment in place. The documented behavior is that htmx, by default, does not swap response content for 4xx and 5xx status codes (with version-sensitive exceptions such as 422), which means a failed request can pro
htmx