navsubtree proposal for accessible canvas and Issue 74

Mike (Cooper),

Please create a straw poll to discuss on Thursday. The group feels it has
addressed the adom accessibility compliance confusion with this proposal
and also the default for keyboard navigation made at the last html task
force meeting. Members must vote on this by the end of Wednesday so that we
can review the results Thursday. This also allow for areamap to be used in
the future should a proposal by Chaals be approved for areamap.

The justification for this change is to provide for a focus navigable
binding of what is rendered in canvas using standard HTML elements in the
area currently designated as the fallback content for <canvas> and provides
the means for the browser to provide an accessibility API binding based on
HTML 5 content.

(See attached file: canvaselement-issue74-feedback1.html)

Rich Schwerdtfeger
Distinguished Engineer, SWG Accessibility Architect/Strategist