I’ve had a tab open in firefox for the majority of my holiday weekend…for two reasons. 1, the influx of visitors I’ve had has left me staring at my google analytics page a bit more than it should have but more importantly, the contents of that tab were something i needed to take some time to think about. I discovered a small, open source project called Flash Aid. This project aims to use a small, 1px square flash embedded object to detect usability features of a users computer and use them in Ajax applications (such as a screen reader, as many other bloggers have pointed out).
I think my internal questioning started because of some of my own preconceived notions of Flash that flash is anything but accessible to begin with. So i turned to a friend/coworker Arthur Dickerson with the question: what does “flash accessibility mean”. From our brief conversation over IM, and a useful link he sent me, it seems that the big feature of the accessibility class for flash is screen reader interaction. While the methods of this class are static, that is, always available without instantiating the class, they seem to be more tedious than complicated to implement. From Macromedia - best Practices for Accessible Flash Design *warning..this is a “flash paper” document. Kinda like acrobat, but flash. ironically, my scroll wheel did NOT work which made reading it a chore :-)* this class seems to feature things like :a “motion alt text”, provide context, control reading order, enabling key access to various components, captioning, and providing control over audio playback.

Ok, fine. That’s a fair amount of good stuff to be including. But I guess I still don’t get how this is useful in AJAX application? Since Ajax is simply super dynamic content, but the structure of that content is (supposed to be) XHTML and css (which are, if built correctly, inherently accessible), how can access to this flash class be helpful?

I understand the need for usability and accessibility considerations in ajax design/development. I found this description of some accessablity considerations that should be taken when building ajax forms. It suggests notification of a lack of javascript support (and therefore an unusable form for that user), informing the user of dynamic page updates, update alerts, and highlighting of updated areas. These are all great ideas, and I agree fully with them, but once again…I don’t see where that flash class can do what javascript/xhtml/css can’t.

I always applaud people for trying to make things better for ALL users, but can someone explain to me what I’m missing here?

>More about Flash 8 Accessability features here

one more post for the day. litebox does the same thing (and is practically identical as far as i can tell) to Lokesh’s Lightbox v2.0, except it uses the moo.fx effect library from mad4milk.net instead of prototype and scriptaculous. This allows it to have a significantly smaller javascript footprint and accomplish all of the same things. 1/4 the size, in fact. If you’re into javascripty stuff at all, and havent already, check out the mad4milk stuff ASAP. its pretty sweet (and well documented for a change). Schwiggity.