WCAG 2.0 Principle 4 Robust Rules

From MemberWiki

Jump to: navigation, search

Rules Home | Principle 1 Pervceivable | Principle 2 Operable | Principle 3 Understandable | Principle 4 Robust

Contents

Page is Deprecated

go new WCAG 2.0 mapping page

WCAG Guideline 4.1 Compatibility with Assistive Technologies: Maximize compatibility with current and future user agents, including assistive technologies.

Requirement 4.1.1 Parsing Content

In content implemented using markup languages, elements have complete start and end tags, elements are nested according to their specifications, elements do not contain duplicate attributes, and any IDs are unique, except where the specifications allow these features. (Level A)

Note: Start and end tags that are missing a critical character in their formation, such as a closing angle bracket or a mismatched attribute value quotation mark are not complete.

HTML 4 Markup

ID Implemented Priority ARIA Transitional Ruleset ARIA Strict Ruleset IITAA 2.0 Ruleset Rule Description
HTML_1 No P1 Recommendation Violation Violation HTML 1: Do not use the FONT element to style text

WCAG Sufficient Techniques:

HTML_2 No P1 Recommendation Violation Violation HTML 2: Do not use the B element to style text

WCAG Sufficient Techniques:

HTML_3 No P1 Recommendation Violation Violation HTML 3: Do not use the I element to style text

WCAG Sufficient Techniques:

HTML_4 No P1 Recommendation Violation Violation HTML 4: Do not use the U element to style text

WCAG Sufficient Techniques:


Requirement 4.1.2 Name, Role, Value

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. (Level A)

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.

User Interface Event Handlers: Keyboard

  • onKeyDown: A keyboard key is pressed
  • onKeyPress: A keyboard key is pressed or held down
  • onKeyUp: A keyboard key is released

User Interface Event Handlers: Pointer

  • onClick: Mouse clicks an object
  • onDblClick: Mouse double-clicks an object
  • onMouseDown: A mouse button is pressed
  • onMouseMove: The mouse is moved
  • onMouseOut: The mouse is moved off an element
  • onMouseOver: The mouse is moved over an element
  • onMouseUp: A mouse button is released

User Interface Event Handlers: Other

  • onBlur: An element loses focus
  • onChange: The content of a field changes
  • onFocus: An element gets focus
  • onSelect: Text is selected

Rules for Requirement 4.1.2 Name, Role, Value

ID Implemented ARIA Transitional Ruleset ARIA Strict Ruleset Rule Properties
WIDGET_1 No Required Required

DEFINITION: Each widget must have an accessible name

SUMMARY: Widgets must have name

PRIMARY REQUIREMENT: 4.1.2

RELATED REQUIREMENTS: 1.3.1, 2.4.6, 3.3.2

SCOPE: Element

CORRECTIVE ACTION: Add accessible name to widget

TARGET RESOURCES

TARGET RESOURCE DESCRIPTION

  • Elements with role attributes that are defined as widget roles

RESOURCE PROPERTIES

  • accessible_name
  • aria_describedby
  • computed_label_source

LANGUAGE DEPENDENCY

  • none

PURPOSE

  • Widgets with accessible names enable people using assistive technologies to identify the purpose of each widget

TECHNIQUES

  1. Descendent text content of the widget
  2. aria-labelledby attribute and a list of IDREFs
  3. aria-label attribute
  4. title attribute (not recommended, use aria-label instead)

INFORMATIONAL LINKS:

WCAG Techniques

Other Resources

WIDGET_2 No Required Required DEFINITION: The values of defined ARIA properties and states for widgets must be valid

note: Includes checking for valid ids for IDREFS content

SUMMARY: ARIA property and state values must be valid

PRIMARY REQUIREMENT: 4.1.2

RELATED REQUIREMENTS: 4.1.1

SCOPE: Element

CORRECTIVE ACTION: Set property or state to valid value

TARGET RESOURCES

TARGET RESOURCE DESCRIPTION

  • Widget elements with ARIA property and state attributes

RESOURCE PROPERTIES

  • aria-XXXX attributes

LANGUAGE DEPENDENCY

  • none

PURPOSE

  • Invalid property and state values will cause misinformation to presented to screen reader users

TECHNIQUES

  1. Use ARIA specifications to determine property and state values, use only values defined in the specification

INFORMATIONAL LINKS:

WCAG Techniques

  • none

Other Resources


WIDGET_4 No Required Required WIDGET 4: ARIA ID references must be valid IDRefs

ACTION: Update the IDRefs to point to valid IDRefs on the page WCAG Sufficient Techniques:

  • none
WIDGET_5 No Required Required WIDGET 5: Required ARIA property or state is missing

ACTION: Add required ARIA property or state WCAG Sufficient Techniques:

  • none
WIDGET_6 No Recommendation Violation WIDGET 6: ARIA property or state cannot be used with this role

ACTION: Removed ARIA property or state WCAG Sufficient Techniques:

  • none
WIDGET_7 No Recommendation Violation WIDGET 7: ARIA required child role is missing

ACTION: add required child element WCAG Sufficient Techniques:

  • none
WIDGET_8 No Recommendation Violation WIDGET 8: ARIA role cannot be a child of this role

ACTION: remove child element, or change parent role WCAG Sufficient Techniques:

  • none
Retrieved from "/member/wiki/WCAG_2.0_Principle_4_Robust_Rules"
Personal tools