Re: Shadow Dom stuff

Hi Lisa,

I agree we need more documentation, tutorials and examples.  I think we
were just waiting for implementations to catch up with the spec.  I did
some early prototyping myself a few months ago, as an exercise to get more
familiar with the features but also to test support.  My slides are
available here:

http://www.w3.org/Talks/2014/0510-canvas-a11y/index.html#1

I built a simple canvas game that can be played by keyboard users, screen
reader users and magnification users, taking advantage of the new
accessibility support in canvas.  The game is here:

https://github.com/cptvitamin/a11y-whack

In order to play/test you have to have the nightly build of chrome or
firefox on windows and have the proper flags configured for experimental
support of drawFocusIfNeeded and HitRegions.  The slide deck includes
embedded video of support for keyboard, speech and mag users.

Mark


On Tue, Aug 19, 2014 at 1:41 PM, lisa.seeman <lisa.seeman@zoho.com> wrote:

> Sorry for creating this confusion. I only intended to ask if anyone is
> making working examples for accessible canvas, with what we currently have
> working so we can identify any additional issues from the author
> perspective.
> My mentioning magnifcation was out of date.
>
>
> All the best
>
> Lisa Seeman
>
> Athena ICT Accessibility Projects
> <http://accessibility.athena-ict.com/default.shtml>
> LinkedIn <http://il.linkedin.com/in/lisaseeman/>, Twitter
> <https://twitter.com/SeemanLisa>
>
>
>
>
> ---- On Tue, 19 Aug 2014 18:30:24 +0300 *Mark Sadecki<mark@sadecki.com
> <mark@sadecki.com>>* wrote ----
>
> Hi Rich,
>
> I agree with you and was also confused by Lisa’s original suggestion.  I
> was hoping she would clarify if she indeed meant Shadow DOM, or fallback
> content by making the distinction.  I think we should also make it clear
> that Hit Regions now support associating that fallback content with regions
> on the canvas for the purpose of informing the AAPI, which should alleviate
> any concern she has about magnification.
>
> Mark
>
>
> On Tue, Aug 19, 2014 at 10:55 AM, Richard Schwerdtfeger <schwer@us.ibm.com
> > wrote:
>
> Mark,
>
> I understand that. While that is true, the approach that Lisa was talking
> about in concept is in concept what she was asking for so there is no need
> to have an alternative shadow DOM strategy.
>
> Rich
>
>
> Rich Schwerdtfeger
>
> [image: Inactive hide details for Mark Sadecki ---08/19/2014 09:22:23
> AM---I think its probably best to refer to it as fallback content]Mark
> Sadecki ---08/19/2014 09:22:23 AM---I think its probably best to refer to
> it as fallback content in canvas.  I know associate Shadow DOM
>
> From: Mark Sadecki <mark@sadecki.com>
> To: Richard Schwerdtfeger/Austin/IBM@IBMUS
> Cc: Rik Cabanier <cabanier@gmail.com>, "lisa.seeman" <lisa.seeman@zoho.com>,
> "public-canvas-api@w3.org" <public-canvas-api@w3.org>
> Date: 08/19/2014 09:22 AM
>
> Subject: Re: Shadow Dom stuff
> Sent by: mark.sadecki@gmail.com
> ------------------------------
>
>
>
> I think its probably best to refer to it as fallback content in canvas.  I
> know associate Shadow DOM with the work that is being done in Web
> Components.
>
> mark
>
>
> On Tue, Aug 19, 2014 at 9:31 AM, Richard Schwerdtfeger <
> *schwer@us.ibm.com* <schwer@us.ibm.com>> wrote:
>
>    Canvas fallback content is a shadow DOM of sorts. I am confused.
>
>
>    Rich Schwerdtfeger
>
>    [image: Inactive hide details for Rik Cabanier ---08/15/2014 01:29:11
>    PM---On Wed, Aug 13, 2014 at 9:57 AM, lisa.seeman <lisa.seeman@zo]Rik
>    Cabanier ---08/15/2014 01:29:11 PM---On Wed, Aug 13, 2014 at 9:57 AM,
>    lisa.seeman <*lisa.seeman@zoho.com* <lisa.seeman@zoho.com>> wrote: >
>    Hi Folks
>
>    From: Rik Cabanier <*cabanier@gmail.com* <cabanier@gmail.com>>
>    To: "lisa.seeman" <*lisa.seeman@zoho.com* <lisa.seeman@zoho.com>>
>    Cc: "*public-canvas-api@w3.org* <public-canvas-api@w3.org>" <
>    *public-canvas-api@w3.org* <public-canvas-api@w3.org>>
>    Date: 08/15/2014 01:29 PM
>    Subject: Re: Shadow Dom stuff
>    ------------------------------
>
>
>
>
>
>
>
>    On Wed, Aug 13, 2014 at 9:57 AM, lisa.seeman <*lisa.seeman@zoho.com*
>    <lisa.seeman@zoho.com>> wrote:
>       Hi Folks
>       I was thinking that we need people to use the shadow DOM to make
>       existing inaccessible  Canvas implementations accessible and see how hard
>       it is and how to explain how to do it to developers.  (With the
>       understanding that we can not get everything working yet - like
>       magnification.)
>
>       Is anyone working on this?
>
>    Can you rephrase the question? Are you asking if someone is educating
>    authors?
>    Why would magnification not work?
>
>
>
>
>