Providing submit buttons

Important Information about Techniques

See Understanding Techniques for WCAG Success Criteria for important information about the usage of these informative techniques and how they relate to the normative WCAG 2.2 success criteria. The Applicability section explains the scope of the technique, and the presence of techniques for a specific technology does not imply that the technology can be used in all situations to create content that meets WCAG 2.2.


Content that includes form controls.

This technique relates to Success Criterion 3.2.2: On Input (Sufficient when used with G80: Providing a submit button to initiate a change of context).


The objective of this technique is to provide a mechanism that allows users to explicitly request changes of context. The intended use of a submit button is to generate an HTTP request that submits data entered in a form, so it is an appropriate control to use for causing a change of context.


Example 1: A basic example of a form with a submit button

<form action="/subscribe" method="post">
 <p>Enter your email address to subscribe to our mailing list.</p>
 <label for="address">Your email address:</label>
 <input autocomplete="email" id="address" name="address" type="text"> 
 <input type="submit" value="Subscribe">


Resources are for information purposes only, no endorsement implied.



  1. Find all forms in the content.
  2. For each form, check that it has a submit button (<input type="submit">, <input type="image">, or <button type="submit">).

Expected Results

  • #2 is true