456 Berea Street
23rd Oct 2007, 09:17 am
In January this year I complained about Adobe Spry and obtrusive, inaccessible JavaScript (http://www.456bereastreet.com/archive/200701/adobe_spry_and_obtrusive_inaccessible_javascript/). Spry (http://labs.adobe.com/technologies/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 (http://blogs.adobe.com/spryteam/2007/10/spry_16_and_the_dreamweaver_up.html) 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 (http://labs.adobe.com/technologies/spry/demos/) now use progressive enhancement
Real links can be used to trigger events, providing for full keyboard navigation supportThe people on the Spry team have also written a series of articles on Best Practices with Spry (http://labs.adobe.com/technologies/spry/articles/best_practices/) 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.
Visit site to read or post comments… (http://www.456bereastreet.com/archive/200710/adobe_spry_16_improves_standards_support_adds_prog ressive_enhancement/#comments)Add 456 Berea Street to your Technorati favorites. (http://technorati.com/faves?add=http://www.456bereastreet.com)
Posted in Accessibility (http://www.456bereastreet.com/archive/categories/accessibility/), JavaScript (http://www.456bereastreet.com/archive/categories/javascript/), Web Standards (http://www.456bereastreet.com/archive/categories/web_standards/).
http://feeds.feedburner.com/~a/456bereastreet?i=kvmNzF</img> (http://feeds.feedburner.com/~a/456bereastreet?a=kvmNzF)
http://feeds.feedburner.com/~f/456bereastreet?i=Ouq3i6a</img> (http://feeds.feedburner.com/~f/456bereastreet?a=Ouq3i6a) http://feeds.feedburner.com/~f/456bereastreet?i=7jHVE5a</img> (http://feeds.feedburner.com/~f/456bereastreet?a=7jHVE5a) http://feeds.feedburner.com/~f/456bereastreet?i=kukgDxa</img> (http://feeds.feedburner.com/~f/456bereastreet?a=kukgDxa) http://feeds.feedburner.com/~f/456bereastreet?i=3fGNlva</img> (http://feeds.feedburner.com/~f/456bereastreet?a=3fGNlva)
http://feeds.feedburner.com/~r/456bereastreet/~4/173421895
More... (http://feeds.feedburner.com/~r/456bereastreet/~3/173421895/)
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 (http://blogs.adobe.com/spryteam/2007/10/spry_16_and_the_dreamweaver_up.html) 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 (http://labs.adobe.com/technologies/spry/demos/) now use progressive enhancement
Real links can be used to trigger events, providing for full keyboard navigation supportThe people on the Spry team have also written a series of articles on Best Practices with Spry (http://labs.adobe.com/technologies/spry/articles/best_practices/) 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.
Visit site to read or post comments… (http://www.456bereastreet.com/archive/200710/adobe_spry_16_improves_standards_support_adds_prog ressive_enhancement/#comments)Add 456 Berea Street to your Technorati favorites. (http://technorati.com/faves?add=http://www.456bereastreet.com)
Posted in Accessibility (http://www.456bereastreet.com/archive/categories/accessibility/), JavaScript (http://www.456bereastreet.com/archive/categories/javascript/), Web Standards (http://www.456bereastreet.com/archive/categories/web_standards/).
http://feeds.feedburner.com/~a/456bereastreet?i=kvmNzF</img> (http://feeds.feedburner.com/~a/456bereastreet?a=kvmNzF)
http://feeds.feedburner.com/~f/456bereastreet?i=Ouq3i6a</img> (http://feeds.feedburner.com/~f/456bereastreet?a=Ouq3i6a) http://feeds.feedburner.com/~f/456bereastreet?i=7jHVE5a</img> (http://feeds.feedburner.com/~f/456bereastreet?a=7jHVE5a) http://feeds.feedburner.com/~f/456bereastreet?i=kukgDxa</img> (http://feeds.feedburner.com/~f/456bereastreet?a=kukgDxa) http://feeds.feedburner.com/~f/456bereastreet?i=3fGNlva</img> (http://feeds.feedburner.com/~f/456bereastreet?a=3fGNlva)
http://feeds.feedburner.com/~r/456bereastreet/~4/173421895
More... (http://feeds.feedburner.com/~r/456bereastreet/~3/173421895/)