On Tue, Mar 19, 2013 at 8:08 PM, Om <bigosma...@gmail.com> wrote:
> > To make this work we'd have to create our own graphics api class in JS > that > > was included. It could be really basic and allow use to use Flex skins, > > graphics calls and skins. The downside might be it sacrifices > > accessibility. But if it were up to me and that was the only reason why > we > > hesitate to use it I'd say let's output an accessible version at the same > > time. We can do that now. We didn't have that option before. Then screen > > readers will be satisfied and we can avoid a whole mess of problems. > > > > > SVG supports basic accessibility: http://www.w3.org/TR/SVG-access/ And > it > seems that we can make it more accessible by mixing with HTML as needed. > > Compared to this, drawing on the Canvas pretty much kills accessibility for > us. It would be much more work to make it accessible. > > On accessibility. We now have the Falcon compiler so we can create an accessible version at the same time. For example, at one agency I worked at we would create a Flash site for our clients and then another static HTML site for SEO and non-Flash enabled browsers. This was a while ago but it worked. We could probably make an optimized accessible version better than an all in one solution because we can throw out everything that's not needed. There was a thread from about a year ago that described a similar solution about adding things into the HTML wrapper page and creating a site map for SEO and deep linking. If Falcon enables it at some point in the time it is something we can think about doing. Thinking out loud here. ;)
