Changes of context are initiated only by user request or a mechanism is available to turn off such changes.
Testing & RemediationHow to test: Open your website in your browser of choice and begin examining your content for places where changes of context occur. During instances where user input changes context on a page (entering information into a form causing an AJAX change, redirecting the user to a new page upon modifying elements in a form, etc.), confirm that the user is required to authorize the change to continue. How to remediate: The type of remediation technique will depend on how your site is using content:
- If your page/content allows for automatic updates, you must provide a mechanism for the user to request the updating of the content instead of having it update automatically
- If you have any automatic redirects in place, implement them server-side instead of client-side
- If your page uses pop-up windows, use the target attribute to open a new window upon user request & indicate this in the link text. You can also use progressive enhancement to open new windows on user request.
- If using an onchange event on a select element, use the onchange event without causing a change of context
Questions and Answers
Your site should have the correct semantic elements (header, main, footer, article, etc) in the order that they are intended to be read. This means that sometimes this isn't the order that makes styling the page the easiest. You must also ensure that all your heading levels are hit in the order. This means that you should not skip from an h1 to an h4, and so on.
This question depends on a number of factors including size of site, desired level of conformance, your developer's understanding of accessibility techniques, etc. Accessible Web is here to help. Reach out and we can discuss your site specifically.