Canvas ought not be utilized to produce content since it renders as a picture of content that pixelates, when developed, and can't be modified by the client like CSS content.
A canvas component must have an available name and depiction that coordinates the noticeable content and substance inside the canvas drawing region.
Canvas components that are utilized as mouse and console operable custom UI controls must have an availability job, for example role=button for custom canvas catches.
HTML5 Canvas and the Canvas Shadow DOM
Taking care of client contribution to HTML5 Canvas-based games
Canvas components MUST have a book elective
The canvas component that renders on screen isn't open to screen perusers on the grounds that the substance isn't in the DOM and has no openness semantics. Either inside fallback substance or ARIA semantics must be utilized to make a book elective open to screen perusers.
ARIA as alt content
Utilizing ARIA role=img and aria-label="alt content" on the <canvas> component or the inner fallback content makes a component accessible to the screen peruser by means of Image fast route orders with the picture job spoken dependent on role=img.
Fallback content as alt content
Interior fallback content between the opening and shutting canvas labels, for example <canvas height=200 width=400>Fallback Content Static Text</canvas>, doesn't have a picture job except if ARIA is applied and the focusable territory isn't the full canvas square shape, the touch target region and screen peruser center layout just encompasses fallback content. By putting role=img and aria-mark esteem straightforwardly on the <canvas> label the touch target and screen peruser center territory effectively encompasses the enter canvas component.
In the event that fallback content is utilized, at that point, it should likewise be available.