Adobe Spry 1.6 improves standards support, adds progressive enhancement

In January this year I complained about Adobe Spry and obtrusive, inaccessible JavaScript. Spry is yet another JavaScript library that features Ajax helpers and various effects and behaviours. The problem was that the examples on the demo site used non-standard and obtrusive code, and as we all know examples get copied and used as is regardless of how many warnings there are.

I didn't expect things to change and dismissed Spry as something that can't be used in the real world, at least not if you care about Web standards and accessibility. Well, I may need to change my mind about that. The reason is that I found out from the post Spry 1.6 and the Dreamweaver Updater on the Spry Team blog that Spry 1.6 has in fact improved support for both Web standards, accessibility and progressive enhancement. That's good news of course.

Some of the changes in Spry 1.6:

  • You can now use the framework without breaking validation
  • Several of the examples in the Spry Demo Gallery now use progressive enhancement
  • Real links can be used to trigger events, providing for full keyboard navigation support

The people on the Spry team have also written a series of articles on Best Practices with Spry and made several demos of Spry used unobtrusively.

It's not perfect yet, but it's encouraging to see Adobe improving Spry in these areas.

Posted on October 22, 2007 in JavaScript, Accessibility, Web Standards