AJAX and 508 Accessibility
24 Mar 2005 - 9:58am
1 reply
1001 reads
Todd Warfel
2003
Anyone have any ideas what impact AJAX has on 508 compliance? How
easy/difficult it is to make it 508 compliance? Many screen readers
only reread the page upon page loads (or used to). Has this changed?
Yet another challenge in the RIA bucket - but I still think they're
fascinating.
Cheers!
Todd R. Warfel
Partner, Design & Usability Specialist
MessageFirst | making products easier to use
--------------------------------------
Contact Info
V: (607) 339-9640
E: twarfel at messagefirst.com
W: messagefirst.com
AIM: twarfel at mac.com
Blog: http://toddwarfel.com/
--------------------------------------
Problems are just opportunities for success.
Get the feed
Comments
On 24 Mar 2005, at 14:58, Todd Warfel wrote:
> [Please voluntarily trim replies to include only relevant quoted
> material.]
>
> Anyone have any ideas what impact AJAX has on 508 compliance? How
> easy/difficult it is to make it 508 compliance? Many screen readers
> only reread the page upon page loads (or used to). Has this changed?
It hasn't changed to the best of my knowledge, so you're going to need
to provide accessible alternatives if you want 508/WAI/whatever
compliance.
Ajax offers other challenges too (e.g. what should the back button do?)
Fortunately people do seem to have started thinking about these (see
<http://del.icio.us/tag/ajax+usability> for some links).
Cheers,
Adrian