Re: Single Page Architecture General Concepts

Completely agree with proper focus management, updating title elements, the need for semantic markup and announcing change with aria-live. Also consider:
1. Ensuring the browser back/forward buttons behave in the same way as non SPA sites. (also a usability concern).
2. Applying additional context (visually hidden) as part of complex inter-page interactions.

Adam



> On 15 Jun 2016, at 1:44 am, Jim Homme <jhomme@benderconsult.com> wrote:
> 
> Hi,
> I’m a pretty good HTML person, and a very dangerous JavaScript and CSS person, but a very good screen reader user. Can anyone recommend a good place to go to understand the differences in approach in making single page architecture accessible, and how screen readers either react or do not react, and the various events involved in helping screen readers figure out when parts of pages load? I’d like to understand what developers need to look out for when writing code and unit testing.
>  
> Thanks so much.
>  
> Jim
>  
>  
> ==========
> Jim Homme,
> Accessibility Consultant,
> Bender HighTest Accessibility Team
> Bender Consulting Services, Inc.,
> 412-787-8567,
> jhomme@benderconsult.com
> http://www.benderconsult.com/our%20services/hightest-accessible-technology-solutions
> E+R=O
>