- https://wagtail.org/blog/htmx-accessibility-gaps-data-and-recommendations/ (htmx accessibility gaps: data and recommendations. A look at available data, known gotchas, and how to address the gaps)
--<--
Recommendations
Accessibility gets a mention in the htmx docs as part of Progressive Enhancement. This is a bit light on details for my liking, and I think oversimplifies what it means to build accessible UIs. Those oversimplifications are common in online htmx resources. I’d phrase them as:
- Simple HTML is all you need. That’s true – except when your UI becomes complex enough that it’s not.
- The least JavaScript the better. Also somewhat true – except when it leads to leaving out essential accessibility considerations.
-->--