Accessibility in Canvas 3D

Editor's Notes

• #3: Originally people thought canvas was just about painting boring images on a bitmap...
• #4: ... or for adding wet floor effects for photos.
• #5: Then people started getting creative, for example in this emulator written in JavaScript for the original Space Invaders engine that you can now play in your browser.
• #6: The lesson learned: given the tools people will do anything with a canvas!
• #7: Like building a rich text editor in canvas: Bespin was published by Mozilla and is now part of the Jetpack code editor.
• #8: Therefore it is important that there is fallback content.
• #9: Fallback content, aka. “the shadow DOM,” is always exposed to assistive technologies, unlike other fallback content that’s only displayed if the browser doesn’t support the element. Shadow DOM elements must be keyboard accessible, and the corresponding part of the bitmap must be highlighted with a focus ring, probably a caret position as well in the case of editable content.
• #10: In a 3D context one of the strongest use cases is in games. This is a demo of the 3D jump & run game “Infinite Journey” created in WebGL that runs in your browser (if you are lucky enough to have the right chipset).
• #11: In games the interaction is limited to a small number of objects, mainly player and non-player characters as well as items. They are in control of players or the game vendors and are well defined.
• #12: However, the main challenge in games is reaction time. Games for blind people feature several mechanics to support this, like audio cues, “earcons” (similar to icons), a sound radar to spot enemies and friends, sometimes tactile feedback is used (vibration) to identify objects, and there is speech synthesis for announcing the names of objects. There is a problem with hardware acceleration because it goes directly to the GPU, bypassing the accessibility API.
• #13: In 3D social worlds like Second Life the challenges are different.
• #14: There is user generated content. A lot of it! About 40% of the objects don’t have alternative or descriptive texts, on some islands as high as 85%. To prevent clutter, users get summaries of the number of people and objects present. Also only objects within a 10-20 meter range are announced. Screen-reader support is crucial because users heavily customize their software.
• #15: Eelke Folmer did a lot of research on the topic of accessibility in 3D worlds. Also IBM published games for blind and vision impaired people. I’d like to encourage you to contact them.
• #16: But it doesn’t stop at games and social worlds. For example there are medical applications. A CT scan of a hand has about 20-30 MB, a full body scan about 700 MB. I can imagine tools to process this information in the browser.
• #17: And of course architects use 3D models, among others.
• #18: Therefore my plea would be to reach out to the Khronos Working Group and vice versa.
• #19: Because bolt-on accessibility is ugly,
• #20: Whereas inclusive, integrated accessibility is beautiful …
• #21: … and good for your health.