Important note: This Wiki page is edited by participants of the RDWG. It does not necessarily represent consensus and it may have incorrect information or information that is not supported by other Working Group participants, WAI, or W3C. It may also have some very useful information.
Dynamic Content Accessibility
Page author(s): Peter Thiessen
Guidelines, Assistive Technologies, Clients
Until recently Assistive Technologies (AT) have linearly parsed information on a Web page with the assumption that this information is static. With the advent of AJAX and the ever developing HTML5/Web applications API, an assumption for static Web content is no longer prudent. Many Web applications contain desktop-like User Interfaces with complex dynamic content that without additional semantics and scripting best practices, can leave much, if not all of the information inaccessible to people with disabilities. The main specification to solve the accessibility gap for dynamic content is WAI-ARIA which adds roles, states and properties, and some best practices for scripting content, such as keyboard navigation to Web content/applications. Some research has been done on how well the ARIA specification fills this gap [*], and others[*], but much more is needed to better understand how well these gaps are filled and if and where hidden gaps exist.
Back to the list of topics.