From MemberWiki
OAA Rules Home |
WCAG 2.0 Summary of Rules |
Rule Category Summary of Rules |
Abbreviation Rules |
Audio Rules |
Color Rules |
Embedded Application Rules |
Form Control Rules |
Heading Rules |
Image Rules |
Landmark Rules |
Language Rules |
Layout Rules |
List Rules |
Link Rules |
Page Navigation Rules |
Scripting Rules |
Table Rules |
Timing Rules |
Title Rules |
Video Rules |
Widget Rules
Form Control Rule Details
Form Control 1: Controls must/should have labels
| Property
| Value(s)
| Up To Date
|
| Definition
| TEXTAREA, SELECT and INPUT elements of type TEXT, PASSWORD, CHECKBOX, RADIO and FILE must/should have an accessible label
| yes
|
| Summary
| Controls must/should have labels
| yes
|
| Purpose
|
- A label associated with a form control insures that information about the form control is spoken by screen readers when it receives focus
| yes
|
| Rule ID
| CONTROL_1
| yes
|
| NLS Rule ID
| Form Control 1
| yes
|
| Techniques
|
- The preferred technique for labeling for controls is using the LABEL element and referencing the ID attribute value of the form control element
- Use the LABEL element to encapsulate the form control element
- In special cases, use ARIA-LABELLEDBY attribute to reference the id(s) of the elements on the page that describe the purpose of the form control element
- In special cases, use ARIA-LABEL attribute to provide a explicit text description of the purpose of the form control element
| yes
|
| Manual Checks
| none
| yes
|
| Scope
| Element
| yes
|
| WCAG 2.0 Primary
| 3.3.2
| yes
|
| WCAG 2.0 Related
|
| yes
|
| Language Dependency
| empty string
| yes
|
| Rule Category
| Form Control
| yes
|
| Target Resources
|
- input[type="checkbox"]
- input[type="radio"]
- input[type="text"]
- input[type="password"]
- input[type="file"]
- select
- textarea
| yes
|
| Target Resources Description
| User interface form controls
| yes
|
| Resource Properties
|
- computed_label
- fieldset_element
- computed_label_source
- name_attribute
| yes
|
Form Control 1: Rule Result Messages
| Property
| Value(s)
| Up To Date
|
| All Pass: Singular
| Form control has label
| yes
|
| All Pass: Plural
| %N_P form controls have a label
| yes
|
| Manual Check: Singular
| empty string
| yes
|
| Manual Check: Plural
| empty string
| yes
|
| Some Fail
| %N_F out of %N_T form controls do NOT have a label
| yes
|
| All Fail: Singular
| form control does NOT have label
| yes
|
| All Fail: Plural
| All %N_F form controls do NOT have a label
| yes
|
| Corrective Action: Singular
| add label to form control missing a label
| yes
|
| Corrective Action: Plural
| add labels to %N_F form controls missing a label
| yes
|
| Not Applicable
| No form controls on this page
| yes
|
Form Control 1: Node Result Messages
| Property
| Value(s)
| Up To Date
|
| Pass 1
| %1 control has label
| yes
|
| Pass 2
| empty string
| yes
|
| Pass 3
| empty string
| yes
|
| Manual Check 1
| empty string
| yes
|
| Manual Check 2
| empty string
| yes
|
| Manual Check 3
| empty string
| yes
|
| Corrective Action 1
| Add label to %1 control
| yes
|
| Corrective Action 2
| empty string
| yes
|
| Corrective Action 3
| empty string
| yes
|
| Hidden (i.e. thru css)
| %1 control is hidden from assistive technologies.
| yes
|
| Presentation (i.e. role=presentation)
| empty string
| yes
|
| Other
| empty string
| yes
|
Form Control 2: Image button must/should have alt content
| Property
| Value(s)
| Up To Date
|
| Definition
| Every INPUT type IMAGE must/should have an ALT or TITLE attribute with content
| yes
|
| Summary
| Image button must/should have alt content
| yes
|
| Purpose
|
- A label associated with a form control insures that information about the form control is spoken by screen readers when it receives focus
| yes
|
| Rule ID
| CONTROL_2
| yes
|
| NLS Rule ID
| Form Control 2
| yes
|
| Techniques
|
- The preferered technique for labeling for controls is using the LABEL element and referencing the ID attribute value of the form control element
- Use the LABEL element to encapsulate the form control element
- In special cases, use ARIA-LABELLEDBY attributes to reference the id(s) of the elements on the page that describe the purpose of the form control element
- In special cases, use ARIA-LABEL attributes to provide a explicit text description of the purpose of the form control element
| yes
|
| Manual Checks
| none
| yes
|
| Scope
| Element
| yes
|
| WCAG 2.0 Primary
| 3.3.2
| yes
|
| WCAG 2.0 Related
|
| yes
|
| Language Dependency
| empty string
| yes
|
| Rule Category
| Form Control
| yes
|
| Target Resources
|
| yes
|
| Target Resources Description
| input elements of type image
| yes
|
| Resource Properties
|
| yes
|
Form Control 2: Rule Result Messages
| Property
| Value(s)
| Up To Date
|
| All Pass: Singular
| INPUT[TYPE="IMAGE"] form control has ALT attribute with content
| yes
|
| All Pass: Plural
| %N_P INPUT[TYPE="IMAGE"] form controls have ALT attribute with content
| yes
|
| Manual Check: Singular
| empty string
| yes
|
| Manual Check: Plural
| empty string
| yes
|
| Some Fail
| %N_F out of %N_T INPUT[TYPE="IMAGE"] form controls do NOT have an ALT attribute with content
| yes
|
| All Fail: Singular
| INPUT[TYPE="IMAGE"] form control does NOT have an ALT attribute with content
| yes
|
| All Fail: Plural
| All %N_F INPUT[TYPE="IMAGE"] form controls do NOT have an ALT attribute with content
| yes
|
| Corrective Action: Singular
| add ALT attribute and/or content to INPUT[TYPE="IMAGE"] form control missing a ALT attribute with content
| yes
|
| Corrective Action: Plural
| add ALT attribute and/or content to %N_F INPUT[TYPE="IMAGE"] form controls missing a ALT attribute with content
| yes
|
| Not Applicable
| No INPUT[TYPE="IMAGE"] form controls on this page
| yes
|
Form Control 2: Node Result Messages
| Property
| Value(s)
| Up To Date
|
| Pass 1
| Image button has label
| yes
|
| Pass 2
| empty string
| yes
|
| Pass 3
| empty string
| yes
|
| Manual Check 1
| empty string
| yes
|
| Manual Check 2
| empty string
| yes
|
| Manual Check 3
| empty string
| yes
|
| Corrective Action 1
| Add ALT attribute with text content
| yes
|
| Corrective Action 2
| Add text content to the ALT attribute
| yes
|
| Corrective Action 3
| empty string
| yes
|
| Hidden (i.e. thru css)
| Image button is hidden from asssistive technologies.
| yes
|
| Presentation (i.e. role=presentation)
| empty string
| yes
|
| Other
| empty string
| yes
|
Form Control 3: Radio button must/should use FIELDSET/LEGEND
| Property
| Value(s)
| Up To Date
|
| Definition
| Every input type radio must/should be contained in a FIELDSET and LEGEND elements to provide grouping information for radio button groups
| yes
|
| Summary
| Radio button must/should use FIELDSET/LEGEND
| yes
|
| Purpose
|
- Radio buttons need a common grouping label to provide a context for each radio button option
| yes
|
| Rule ID
| CONTROL_3
| yes
|
| NLS Rule ID
| Form Control 3
| yes
|
| Techniques
|
- FIELDSET/LEGEND element combination is the preferred technique to provide a grouping label for radio buttons
- ARIA-LABELLEDBY attributes can provide a grouping label with references to the grouping text content and the radio button option text content
- ARIA-LABEL attributes can provide a grouping label that includes both the grouping and radio button option text content
| yes
|
| Manual Checks
| none
| yes
|
| Scope
| Element
| yes
|
| WCAG 2.0 Primary
| 3.3.2
| yes
|
| WCAG 2.0 Related
|
| yes
|
| Language Dependency
| empty string
| yes
|
| Rule Category
| Form Control
| yes
|
| Target Resources
|
| yes
|
| Target Resources Description
| input elements of type radio
| yes
|
| Resource Properties
|
| yes
|
Form Control 3: Rule Result Messages
| Property
| Value(s)
| Up To Date
|
| All Pass: Singular
| INPUT[TYPE="RADIO"] form control is contained in a FILEDSET/LEGEND labeling container
| yes
|
| All Pass: Plural
| %N_P INPUT[TYPE="RADIO"] form controls are contained in FILEDSET/LEGEND labeling container
| yes
|
| Manual Check: Singular
| empty string
| yes
|
| Manual Check: Plural
| empty string
| yes
|
| Some Fail
| %N_F out of %N_T INPUT[TYPE="RADIO"]form controls are NOT contained in FILEDSET/LEGEND labeling container
| yes
|
| All Fail: Singular
| INPUT[TYPE="RADIO"] form control is NOT a contained in a FILEDSET/LEGEND labeling container
| yes
|
| All Fail: Plural
| All %N_F INPUT[TYPE="RADIO"] form controls are NOT a contained in FILEDSET/LEGEND labeling containers
| yes
|
| Corrective Action: Singular
| move the INPUT[TYPE="RADIO"] form control to an existing FILEDSET/LEGEND labeling container or create a new FILEDSET/LEGEND labeling container for the control
| yes
|
| Corrective Action: Plural
| move the %N_F INPUT[TYPE="RADIO"] form controls to an existing FILEDSET/LEGEND labeling container or add new FILEDSET/LEGEND labeling containers for the %N_F controls
| yes
|
| Not Applicable
| No INPUT[TYPE="RADIO"] form controls on this page
| yes
|
Form Control 3: Node Result Messages
| Property
| Value(s)
| Up To Date
|
| Pass 1
| Radio button uses FIELDSET and LEGEND elements, and the LEGEND element has text content
| yes
|
| Pass 2
| empty string
| yes
|
| Pass 3
| empty string
| yes
|
| Manual Check 1
| Radio button uses aria-labelledby, verify the label text content includes group information
| yes
|
| Manual Check 2
| Radio button uses aria-label, verify the label text content includes group information
| yes
|
| Manual Check 3
| empty string
| yes
|
| Corrective Action 1
| Add a LEGEND element to with text content to the FIELDSET element to provide grouping label information for the radio buttons.
| yes
|
| Corrective Action 2
| Add a FIELDSET and LEGEND elements to provide grouping label information for the radio buttons.
| yes
|
| Corrective Action 3
| empty string
| yes
|
| Hidden (i.e. thru css)
| Radio button is hidden from asssistive technologies.
| yes
|
| Presentation (i.e. role=presentation)
| empty string
| yes
|
| Other
| empty string
| yes
|
Form Control 4: buttons must/should have content
| Property
| Value(s)
| Up To Date
|
| Definition
| BUTTON elements must/should have text content
| yes
|
| Summary
| BUTTONs must/should have content
| yes
|
| Purpose
|
- The text content of a BUTTON element is used as a label to insure that the purpose of the button is spoken by screen readers when the button receives focus
| yes
|
| Rule ID
| CONTROL_4
| yes
|
| NLS Rule ID
| Form Control 4
| yes
|
| Techniques
|
- The text content of the BUTTON element and the ALT attribute content of images inside the button is used as the text content
| yes
|
| Manual Checks
| none
| yes
|
| Scope
| Element
| yes
|
| WCAG 2.0 Primary
| 3.3.2
| yes
|
| WCAG 2.0 Related
|
| yes
|
| Language Dependency
| empty string
| yes
|
| Rule Category
| Form Control
| yes
|
| Target Resources
|
| yes
|
| Target Resources Description
| BUTTON elements
| yes
|
| Resource Properties
|
| yes
|
Form Control 4: Rule Result Messages
| Property
| Value(s)
| Up To Date
|
| All Pass: Singular
| BUTTON element has text content
| yes
|
| All Pass: Plural
| %N_P BUTTON elements have text content
| yes
|
| Manual Check: Singular
| empty string
| yes
|
| Manual Check: Plural
| empty string
| yes
|
| Some Fail
| %N_F out of %N_T BUTTON elements do NOT have text content
| yes
|
| All Fail: Singular
| BUTTON element does NOT have text content
| yes
|
| All Fail: Plural
| All %N_F BUTTON elements do NOT have text content
| yes
|
| Corrective Action: Singular
| add text content to BUTTON element that describe the purpose of the button
| yes
|
| Corrective Action: Plural
| add text content to %N_F BUTTON elements that describe the purpose of the buttons
| yes
|
| Not Applicable
| No BUTTON elements on this page
| yes
|
Form Control 4: Node Result Messages
| Property
| Value(s)
| Up To Date
|
| Pass 1
| BUTTON element has text content
| yes
|
| Pass 2
| empty string
| yes
|
| Pass 3
| empty string
| yes
|
| Manual Check 1
| empty string
| yes
|
| Manual Check 2
| empty string
| yes
|
| Manual Check 3
| empty string
| yes
|
| Corrective Action 1
| Add text content to BUTTON element
| yes
|
| Corrective Action 2
| empty string
| yes
|
| Corrective Action 3
| empty string
| yes
|
| Hidden (i.e. thru css)
| BUTTON element is hidden from asssistive technologies.
| yes
|
| Presentation (i.e. role=presentation)
| empty string
| yes
|
| Other
| empty string
| yes
|
Form Control 5: id must/should be unique
| Property
| Value(s)
| Up To Date
|
| Definition
| ID attributes must/should have unique values on the web page
| yes
|
| Summary
| ID must/should be unique
| yes
|
| Purpose
|
- ID attribute values can be used as references for LABEL elements, if ID attribute values are not unique it can result incorrect labeling of form controls
| yes
|
| Rule ID
| CONTROL_5
| yes
|
| NLS Rule ID
| Form Control 5
| yes
|
| Techniques
|
- If a form control defines an ID attribute, make sure the valeu is unique
| yes
|
| Manual Checks
| none
| yes
|
| Scope
| Element
| yes
|
| WCAG 2.0 Primary
| 4.1.1
| yes
|
| WCAG 2.0 Related
|
| yes
|
| Language Dependency
| empty string
| yes
|
| Rule Category
| Form Control
| yes
|
| Target Resources
|
- input[type="checkbox"]
- input[type="radio"]
- input[type="text"]
- input[type="password"]
- input[type="file"]
- select
- textarea
| yes
|
| Target Resources Description
| Form control elements with ID attributes
| yes
|
| Resource Properties
|
| yes
|
Form Control 5: Rule Result Messages
| Property
| Value(s)
| Up To Date
|
| All Pass: Singular
| empty string
| yes
|
| All Pass: Plural
| The %N_P elements with an ID attribute have unique id values on page
| yes
|
| Manual Check: Singular
| empty string
| yes
|
| Manual Check: Plural
| empty string
| yes
|
| Some Fail
| %N_F out of %N_T elements with an ID attribute do NOT have unique id values on page
| yes
|
| All Fail: Singular
| empty string
| yes
|
| All Fail: Plural
| All %N_F element with an ID attribute do NOT have a unique id values on page
| yes
|
| Corrective Action: Singular
| empty string
| yes
|
| Corrective Action: Plural
| update elements with ID attributes so the id values are all unique
| yes
|
| Not Applicable
| No elements or only one element with an ID attribute on this page
| yes
|
Form Control 5: Node Result Messages
| Property
| Value(s)
| Up To Date
|
| Pass 1
| '%1' ID attribute value is unique
| yes
|
| Pass 2
| empty string
| yes
|
| Pass 3
| empty string
| yes
|
| Manual Check 1
| empty string
| yes
|
| Manual Check 2
| empty string
| yes
|
| Manual Check 3
| empty string
| yes
|
| Corrective Action 1
| Update elements that share the '%1' ID value to have unique ID values
| yes
|
| Corrective Action 2
| empty string
| yes
|
| Corrective Action 3
| empty string
| yes
|
| Hidden (i.e. thru css)
| %1 control is hidden from assistive technologies.
| yes
|
| Presentation (i.e. role=presentation)
| empty string
| yes
|
| Other
| empty string
| yes
|
Form Control 6: label must/should reference control
| Property
| Value(s)
| Up To Date
|
| Definition
| LABEL element using the FOR attribute must/should reference a form control on the page
| yes
|
| Summary
| LABEL must/should reference control
| yes
|
| Purpose
|
- LABEL elements only are useful for accessibility when they reference or encapsulate form controls
| yes
|
| Rule ID
| CONTROL_6
| yes
|
| NLS Rule ID
| Form Control 6
| yes
|
| Techniques
|
- LABEL elements using the FOR attribute need to reference a form control with the corresponding ID attribute value
| yes
|
| Manual Checks
| none
| yes
|
| Scope
| Element
| yes
|
| WCAG 2.0 Primary
| 3.3.2
| yes
|
| WCAG 2.0 Related
|
| yes
|
| Language Dependency
| empty string
| yes
|
| Rule Category
| Form Control
| yes
|
| Target Resources
|
| yes
|
| Target Resources Description
| LABEL elements
| yes
|
| Resource Properties
|
| yes
|
Form Control 6: Rule Result Messages
| Property
| Value(s)
| Up To Date
|
| All Pass: Singular
| LABEL element uses FOR attribute to label a form control
| yes
|
| All Pass: Plural
| %N_P LABEL elements use the FOR attribute to label form controls
| yes
|
| Manual Check: Singular
| empty string
| yes
|
| Manual Check: Plural
| empty string
| yes
|
| Some Fail
| %N_F out of %N_T LABEL elements do NOT use the FOR attribute to label form controls
| yes
|
| All Fail: Singular
| LABEL element does NOT use FOR attribute to label a form control
| yes
|
| All Fail: Plural
| All %N_F LABEL elements do NOT use FOR attribute to label a form control
| yes
|
| Corrective Action: Singular
| change the LABEL element to use the FOR attribute to label its form control
| yes
|
| Corrective Action: Plural
| change the %N_F LABEL elements to use the FOR attribute to label their form control
| yes
|
| Not Applicable
| No LABEL elements on this page
| yes
|
Form Control 6: Node Result Messages
| Property
| Value(s)
| Up To Date
|
| Pass 1
| empty string
| yes
|
| Pass 2
| empty string
| yes
|
| Pass 3
| empty string
| yes
|
| Manual Check 1
| empty string
| yes
|
| Manual Check 2
| empty string
| yes
|
| Manual Check 3
| empty string
| yes
|
| Corrective Action 1
| Change the LABEL element FOR attribute to reference '%1' to reference a form control
| yes
|
| Corrective Action 2
| empty string
| yes
|
| Corrective Action 3
| empty string
| yes
|
| Hidden (i.e. thru css)
| empty string
| yes
|
| Presentation (i.e. role=presentation)
| empty string
| yes
|
| Other
| empty string
| yes
|
Form Control 7: label must/should have content
| Property
| Value(s)
| Up To Date
|
| Definition
| LABEL element or legend element must/should contain text content
| yes
|
| Summary
| LABEL must/should have content
| yes
|
| Purpose
|
- For LABEL and LEGEND elements only are useful for accessibility when they contain content
| yes
|
| Rule ID
| CONTROL_7
| yes
|
| NLS Rule ID
| Form Control 7
| yes
|
| Techniques
|
- Add text content to LABEL and LEGEND elements that help describe the purpose of the form control
| yes
|
| Manual Checks
| none
| yes
|
| Scope
| Element
| yes
|
| WCAG 2.0 Primary
| 3.3.2
| yes
|
| WCAG 2.0 Related
|
| yes
|
| Language Dependency
| empty string
| yes
|
| Rule Category
| Form Control
| yes
|
| Target Resources
|
| yes
|
| Target Resources Description
| LABEL and LEGEND elements
| yes
|
| Resource Properties
|
| yes
|
Form Control 7: Rule Result Messages
| Property
| Value(s)
| Up To Date
|
| All Pass: Singular
| LABEL or LEGEND element has text content
| yes
|
| All Pass: Plural
| %N_P LABEL or LEGEND elements have text content
| yes
|
| Manual Check: Singular
| empty string
| yes
|
| Manual Check: Plural
| empty string
| yes
|
| Some Fail
| %N_F out of %N_T LABEL or LEGEND elements do NOT have text content
| yes
|
| All Fail: Singular
| LABEL or LEGEND element does NOT have text content
| yes
|
| All Fail: Plural
| All %N_F LABEL or LEGEND elements do NOT have text content
| yes
|
| Corrective Action: Singular
| add content to the LABEL or LEGEND element the describes the purpose of a form control or groupings of form controls
| yes
|
| Corrective Action: Plural
| add content to the %N_F LABEL or LEGEND elements to describes the purpose of each form control or groupings of form controls
| yes
|
| Not Applicable
| No LABEL or LEGEND elements on this page
| yes
|
Form Control 7: Node Result Messages
| Property
| Value(s)
| Up To Date
|
| Pass 1
| %1 has text content
| yes
|
| Pass 2
| empty string
| yes
|
| Pass 3
| empty string
| yes
|
| Manual Check 1
| empty string
| yes
|
| Manual Check 2
| empty string
| yes
|
| Manual Check 3
| empty string
| yes
|
| Corrective Action 1
| Add text content to the %1 element
| yes
|
| Corrective Action 2
| empty string
| yes
|
| Corrective Action 3
| empty string
| yes
|
| Hidden (i.e. thru css)
| %1 control is hidden from asssistive technologies, so %2 content is ignored
| yes
|
| Presentation (i.e. role=presentation)
| empty string
| yes
|
| Other
| empty string
| yes
|
Form Control 8: fieldset must/should have one legend
| Property
| Value(s)
| Up To Date
|
| Definition
| FIELDSET element must/should contain exactly one legend element
| yes
|
| Summary
| FIELDSET must/should have one legend
| yes
|
| Purpose
|
- Multiple legend elements contained in the same fieldset may result in the improper calucation of labels for assistive technologies.
| yes
|
| Rule ID
| CONTROL_8
| yes
|
| NLS Rule ID
| Form Control 8
| yes
|
| Techniques
|
- FIELDSET element should have one and only one LEGEND elements to help describe the purpose of the form controls contained in the FIELDSET element
| yes
|
| Manual Checks
| none
| yes
|
| Scope
| Element
| yes
|
| WCAG 2.0 Primary
| 3.3.2
| yes
|
| WCAG 2.0 Related
|
| yes
|
| Language Dependency
| empty string
| yes
|
| Rule Category
| Form Control
| yes
|
| Target Resources
|
| yes
|
| Target Resources Description
| FIELDSET and LEGEND elements
| yes
|
| Resource Properties
|
| yes
|
Form Control 8: Rule Result Messages
| Property
| Value(s)
| Up To Date
|
| All Pass: Singular
| FIELDSET element has only one LEGEND element
| yes
|
| All Pass: Plural
| %N_P FIELDSET elements have only one LEGEND element
| yes
|
| Manual Check: Singular
| empty string
| yes
|
| Manual Check: Plural
| empty string
| yes
|
| Some Fail
| %N_F out of %N_T FIELDSET elements have more than one LEGEND element or no LEGEND element
| yes
|
| All Fail: Singular
| FIELDSET element has more than one LEGEND element or no LEGEND element
| yes
|
| All Fail: Plural
| All %N_F FIELDSET elements have more than one LEGEND element or no LEGEND element
| yes
|
| Corrective Action: Singular
| update FIELDSET element to contain only one LEGEND element
| yes
|
| Corrective Action: Plural
| update %N_F FIELDSET elements to contain only one LEGEND element
| yes
|
| Not Applicable
| No FIELDSET elements on this page
| yes
|
Form Control 8: Node Result Messages
| Property
| Value(s)
| Up To Date
|
| Pass 1
| FIELDSET has one LEGEND element
| yes
|
| Pass 2
| empty string
| yes
|
| Pass 3
| empty string
| yes
|
| Manual Check 1
| empty string
| yes
|
| Manual Check 2
| empty string
| yes
|
| Manual Check 3
| empty string
| yes
|
| Corrective Action 1
| Add LEGEND element
| yes
|
| Corrective Action 2
| Remove %1 LEGEND elements
| yes
|
| Corrective Action 3
| empty string
| yes
|
| Hidden (i.e. thru css)
| FIELDSET element is hidden from asssistive technologies.
| yes
|
| Presentation (i.e. role=presentation)
| empty string
| yes
|
| Other
| empty string
| yes
|
Form Control 9: title may not be good label
| Property
| Value(s)
| Up To Date
|
| Definition
| TITLE attribute may not be good a label for form control
| yes
|
| Summary
| TITLE may not be good label
| yes
|
| Purpose
|
- When the TITLE attribute is used for tooltips it is often uses more words than needed to label a form control for users of assistive technologies
- use ARIA-LABEL to provide a shorter label to users of assistive technologies if the TITLE attribute content is determined to not be an optimal label
| yes
|
| Rule ID
| CONTROL_9
| yes
|
| NLS Rule ID
| Form Control 9
| yes
|
| Techniques
|
- The preferered technique for labeling for controls is using the LABEL element and referencing the ID attribute value of the form control element
- Use the LABEL element to encapsulate the form control element
- In special cases, use ARIA-LABELLEDBY attributes to reference the id(s) of the elements on the page that describe the purpose of the form control element
- In special cases, use ARIA-LABEL attributes to provide a explicit text description of the purpose of the form control element
| yes
|
| Manual Checks
| none
| yes
|
| Scope
| Element
| yes
|
| WCAG 2.0 Primary
| 3.3.2
| yes
|
| WCAG 2.0 Related
|
| yes
|
| Language Dependency
| empty string
| yes
|
| Rule Category
| Form Control
| yes
|
| Target Resources
|
| yes
|
| Target Resources Description
| TEXTAREA, SELECT and INPUT elements
| yes
|
| Resource Properties
|
| yes
|
Form Control 9: Rule Result Messages
| Property
| Value(s)
| Up To Date
|
| All Pass: Singular
| Form control does not use TITLE attribute as label
| yes
|
| All Pass: Plural
| All %N_P form controls do not use TITLE attribute as label
| yes
|
| Manual Check: Singular
| empty string
| yes
|
| Manual Check: Plural
| empty string
| yes
|
| Some Fail
| empty string
| yes
|
| All Fail: Singular
| empty string
| yes
|
| All Fail: Plural
| empty string
| yes
|
| Corrective Action: Singular
| empty string
| yes
|
| Corrective Action: Plural
| empty string
| yes
|
| Not Applicable
| No form controls on this page
| yes
|
Form Control 9: Node Result Messages
| Property
| Value(s)
| Up To Date
|
| Pass 1
| TITLE is not used as label
| yes
|
| Pass 2
| empty string
| yes
|
| Pass 3
| empty string
| yes
|
| Manual Check 1
| Verify LABEL element or ARIA technique to label %1 form control
| yes
|
| Manual Check 2
| empty string
| yes
|
| Manual Check 3
| empty string
| yes
|
| Corrective Action 1
| empty string
| yes
|
| Corrective Action 2
| empty string
| yes
|
| Corrective Action 3
| empty string
| yes
|
| Hidden (i.e. thru css)
| %1 control is hidden from asssistive technologies.
| yes
|
| Presentation (i.e. role=presentation)
| empty string
| yes
|
| Other
| empty string
| yes
|
Form Control 10: Labels must/should be unique
| Property
| Value(s)
| Up To Date
|
| Definition
| Labels must/should be unique for every textarea, select and input element of type text, password, radio, and checkbox on a page
| yes
|
| Summary
| Labels must/should be unique
| yes
|
| Purpose
|
- Labels that are unique make it possible for people to understand the different purposes of form controls on the same page
| yes
|
| Rule ID
| CONTROL_10
| yes
|
| NLS Rule ID
| Form Control 10
| yes
|
| Techniques
|
- The preferred technique for labeling for controls is using the LABEL element and referencing the ID attribute value of the form control element
- Use the LABEL element to encapsulate the form control element
- In special cases, use ARIA-LABELLEDBY attribute to reference the id(s) of the elements on the page that describe the purpose of the form control element
- In special cases, use ARIA-LABEL attribute to provide a explicit text description of the purpose of the form control element
| yes
|
| Manual Checks
| none
| yes
|
| Scope
| Element
| yes
|
| WCAG 2.0 Primary
| 2.4.6
| yes
|
| WCAG 2.0 Related
|
| yes
|
| Language Dependency
| empty string
| yes
|
| Rule Category
| Form Control
| yes
|
| Target Resources
|
- input[type="checkbox"]
- input[type="radio"]
- input[type="text"]
- input[type="password"]
- input[type="file"]
- select
- textarea
| yes
|
| Target Resources Description
| TEXTAREA, SELECT and INPUT elements of type TEXT, PASSWORD, CHECKBOX, RADIO and FILE
| yes
|
| Resource Properties
|
- computed_label
- fieldset_element
- computed_label_source
- name_attribute
| yes
|
Form Control 10: Rule Result Messages
| Property
| Value(s)
| Up To Date
|
| All Pass: Singular
| empty string
| yes
|
| All Pass: Plural
| %N_P form controls have unique labels
| yes
|
| Manual Check: Singular
| empty string
| yes
|
| Manual Check: Plural
| empty string
| yes
|
| Some Fail
| %N_F out of %N_T form controls do NOT have unique labels
| yes
|
| All Fail: Singular
| empty string
| yes
|
| All Fail: Plural
| All %N_F form controls do NOT have a unique labels
| yes
|
| Corrective Action: Singular
| empty string
| yes
|
| Corrective Action: Plural
| change the labeling of %N_F form controls to uniquely identify the purpose of each form control on the page
| yes
|
| Not Applicable
| No form controls or only one form control on this page
| yes
|
Form Control 10: Node Result Messages
| Property
| Value(s)
| Up To Date
|
| Pass 1
| Label is unique
| yes
|
| Pass 2
| empty string
| yes
|
| Pass 3
| empty string
| yes
|
| Manual Check 1
| empty string
| yes
|
| Manual Check 2
| empty string
| yes
|
| Manual Check 3
| empty string
| yes
|
| Corrective Action 1
| Add label to %1 control
| yes
|
| Corrective Action 2
| Change the LABEL element content, use FIELDSET/LEGEND elements or ARIA technique to make label text content unique on the page
| yes
|
| Corrective Action 3
| empty string
| yes
|
| Hidden (i.e. thru css)
| %1 control is hidden from asssistive technologies.
| yes
|
| Presentation (i.e. role=presentation)
| empty string
| yes
|
| Other
| empty string
| yes
|
Form Control 11: submit and reset buttons must/should be unique
| Property
| Value(s)
| Up To Date
|
| Definition
| If there is more than one form on a page, INPUT element of type SUBMIT and RESET must/should have unique labels using the value attribute
| yes
|
| Summary
| SUBMIT and RESET buttons must/should be unique
| yes
|
| Purpose
|
- Labels that are unique make it possible for people to understand the different purposes of form controls on the same page
- SUBMIT and RESET form controls have default labels and if there is more than one form on a page the user may not understand which form they are submitting
| yes
|
| Rule ID
| CONTROL_11
| yes
|
| NLS Rule ID
| Form Control 11
| yes
|
| Techniques
|
- The preferred technique for changing the default label for SUBMIT and RESET controls is the VALUE attribute
- In special cases, use ARIA-LABELLEDBY attribute to reference the id(s) of the elements on the page that describe the purpose of the form control element
- In special cases, use ARIA-LABEL attribute to provide a explicit text description of the purpose of the form control element
| yes
|
| Manual Checks
| none
| yes
|
| Scope
| Element
| yes
|
| WCAG 2.0 Primary
| 2.4.6
| yes
|
| WCAG 2.0 Related
|
| yes
|
| Language Dependency
| empty string
| yes
|
| Rule Category
| Form Control
| yes
|
| Target Resources
|
- input[type="submit"]
- input[type="reset"]
| yes
|
| Target Resources Description
| SUBMIT and RESET buttons
| yes
|
| Resource Properties
|
| yes
|
Form Control 11: Rule Result Messages
| Property
| Value(s)
| Up To Date
|
| All Pass: Singular
| empty string
| yes
|
| All Pass: Plural
| %N_P SUBMIT or RESET buttons have unique labels
| yes
|
| Manual Check: Singular
| empty string
| yes
|
| Manual Check: Plural
| empty string
| yes
|
| Some Fail
| %N_F out of %N_T SUBMIT or RESET buttons do NOT have unique labels
| yes
|
| All Fail: Singular
| empty string
| yes
|
| All Fail: Plural
| All %N_F SUBMIT or RESET buttons do NOT have a unique labels
| yes
|
| Corrective Action: Singular
| empty string
| yes
|
| Corrective Action: Plural
| change the labeling of %N_F SUBMIT or RESET buttons to uniquely identify the purpose of each SUBMIT or RESET buttons on the page
| yes
|
| Not Applicable
| No forms or only one form on this page
| yes
|
Form Control 11: Node Result Messages
| Property
| Value(s)
| Up To Date
|
| Pass 1
| Label is unique
| yes
|
| Pass 2
| empty string
| yes
|
| Pass 3
| empty string
| yes
|
| Manual Check 1
| empty string
| yes
|
| Manual Check 2
| empty string
| yes
|
| Manual Check 3
| empty string
| yes
|
| Corrective Action 1
| Add label to %1 control
| yes
|
| Corrective Action 2
| Change the VALUE attribute content, use FIELDSET/LEGEND elements or ARIA technique to make SUBMIT and RESET labels unique on the page
| yes
|
| Corrective Action 3
| empty string
| yes
|
| Hidden (i.e. thru css)
| %1 control is hidden from asssistive technologies.
| yes
|
| Presentation (i.e. role=presentation)
| empty string
| yes
|
| Other
| empty string
| yes
|
Form Control 12: Labels must/should be descriptive
| Property
| Value(s)
| Up To Date
|
| Definition
| Labels must/should be must describe the purpose of every button, textarea, select and input element of type text, password, radio, and checkbox on a page
| yes
|
| Summary
| Labels must/should be descriptive
| yes
|
| Purpose
|
- Labels that are unique make it possible for people to understand the different purposes of form controls on the same page
| yes
|
| Rule ID
| CONTROL_12
| yes
|
| NLS Rule ID
| Form Control 12
| yes
|
| Techniques
|
- The preferred technique for labeling for controls is using the LABEL element and referencing the ID attribute value of the form control element
- Use the LABEL element to encapsulate the form control element
- In special cases, use ARIA-LABELLEDBY attribute to reference the id(s) of the elements on the page that describe the purpose of the form control element
- In special cases, use ARIA-LABEL attribute to provide a explicit text description of the purpose of the form control element
| yes
|
| Manual Checks
| none
| yes
|
| Scope
| Element
| yes
|
| WCAG 2.0 Primary
| 2.4.6
| yes
|
| WCAG 2.0 Related
|
| yes
|
| Language Dependency
| empty string
| yes
|
| Rule Category
| Form Control
| yes
|
| Target Resources
|
- button
- input[type="checkbox"]
- input[type="radio"]
- input[type="text"]
- input[type="password"]
- input[type="file"]
- input[type="submit"]
- input[type="reset"]
- select
- textarea
| yes
|
| Target Resources Description
| TEXTAREA, SELECT and INPUT elements of type TEXT, PASSWORD, CHECKBOX, RADIO and FILE
| yes
|
| Resource Properties
|
| yes
|
Form Control 12: Rule Result Messages
| Property
| Value(s)
| Up To Date
|
| All Pass: Singular
| empty string
| yes
|
| All Pass: Plural
| empty string
| yes
|
| Manual Check: Singular
| form control requires a manual check to verify it describes the purpose of the form control
| yes
|
| Manual Check: Plural
| %N_MC form controls require a manual check to verify they uniquely describe the purpose of each form control
| yes
|
| Some Fail
| %N_F out of %N_T form controls do NOT have labels
| yes
|
| All Fail: Singular
| form control does NOT have a label
| yes
|
| All Fail: Plural
| %N_F form controls do NOT have labels
| yes
|
| Corrective Action: Singular
| add label to the form control that describes the from controls purpose
| yes
|
| Corrective Action: Plural
| add labels to the %N_F form controls that uniquely describe purpose of each from control
| yes
|
| Not Applicable
| No form controls on this page
| yes
|
Form Control 12: Node Result Messages
| Property
| Value(s)
| Up To Date
|
| Pass 1
| empty string
| yes
|
| Pass 2
| empty string
| yes
|
| Pass 3
| empty string
| yes
|
| Manual Check 1
| Verify the label describes the purpose and input required for %1 form control
| yes
|
| Manual Check 2
| empty string
| yes
|
| Manual Check 3
| empty string
| yes
|
| Corrective Action 1
| Add a LABEL element, use FIELDSET/LEGEND elements or ARIA lechnique to provide a label for %1 form control
| yes
|
| Corrective Action 2
| empty string
| yes
|
| Corrective Action 3
| empty string
| yes
|
| Hidden (i.e. thru css)
| %1 control is hidden from asssistive technologies.
| yes
|
| Presentation (i.e. role=presentation)
| empty string
| yes
|
| Other
| empty string
| yes
|
new rule nls id : new rule summary
| Property
| Value(s)
| Up To Date
|
| Definition
| definition
| NO
|
| Summary
| summary
| NO
|
| Purpose
|
- purpose 1
- purpose 2
- purpose 3
- purpose 4
| NO
|
| Rule ID
| rule id
| NO
|
| NLS Rule ID
| rule nls id
| NO
|
| Techniques
|
- technique 1
- technique 1 url
- technique 2
- technique 2 url
- technique 3
- technique 3 url
- technique 4
- technique 4 url
| NO
|
| Manual Checks
|
- manual check 1
- manual 1 url
- manual check 2
- manual 2 url
- manual check 3
- manual 3 url
- manual check 4
- manual 4 url
| NO
|
| Scope
| Element or Page
| NO
|
| WCAG 2.0 Primary
| X.X.X
| NO
|
| WCAG 2.0 Related
|
| NO
|
| Language Dependency
| empty string
| NO
|
| Rule Category
| Form Control
| NO
|
| Target Resources
|
| NO
|
| Target Resources Description
| target resource nls description
| NO
|
| Resource Properties
|
| NO
|
new rule nls id : Rule Result Messages
| Property
| Value(s)
| Up To Date
|
| All Pass: Singular
| empty string
| NO
|
| All Pass: Plural
| empty string
| NO
|
| Manual Check: Singular
| empty string
| NO
|
| Manual Check: Plural
| empty string
| NO
|
| Some Fail
| empty string
| NO
|
| All Fail: Singular
| empty string
| NO
|
| All Fail: Plural
| empty string
| NO
|
| Corrective Action: Singular
| empty string
| NO
|
| Corrective Action: Plural
| empty string
| NO
|
| Not Applicable
| empty string
| NO
|
new rule nls id : Node Result Messages
| Property
| Value(s)
| Up To Date
|
| Pass 1
| empty string
| NO
|
| Pass 2
| empty string
| NO
|
| Pass 3
| empty string
| NO
|
| Manual Check 1
| empty string
| NO
|
| Manual Check 2
| empty string
| NO
|
| Manual Check 3
| empty string
| NO
|
| Corrective Action 1
| empty string
| NO
|
| Corrective Action 2
| empty string
| NO
|
| Corrective Action 3
| empty string
| NO
|
| Hidden (i.e. thru css)
| empty string
| NO
|
| Presentation (i.e. role=presentation)
| empty string
| NO
|
| Other
| empty string
| NO
|
