When any component receives focus, it does not initiate a change of context. (Level A)

Rationale

Users navigating content should be able to predict the circumstances that trigger a change of context. UI components receiving focus must not automatically change the context of the screen content.

Note that changes to the content do not always cause a “change of context”. The following examples of context changes are not accessible:

  • Forms submitted automatically when a component receives focus.
  • New windows launched when a component receives focus.
  • Focus is changed to another component when a component receives focus.

Note: Some compound documents and their user agents are designed to provide different viewing and editing functionality depending on which portion of the compound document the user moves focus to. For example, a presentation can contain an embedded spreadsheet where menus and toolbars change based upon whether the user interacts with the presentation content or the embedded spreadsheet content. If an additional mechanism, such as a menu choice or special keyboard command, allows this change of context, then even though a focus change may trigger this context change, such a compound document would include a means of changing context without a change of focus and so would pass (per WCAG2ICT Guidelines)

Refer to Understanding SC 3.2.1 for more information (external link to WCAG).

Development Techniques

Review the General techniques as well as other tabs applicable to your technology.  Prioritize the use of technology-specific techniques, and implement the General techniques as needed. You are always required to find, understand and implement accessible code techniques to meet the checkpoint. The documented techniques and supplements are not exhaustive; they illustrate acceptable ways to achieve the spirit of the checkpoint. If numbered, techniques are in order of preference, with recommended techniques listed first. Where used, IBM information that complements the WCAG techniques is indicated as supplemental.

General techniques

Any item in this section represents a technique deemed sufficient. Ensure you review WCAG Common Failures to avoid development mistakes.

Web (HTML, ARIA, CSS) techniques

There are no specific Web (HTML, ARIA, CSS) techniques for this checkpoint. Refer to the General techniques section.

Mobile Native (iOS) techniques

There are no specific Mobile Native iOS techniques for this checkpoint. Refer to the General techniques section.

Eclipse techniques

There are no specific Eclipse techniques for this checkpoint. Refer to the General techniques section.

Windows-based (MSAA+IA2) techniques

There are no specific Windows-based (MSAA+IA2) techniques for this checkpoint. Refer to the General techniques section.


Most links in this checklist reside outside ibm.com at the Web Content Accessibility Guidelines (WCAG) 2.0. W3C Recommendation 11 December 2008: http://www.w3.org/TR/WCAG20/

Copyright © 1994-2017 World Wide Web Consortium, (Massachusetts Institute of Technology, European Research Consortium for Informatics and Mathematics, Keio University, Beihang University). All Rights Reserved.

Copyright © 2001, 2017 IBM Corporation