Understanding Canvas Accessibility
taught by: Philip Lazarevic
Session Summary
Creating an accessible canvas element can be challenging. The recommendation of fallback content has not changed in years but does not provide an enjoyable developer nor end user experience as complexity grows. Learn about where Canvas accessibility is today and features being worked on to create accessible, interactive bitmap graphics.
Description
The canvas element can be found in many places on the web, such as graphs, games, image manipulation tools such as Figma and even encapsulate entire pages such as Flutter web. Yet the canvas element is nearly 20 years old and still does not provide a simple way to programmatically associate content with it. There has been a slew of proposed and experimental features to mend this, but a recent proposal has arrived called the Accessibility Object Model (AOM) which is aiming to create meaning without markup. This session will cover current day best practices for canvas accessibility, the problem with fallback content, autogenerating fallback content the Accessibility Object Model (AOM) current state, and what to look forward to in the future. You'll also learn from real life examples such as Flutter on the web and PDF.js.
Practical Skills
- Understanding why certain proposals were not accepted or later depricated.
- Understanding the Accessibility Object Model (AOM) as it regards to canvas accessibility and meaning without markup.