My recent post on the accessibility of Adobe Flex prompted a response from Adam Lehman, an employee of Adobe. His blog post humorously titled “Is Adobe Flex Really Accessible? You bet your robot voice it is!” talks about a few aspects of Adobe Flex which he claims makes it more accessible than the alternatives. Unfortunately, the issues raised in my original post remain, for the most part, unaddressed.
Adam says on his blog:
I think where Aaron had a rough time is that most of the accessibility information on Adobe.com for Flex needs to be updated. It looks like all of the information is based off of Flex 1.5. It’s definitely something that needs to be addressed and our accessibility team is working on it. I’m also willing to bet that all the applications Aaron tested weren’t the best examples of applications designed to be accessible.
I would point out that the applications I tested were those on the above mentioned site that were specifically recommended by Adobe as examples of accessible apps. It is not clear from Adam’s post whether or not those applications are also in need of being updated. It is also not clear if the Jaws scripts (which, as you will recall, I could not get to install on either of two machines) are also slated for update, as they were not mentioned at all.
It is great that Adobe seems to be actively working towards making Adobe Flex accessible. However, “working on it”, and actually being accessible are two very different things.
Again, if I am wrong, I would love to know about it, and I will of course update this blog with any new information. However, at this point, without having actually experienced an accessible Adobe Flex application, I can not recommend it as an accessible solution, though I do hope that that will change.
Sorry for the lack of comments. I’ll keep bugging the admins and hopefully we’ll have them soon. In the meantime, please feel free to email me at email@example.com (removing all of the hopefully spam-bot foiling q’s.)