Thread Subject: Re: Gaps in Web requirements - page andelementrefresh
This archival content is maintained by WebAIM and NCDAE on behalf of TEITAC and the U.S. Access Board . Additional details on the updates to section 508 and section 255 can be found at the Access Board web site.
From: Hoffman, Allen
Date: Mon, Dec 18 2006 6:50 AM
- Return to this mailing list's archives
- View all messages in this thread
- Next message in thread: Barrett, Don: "Re: Gaps in Web requirements - page andelementrefresh"
- Previous message in thread: Andi Snow-Weaver: "Gaps in Web requirements - page and elementrefresh"
- Messages sorted by: Author | Thread | Date
Kate Walser wrote:
Web page and element refresh resulting from user action - Entire page or
parts of the page refreshing when user takes some action such as
selecting an item from a drop-down list. Savvy developers have created
ways to address this (e.g., have the refresh point to an anchor tag near
the element that caused the refresh so the assistive technology picks up
there) This will become more important with rich Internet applications
and ability to change screen elements without server calls. No clear
synergy with existing standard - maybe some synergies with 1194.21 c
Do we need an additional requirement to address this situation?
I believe we do. This goes directly to the heart and problems now being
encountered with "web 2.0" "AJAX" web applications. Adopting something
specifically from 1194.21(c) seems like the logical starting point.
Department of Homeland Security Office on Accessible Systems &
- Next message in Thread: Barrett, Don: "Re: Gaps in Web requirements - page andelementrefresh"
- Previous message in Thread: Andi Snow-Weaver: "Gaps in Web requirements - page and elementrefresh"