My shorter answer: if you think you need to use canvas,

you don't.

(Unless you're literally building a drawing app.)

99.99% of web applications would be better off virtually ignoring "best practices" introduced by Big Tech.

Oh man, I thought "Canvas" was the name of yet another web framework, but no, they mean the actual HTML <canvas/> element.

Back in university, I was tasked to build a calendar view with HTML. It was my first web project, I decided to use a canvas to draw the calendar.
It took me several times as long to complete my implementation compared to other students, because I had to re-implement layouting, click handlers and probably more things I don't remember...

I too hate visually impaired people.

No.

What you most probably want to do is to build your next app as simple as possible, with hypermedia driven architecture, using established patterns of rendering server side, sending html to client, client replaces HTML.

HTMX is one tool that complements and fits nicely within this well established paradigm, which is the way I'm doing web development going forward.