1. 11
  1.  

  2. 5

    I get really concerned about the accessibility situation as browsers can go a great job if developers put in the time, but all of that effort will go down the drain if everything is tossed in a <canvas> tag.

    1. 3

      Yes, and then very big developers (like Google’s Docs team) will be able to implement accessibility within their canvas-based apps, but smaller developers won’t have the resources. This is already a problem with web apps that use JavaScript to re-implement browser functionality: they must also re-implement accessibility for that functionality, which only larger or more motivated teams actually do. But “drop the DOM and do everything by hand in <canvas>” takes everything to the next level.

    2. 2

      The distinction between User and user was illuminating.