This is an unpublished editor’s draft that might include content that is not finalized. View the published version

Skip to content

Technique H32:Providing submit buttons

About this Technique

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

This technique applies to content that includes form controls.

Techniques are examples of ways to meet Web Content Accessibility Guidelines (WCAG). They are not required to meet WCAG. Content can satisfy the normative requirements of WCAG even if it does not use any of the documented techniques. See About WCAG Techniques.

Description

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.

Examples

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">
</form>

Related Resources

No endorsement implied.

Tests

Procedure

  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
Back to Top