My understanding is that this ajax technology doesn't behave real
well for screen readers, but having never used it, I can't confirm
this for myself.
What I can though is that unless the updated text is in a separate
frame, it's a *lot* of work to get to it using voiceover. The other
problem is that generally, voice over gives no indication the page
changed. Also, with the current implementation of voiceover and
safari, there's no way to jump to a place in the current document,
any page that does this simply puts vo back at the top of the page at
worst, or leaves it in the same place at best.
Now, with that said:
I'm not opposed to testing a site for you. As long as it doesn't use
flash. I really hate flash.
On Apr 18, 2006, at 11:59 AM, Joe Clark wrote:
I have a Web usability test coming up-- a really quick one using an
Ajax application. Ajax, which used to be an acronym but is now just
a word, refers to using scripting to cause parts of a page to
update without refreshing the whole page. (If you've ever used
Gmail, you've been using Ajax.)
I'm giving a presentation on Ajax accessibility and am looking for
a handful of people to carry out three tasks on a real Web site
that will be set up with a demo account. I'm looking for VoiceOver
testers.
The good news? You get credited in the ultimate presentation notes.
The bad news? There ain't no money in it.
Let me know if you're interested.
--
Joe Clark | [EMAIL PROTECTED]
Accessibility <http://joeclark.org/access/>
Expect criticism if you top-post
