Canvas-based 3D web experiences are often inaccessible because developers skip semantic fallback content. While the HTML canvas spec has always required fallback content, it's rarely implemented. The emerging HTML-in-canvas proposal (WICG) promises to automatically synchronize visual canvas rendering with semantic HTML, eliminating the costly manual effort of keeping visuals and accessibility fallbacks in sync. Currently available behind a Chrome/Brave feature flag (`chrome://flags/#canvas-draw-element`), it lets developers use semantic elements like buttons and render them visually in canvas, ensuring accessibility is built-in rather than bolted on. The post also advocates for planning accessibility from the ideation phase rather than retrofitting it later.
Table of contents
We already have some solutions, but they are often neglected or forgottenHTML-in-canvas has the potential, but we still need to plan for accessibilityAuthor: Bogdan CerovacSort: