without javascript the only meaningful thing that can be done in HTML are to navigate to a new document with HTTP GET (A[href=]) or submit data via HTTP POST or similar verbs ((BUTTON, INPUT[TYPE=BUTTON]. INPUT[TYPE=IMAGE]) where the url is in the FORM tag or the form* attributes. This is because without javascript there are no persistent stores on the client side and you have to interact with HTTP to create a stateful application.

I'd say whether a button does something without JavaScript is a separate topic.

The page repeatedly mentions accessibility characteristics, it just doesn't call them all out as such.

> Not keyboard focusable

> Correct button role

> correct key events by default

> No accessible name

"Shows wrong cursor on hover" is arguably also about an accessibility characteristic.

True, only <button> (if type is not "button") and <input type="button"> function within a <form> context as a button.

yeah, "A focusable div with a button role" should be pretty accessible compared to a div with onclick event and neither of those things, for example.