•Conventional post/response creates
“history” and provides data to AT by it's nature. What about AJAX?
•Browser history may not be meaningful in an
AJAX app - so the means for users to go back/forth needs to be built into the
app
•How can AJAX apps provide information to
screen readers that the UI has changed without doing it in the UI where they
won't "see" it?
•As well as XHTML/CSS
techniques, consider:
–1. XmlHttpRequest usability and
accessibility
–2. DHTML and JavaScript accessibility
–3. Interaction model for AT and browser to
provide meta-UI
•Let’s consider these
in turn