WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Ajax, circa 2008 and beyond

for

From: Phil Teare
Date: Jul 16, 2008 9:20AM

Yes and GWT of course.

And I'm finding good old MSDN quite useful re ARIA. Its already listing the
various objects, properties, etc... amongst its DHTML pages.

But its worth noting that for many, ARIA won't be useful for a few years
yet. However acceptance is looking very positive alround for the future.


Phil


Phil Teare,
CTO & Chief Architect,
http://www.textic.com from Textic Ltd.
(44) [0] 208 4452871

2008/7/16 Sandra Clark < <EMAIL REMOVED> >:

> Check out WAI-ARIA which attempts to address Accessibility and RIA's
> (specifically Ajax).
>
>
>
> Both WCAG 2.0 and the Section 508 refresh address ARIA in their
> requirements
> for dynamic pages to provide properties, roles and states, which WAI-ARIA
> specifies.
>
>
>
> Firefox 2+, IE8 Beta 1 currently support ARIA as does Window-Eyes 5.5, Jaws
> 9 and newer versions of the Mac OS. Javascript frameworks supporting it
> are
> AxsJax and Dojo Toolkit. JQuery will be providing it in a future buid.
>
>
>
>
>
> Sandra Clark
>
> ============>
> http://www.shayna.com <http://www.shayna.com/>;
>
> Training and Consulting in CSS and Accessibility
>
> Team Fusebox
>
>
>
>
>
>
>
> From: <EMAIL REMOVED>
> [mailto: <EMAIL REMOVED> ] On Behalf Of Tech
> Sent: Tuesday, July 15, 2008 1:51 PM
> To: WebAIM Discussion List
> Subject: [WebAIM] Ajax, circa 2008 and beyond
>
>
>
> At Webaim.org, I can find some fairly dated articles (2005) about Ajax and
> accessibility. Could someone please point me to a good list of links with
> some really current discussion about Ajax adoption, standards, etc.
>
> With so many Ajax-based applications now online, and coming, I'm
> particularly curious about how government and education are adjusting to
> this new world of interface widgets.
> Perhaps I am just a dumb, selfish developer, but it would seem that the
> days
> of the non-ajaxed interface are numbered. Economic realities, and the
> 80/20
> rule will conspire to ensure that few new projects are just not going to
> expend much effort in building dual interfaces for the majority of
> applications. If for no other reason, than non-javascript interfaces are
> hard, and painfully boring to work on. Who even wants to do that work in
> most business environments, unless forced to?
>
> Google Docs doesn't seem to be too concerned with addressing this, nor
> countless other sites. So what does this mean, long term? Smarter, more
> informed people than I must be discussing this realistically, and
> eloquently, but I'm having trouble finding anything very comprehensive or
> current (except here, of course).
>
> Thoughts, links, welcomed.
>
>
>
>