Over a million developers have joined DZone.

Where HTML5 Canvas Accessibility Is Now

DZone's Guide to

Where HTML5 Canvas Accessibility Is Now

· Web Dev Zone
Free Resource

Discover how to focus on operators for Reactive Programming and how they are essential to react to data in your application.  Brought to you in partnership with Wakanda

New features in HTML5 mean new accessibility issues, whether problematic or no (there's some disagreement on this). Here are two resources for keeping up with the current status quo:

  • html5accessibility.com includes tables detailing each browser's HTML5 accessibility support, with numerical rankings alongside more qualitative notes. The site hasn't been updated since July, which will become more of an issue as more rapid-releases (especially Firefox) appear; but for now, at least, the site has a lot of great info. Also includes tips for accessibility support workarounds.
  • Steve Faulkner's 'HTML5 canvas accessibility discussions 2009-2011' page organizes and reformats Charles Pritchard's in-depth review of three years in HTML5 accessibility discussions, an overview of relevant conversations on the public-canvas-api email list. The back-and-forth hyperlinked emails, which in many places conclude in aporia, reveal a bit more about the deeper disagreements still plaguing the development of HTML5 accessibility.

The SVG vs. Canvas debate touches closely on the accessibility issue -- so even if you're not terribly fascinated by accessibility in general, anyone interested in interactive web graphics should find these two pages interesting.

Learn how divergent branches can appear in your repository and how to better understand why they are called “branches".  Brought to you in partnership with Wakanda


Opinions expressed by DZone contributors are their own.

The best of DZone straight to your inbox.

Please provide a valid email address.

Thanks for subscribing!

Awesome! Check your inbox to verify your email so you can start receiving the latest in tech news and resources.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}