- From: Charles Pritchard <chuck@jumis.com>
- Date: Wed, 26 Feb 2014 19:32:24 -0800
- To: Rik Cabanier <cabanier@gmail.com>
- Cc: Dominic Mazzoni <dmazzoni@google.com>, Mark Sadecki <mark@w3.org>, Richard Schwerdtfeger <schwer@us.ibm.com>, Jatinder Mann <jmann@microsoft.com>, Canvas <public-canvas-api@w3.org>
> On Feb 26, 2014, at 2:18 PM, Rik Cabanier <cabanier@gmail.com> wrote: > > That being said, I was in favor of including all of hit region but mark it as at-risk. Once we then go to CR, we can strip it down to what is implemented. Is there something we as authors can do to encourage vendors to put in the resources necessary to complete this part of the spec? Now that all parties have agreed to allow the functionality (no small feat) and all vendors are highly supportive of a11y... What is blocking implementation?
Received on Thursday, 27 February 2014 03:32:48 UTC