Has anyone faced any issues with using AJAX with update panels and keeping their sites 508/ Accessibility compliant? Is there a way to detect that javascript is turned off and force update panels to work as synchronous?
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Has anyone faced any issues with using AJAX with update panels and keeping their sites 508/ Accessibility compliant? Is there a way to detect that javascript is turned off and force update panels to work as synchronous?
Section 508 guidelines are moving toward WCAG 2.0.
http://www.access-board.gov/sec508/refresh/draft-rule.htm#e107
WAI-ARIA is a critical technology for making dynamic web sites accessible. This relates directly to using UpdatePanels. Using WAI-ARIA tags, assistive technology can receive notifications from the browser, via the accessibility API, that a panel has been updated. Using WAI-ARIA, you don’t have to be as concerned about making a synchronous request for new content. However, if you are still concerned, look into using a technique called ‘progressive enhancement.’
Using the WAI-ARIA approach will move your application toward the future of accessibility and have it in good shape for the 508 harmonization with WCAG 2.0.
This is a big topic, so you’ll likely have more questions.