Understanding 3.2.1 On Focus

Anything that receives focus should not change context. For example any component that is able to trigger an event such a submit button on a form or a link that opens a new tab or window. 

All functionality of a website should be predictable as users navigate around. 

• Example: If someone is tabbing through a dropdown menu and lands on a menu item, it should not take them to that new page until it is activated by the enter key on the keyboard. At the same time if they escape out of the menu the context should not change when they get out of the menu.
  
  

How AudioEye Helps

AudioEye automatically applies the necessary fixes to warn users when links open a new window.

If content changes are triggered automatically when a component receives focus, AudioEye will alert Managed customers if a  3.2.1 violation is detected and can take action with customer approval. However, for instances where Managed customers do have full control to remediate the source issue, AudioEye will collaborate with accessibility stakeholders to instruct them on what specific changes are required, why the changes are important, and how the changes can be implemented.

Recommended Solutions

Ensure that when focus is on an element to not trigger any changes of context unless it is activated by the user. Allow the user to control the activation via the return/enter key on their keyboard.