Techniques for WCAG 2.0

Skip to Content (Press Enter)

-

FLASH10: Indicating required form controls in Flash

Applicability

This technique relates to:

User Agent and Assistive Technology Support Notes

See User Agent Support Notes for FLASH10.

Description

The objective of this technique is to provide a clear indication that a specific form control in a Web application or form is required for successful data submission. The word "required" is added to the form control's accessible name, and a visual indicator is placed next to the label.

Examples

Example 1: Adding the word "required" to the control's accessible name

This example shows how to use the Accessibility panel to indicate a field as being 'required' to users:

  1. Visually, place asterisk character or some other indication adjacent to the form control's label.

  2. Use the Accessibility panel to combine the word "required" with the control's label in the "Name" field.

This approach is illustrated in the screenshot below:

Using the Accessibility panel to indicate a form control as being   required

This is demonstrated in the working example of Adding the word "required" to the control's accessible name. The source of Adding the word "required" to the control's accessible name is available.

Tests

Procedure

For each required form control within a Flash movie, confirm that:

Expected Results

If this is a sufficient technique for a success criterion, failing this test procedure does not necessarily mean that the success criterion has not been satisfied in some other way, only that this technique has not been successfully implemented and can not be used to claim conformance.

Techniques are Informative

Techniques are informative—that means they are not required. The basis for determining conformance to WCAG 2.0 is the success criteria from the WCAG 2.0 standard—not the techniques. For important information about techniques, please see the Understanding Techniques for WCAG Success Criteria section of Understanding WCAG 2.0.