• Skip to primary navigation
  • Skip to main content
  • Skip to primary sidebar
Logo for DigitalA11Y

Digital A11Y

Your Accessibility Partner

  • About
  • Articles
  • WAI-ARIA
  • WCAG
  • Resources
    • Cheat Sheets
    • A11Y Blogs
    • A11Y Toolkit
  • Contact
You are here: Home / Web Accessibility / WCAG / Understanding SC 3.2.2 on Input

Understanding SC 3.2.2 on Input

Last Modified: July 9, 2019 by Raghavendra Satish Peri 4 Comments

3.2.2 On Input: Changing the setting of any user interface component does not automatically cause a change of context unless the user has been advised of the behavior before using the component. (Level A)

This success criterion conveys that change of context should not occur while user is trying to input data. For example, if the user is filling a form & if the page refreshes while selecting an option in <select> element or if the form submits after the user fills in the last form field, it fails this checkpoint. User should be provided with an option to submit the form by providing a submit button or hint/instruction should be provided for all users informing that form will submit once the form fields are filled

Exceptions

There are some exceptions to this success criterion. Change of content is not change of context. For example if a radio button is selected & if it triggers more form controls it is not change of context. Here content is updating. Activating links, buttons or tab controls doesn’t fall into on input category. Here is user is taking deliberate action to trigger these form controls…

Points to Remember

  • Make sure that forms don’t submit on input of data.
  • Make sure that focus doesn’t move to next form control once a form field is populated with data.
  • Provide a submit button for all forms.
  • Make sure that control of how data is populated is in the hands of your users.
  • If there is a change of context, then provide an instruction that is available for all user groups.

References

Understanding Success Criterion 3.2.2

Share A11Y Love

  • Twitter
  • LinkedIn
  • Facebook
  • Reddit

More Accessibility Articles

Filed Under: WCAG

About Raghavendra Satish Peri

Raghavendra Satish Peri is a digital accessibility evangelist working at Deque Systems as Product Manager [Accessibility]breaking web accessibility & mobile accessibility challenges. He authors an Accessibility Blog at DigitalA11Y.com & is galvanizing the adoption of accessibility by inspiring the local tech community with meetups and mentorship. He propelled this thought by founding HelloA11y.com, a community of accessibility professionals, developers and enthusiasts. When away from his computer, Raghava can be found at local cafes & restaurants sampling cuisines, attending local meetups, listening to audio books or writing on his Personal Blog at raghava.in.

Reader Interactions

Comments

  1. Monique says

    January 30, 2020 at 1:23 am

    In the documentation for understanding this guideline, focus is listed under “change of context” in the Key Terms section.

    https://www.w3.org/TR/UNDERSTANDING-WCAG20/consistent-behavior-unpredictable-change.html

    Does this mean that if you submit a form to filter results, if the page refreshes and the user has lost focus, that this would classify as a change in context?

    Thanks so much!

    Reply
    • Raghavendra Satish Peri says

      February 14, 2020 at 7:05 am

      Hello Monique,
      There is a lot of difference between change of context & change of content. Change of content is not failure of this SC, if you submitted a form using the submit button & page refreshes then it’s not a failure. But if you selected a checkbox or a radio button option & page refreshed then its failure of this SC. Hope this is helpful.

      Reply
  2. Jahnvi says

    April 28, 2020 at 9:41 pm

    Hi Raghav,

    If I Describing what will happen before I make a selection for the radio button/ Checkbox, would that be considered as success criteria?

    E.g. Selecting a radio button/ checkbox will move over to the next question something like that. (No submit buttons)

    Reply
    • Raghavendra Satish Peri says

      April 29, 2020 at 10:10 am

      Hi Jahnvi,
      Yes, if you can provide the instruction visually & let all the user groups know that a change of context will trigger when an option is selected then it passes this checkpoint.

      Reply

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Primary Sidebar

Get Digital A11Y in Your Inbox

Recent A11Y Articles

  • A Sneak peek into WCAG 3.0 First Public Draft
  • Understanding SC 4.1.3 Status messages
  • Understanding SC 2.5.4 Motion Actuation
  • Understanding SC 2.5.3 Label in Name
  • Knowbility looking for mentors in its Accessible Internet Rally

Recent Comments

  • Raghavendra Satish Peri on Foresee Your Colors: Tools to Evaluate your design for Color contrast Accessibility
  • Raghavendra Satish Peri on Digital Accessibility Companies Roundup
  • Andrew Somers on Foresee Your Colors: Tools to Evaluate your design for Color contrast Accessibility
  • Regine Lambrecht on Digital Accessibility Companies Roundup
  • william hruska on 18 Free Mobile Accessibility Testing Tools

A11Y Categories

  • Design
  • Events
  • HTML
  • IOS
  • Mobile Accessibility
  • News
  • Tools
  • WAI-ARIA
  • WCAG
  • Web Accessibility

  • Privacy Policy
  • Sitemap
© 2021 Digital A11Y