W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > July to September 2012

RE: Testing flash techniques

From: Jonathan Avila <jon.avila@ssbbartgroup.com>
Date: Mon, 20 Aug 2012 11:23:34 -0400
Message-ID: <51df46cbc93a8928fb318fce002028b2@mail.gmail.com>
To: Jan Eric Hellbusch <hellbusch@2bweb.de>, w3c-wai-ig@w3.org
[Jan wrote] I could put the question differently: What software is
suitable for testing Flash accessibility (besides a screen reader)?

Microsoft Object Inspector and the Accessible Event Watcher which are part
of the Windows 7 SDK are very useful.  aDesigner along with some of the
other MSAA based tools are good also.

I posted a blog on where to find the tools:

A colleague posted another blog on the use of the tool:


-----Original Message-----
From: Jan Eric Hellbusch [mailto:hellbusch@2bweb.de]
Sent: Monday, August 20, 2012 11:07 AM
To: w3c-wai-ig@w3.org
Subject: Testing flash techniques

Hi all,

in the Adobe Flash techniques at

there are references to "aDesigner2" in the testing sections.

After searching for the software with various methods, I was able to find
a link by translating a Japanese page. Via IBM research I was directed to

Now I am wondering why the software was so hard to find. Is there any
background information on aDesigner? The WCAG techniques refer to
aDesigner2, but the current version on the page is 1.0 from 2012/06. Is
there a reason for the different version numbers?

I could put the question differently: What software is suitable for
testing Flash accessibility (besides a screenreader)?


Jan Eric Hellbusch
Tel.: +49 (231) 86436760 oder +49 (163) 3369925
Web: http://2bweb.de     Twitter: www.twitter.com/2bweb
Das Buch über barrierefreies Webdesign:
"Barrierefreiheit verstehen und umsetzen - Webstandards für ein
zugängliches und nutzbares Internet"
812 Seiten, Dpunkt Verlag (2011)
Received on Monday, 20 August 2012 15:24:10 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:36:41 UTC