Control without programmatically determined name [F68]

Test info

Test for Success Criterion 1.3.1

About

Checked Elements: all

Checks for implicit associate of labels and input or select elements. Checks for text acting as a label for input or select elements. Checks for text acting as a label for input or select elements.

Short Description

This failure describes a problem that occurs when a form control does not have a name exposed to assistive technologies. The result is that some users will not be able to identify the purpose of the form control. <br> Reference: WCAG

WCAG 2.0

Principle 4: Robust

Content must be robust enough that it can be interpreted reliably by a wide variety of user agents, including assistive technologies. WCAG 2.0: Principle 4

Guideline 4.1: Compatible

Maximize compatibility with current and future user agents, including assistive technologies. Understanding Guideline 4.1

Success Criterion 4.1.2: Name, Role, Value (Level A)

For all user interface components (including but not limited to: form elements, links and components generated by scripts), the name and role can be programmatically determined ; states, properties, and values that can be set by the user can be programmatically set ; and notification of changes to these items is available to user agents , including assistive technologies . Note: This success criterion is primarily for Web authors who develop or script their own user interface components. For example, standard HTML controls already meet this success criterion when used according to specification. Understanding: Success Criterion 4.1.2

Techniques

F68: Failure of Success Criterion 4.1.2 due to a user interface control not having a programmatically determined name

Possible Results

text act as label: text act as label
no associated label: No associated label found for control
F68-pass2: F68-pass2
F68-pass1: F68-pass1