htmx does not have a build step and delivers the source file as a single 3500 LOC file. Alexander Petrois justifies this choice, as it is a tradeoff.

Courses that somehow seems relevant to every web developer. There is a 10-day trial.

Use accessibility APIs of OSes that contains building blocks. These building blocks have 3 kinds of information about a UI element.

The first is a role: What kind of element is this?
The second is a name: a label or an identifier for this element.
The third is state and other properties: Other functional aspects of an element that would be relevant for a user or an assistive technology to be aware of. Is a checkbox checked or unchecked, etc...

It looks like ARIA, oh wait!

The web browsers now expose this accessibility tree.

So the question is, when you have done everything "right" in your attempt to do the right thing and it still doesn't work, at what point do you give up and when do you push on and try to make it right?

What to do?

1. Do nothing (and it degrades user experience for years until a fix is made)
2. Suggest an alternative (and it takes years to fix to go through the roadmap)
3. Work around it
4. Engineer a solution