You are getting downvoted because the rendered page is HTML, which has the same accessibility properties as always

There's more to rendering than looking at the DOM at static points in time. There's certainly more to accessibility that conveying changes to the dom which may or may not be "visible", or certainly relevant, to the end user.

Other than 10% of the globe unable to run wasm, what accessibility concerns come to mind here? Are there any that wouldn't also apply to a SPA that uses JS to manage the DOM?

Some people believe that wasm will encourage people to turn web pages into one big <canvas>, which would be quite a hit. I don't personally believe that, though.

I had in fact considered playing with and possibly deploying something like this if I liked it.

I'd like to thank this thread for reminding me why that's probably not a good idea.

Are there any good resources to read up on for making sure accessibility is good in <canvas>? I assume you'd have to implement it yourself.

> Are there any good resources to read up on for making sure accessibility is good in <canvas>

whatwg.org[1] is less than helpful when it comes to to describing how to make sure canvas elements are accessible; MDN[2] is a little more helpful. tl;dr: it's a lot of hard work.

I have found some relatively useful posts in various places (eg: [3]) for people (like me) who don't like being told not to do something. These articles generally date from around the mid 2010s but, given that there has been little development in the <canvas> world since then, their advice is still good today.

[1] whatwg - https://html.spec.whatwg.org/multipage/canvas.html

[2] MDN - https://developer.mozilla.org/en-US/docs/Web/API/Canvas_API/...

[3] - https://developer.paciellogroup.com/blog/2015/02/html5-canva... - including this link because post was updated in 2020

Thanks, I've favorited this.

I have no idea personally, I imagine you'd have to implement it all yourself, yes, and I don't even know if the proper hooks are there, honestly.

The typical concerns that come with dynamic DOM manipulation....