WASM does not need to access the DOM to be extremely useful. JS is already very effective and ridiculously fast for updating the DOM.
WASM is to offload computationally expensive workloads that JS is not so good for (perhaps some sort of computer vision, for example). It passes the result back to JS to update the DOM.
Everyone says that and it makes sense, so I don't criticize this opinion.
And yet you have articles like OP, where someone finds WASM useful for form validation which is clearly not in the "offload computationally expensive workloads" category and would profit from a direct integration.
