It's not meant to be an HTML renderer. That's for .NET apps. While it's cool they can run in a browser, that's not meant to build websites.
Would you complain that Qwasm/Dwasm doesn't follow HTML standards of accessibility?
Would you complain that Qwasm/Dwasm doesn't follow HTML standards of accessibility?
If Qwasm is referring to Quake, it absolutely should have, for example, legible color contrast and be usable if you are colorblind.
Even if you do consider it separate from webapps, it should still work with tab navigation and screen readers, which rendering to `<canvas>` doesn't allow for (at least without some very hacky workarounds).
Flutter faces a similar problem; to render cross-platform, they use a custom layer not standard to the system, and then try to emulate all the behaviors of a native app, which often feels broken and unnatural and is wasted work because the engineers are just rewriting and reshipping everything the platform already offers—at the cost of accessibility and general user experience.
- [1]: https://vscode.dev