[access-uk] Re: AJAX and accessibility
- From: Léonie Watson <tink@xxxxxxxxxx>
- To: <access-uk@xxxxxxxxxxxxx>
- Date: Sat, 20 May 2006 18:14:22 +0100
Andrew,
Could you repost the URL? It sounds interesting.
Thanks,
Tink.
_____
From: access-uk@xxxxxxxxxxxxx [mailto:access-uk@xxxxxxxxxxxxx] On Behalf Of
Andrew Hodgson
Sent: Saturday, 20 May 2006 18:09
To: access-uk@xxxxxxxxxxxxx
Subject: [access-uk] Re: AJAX and accessibility
Hi,
The issue with Ajax is where you have multiple items on a webpage that
change, or the item that changes is not specificly where the virtual cursor
is in Jaws.
See the webpage I posted, it will explain the issue.
Andrew.
_____
From: access-uk@xxxxxxxxxxxxx [mailto:access-uk@xxxxxxxxxxxxx] On Behalf Of
Kevin Lloyd
Sent: 20 May 2006 17:23
To: access-uk@xxxxxxxxxxxxx
Subject: [access-uk] AJAX and accessibility
There was some discussion earlier of AJAX (Asynchronous Javascript and XML)
and it's inaccessibility with screen readers.
Coincidentally, I've just been taking a look at google suggest which I
believe actually uses AJAX. Basically, google suggest works like predictive
text when in keying your search words in the edit field. So, for example, I
just typed the letter C and the edit field was prefilled with currency
convertor. I then added letter A and the field changed to cars. The
predictive nature is based on your previous google searches and then the
most popular search strings as used by the general population.
You can arrow up and down in the edit field and you'll see similar search
terms to what you've keyed. Another example, is that I've just keyed the
letters d and o and it prefilled with dogs. I pressed down arrow to find
the field chane to download.com
No doubt there will be some implementations of AJAX that may cause some
accessibility issues but the google suggest implementation of the technology
looks to be very accessible with JAWS.
You can find google suggest at
http://www.google.com/webhp?complete=1
<http://www.google.com/webhp?complete=1&hl=en> &hl=en
Regards.
Kevin
E-mail: kevin.lloyd3@xxxxxxxxxxxxxx
Other related posts: