Rich Colaggero, one of the accessibility experts at MIT, sent this
article to me and I thought I'd forward the address to you:
http://www.research.ibm.com/journal/sj/443/hoffman.html
The article talks about how architecture can affect accessibility, and
recommends how to ensure dynamic web applications remain accessible. The
conclusion is that there should be alternate views available based on
persons' needs (TILE, anyone?), but also suggests:
1) Making architecture decisions with usability and accessibility in
mind, rather than including them at the end of the design process or (worse)
implementation;
2) Creating reusable objects that contain accessibility elements, for
greater consistency and accessibility (JSF widgets);
3) Supplementary information that adds context for screen reader users
(such as title tags and extended label descriptions);
4) Designing error messages that allow users to "recover gracefully."
I'd be interested in hearing how close you feel we are to implementing
their suggestions!