WCAG 2.0 Principle 2 Operable Rules

From MemberWiki

Jump to: navigation, search

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

Contents

WCAG Guideline 2.1 Keyboard Accessible: Make all functionality available from a keyboard.

Requirement 2.1.1 Keyboard

All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes, except where the underlying function requires input that depends on the path of the user's movement and not just the endpoints. (Level A)

Note 1: This exception relates to the underlying function, not the input technique. For example, if using handwriting to enter text, the input technique (handwriting) requires path-dependent input but the underlying function (text input) does not.

Note 2: This does not forbid and should not discourage providing mouse input or other input methods in addition to keyboard operation.

ID Implemented Priority ARIA Transitional Ruleset ARIA Strict Ruleset IITAA 2.0 Ruleset Rule Description
KEYBOARD_1 No P1 Violation Violation Violation KEYBOARD 1: Any element with a onMouseDown, onMouseUp or onMouseMove event handler, must have a keyboard event on the node or on an ancestor
KEYBOARD_2 No P1 Violation Violation Violation KEYBOARD 2: Any element with an onClick event handler, must be on a focusable element or a child of a focusable element
KEYBOARD_3 No P1 Recommendation Violation Violation KEYBOARD 3: Any onChange event handlers should not be used with the select element

Requirement 2.1.2 No Keyboard Trap

If keyboard focus can be moved to a component of the page using a keyboard interface, then focus can be moved away from that component using only a keyboard interface, and, if it requires more than unmodified arrow or tab keys or other standard exit methods, the user is advised of the method for moving focus away. (Level A)

Note: Since any content that does not meet this success criterion can interfere with a user's ability to use the whole page, all content on the Web page (whether it is used to meet other success criteria or not) must meet this success criterion

ID Implemented Priority ARIA Transitional Ruleset ARIA Strict Ruleset IITAA 2.0 Ruleset Rule Description
none no rule

Requirement 2.1.3 Keyboard (No Exception)

All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes. (Level AAA)

ID Implemented Priority ARIA Transitional Ruleset ARIA Strict Ruleset IITAA 2.0 Ruleset Rule Description
ACCESSKEY_1 No P1 Recommendation Recommendation Recommendation ACCESSKEY 1: Accesskey attribute values should be unique.

WCAG Guideline 2.2 Enough Time: Provide users enough time to read and use content.

Requirement 2.2.1 Timing Adjustable

For each time limit that is set by the content, at least one of the following is true: (Level A)

  • Turn off: The user is allowed to turn off the time limit before encountering it; or
  • Adjust: The user is allowed to adjust the time limit before encountering it over a wide range that is at least ten times the length of the default setting; or
  • Extend: The user is warned before time expires and given at least 20 seconds to extend the time limit with a simple action (for example, "press the space bar"), and the user is allowed to extend the time limit at least ten times; or
  • Real-time Exception: The time limit is a required part of a real-time event (for example, an auction), and no alternative to the time limit is possible; or
  • Essential Exception: The time limit is essential and extending it would invalidate the activity; or
  • 20 Hour Exception: The time limit is longer than 20 hours.

Note: This success criterion helps ensure that users can complete tasks without unexpected changes in content or context that are a result of a time limit. This success criterion should be considered in conjunction with Success Criterion 3.2.1, which puts limits on changes of content or context as a result of user action.

ID Implemented Priority ARIA Transitional Ruleset ARIA Strict Ruleset IITAA 2.0 Ruleset Rule Description
none no rule Rules under development

Requirement 2.2.2 Pause, Stop, Hide

For moving, blinking, scrolling, or auto-updating information, all of the following are true: (Level A)

  • Moving, blinking, scrolling: For any moving, blinking or scrolling information that (1) starts automatically, (2) lasts more than five seconds, and (3) is presented in parallel with other content, there is a mechanism for the user to pause, stop, or hide it unless the movement, blinking, or scrolling is part of an activity where it is essential; and
  • Auto-updating: For any auto-updating information that (1) starts automatically and (2) is presented in parallel with other content, there is a mechanism for the user to pause, stop, or hide it or to control the frequency of the update unless the auto-updating is part of an activity where it is essential.

Note 1: For requirements related to flickering or flashing content, refer to Guideline 2.3.

Note 2: Since any content that does not meet this success criterion can interfere with a user's ability to use the whole page, all content on the Web page (whether it is used to meet other success criteria or not) must meet this success criterion. See Conformance Requirement 5: Non-Interference.

Note 3: Content that is updated periodically by software or that is streamed to the user agent is not required to preserve or present information that is generated or received between the initiation of the pause and resuming presentation, as this may not be technically possible, and in many situations could be misleading to do so.

Note 4: An animation that occurs as part of a preload phase or similar situation can be considered essential if interaction cannot occur during that phase for all users and if not indicating progress could confuse users or cause them to think that content was frozen or broken.

ID Implemented Priority ARIA Transitional Ruleset ARIA Strict Ruleset IITAA 2.0 Ruleset Rule Description
TIME_1 No P1 Recommendation Violation Violation TIME 1: Do not animate text without providing the user to stop and start the animation (in this case the MARQUEE element)

WCAG Sufficient Techniques:

TIME_2 No P1 Recommendation Violation Violation TIME 2: Do not automatically blink text (in this case the BLINK element)

WCAG Sufficient Techniques:

Requirement 2.2.3 No Timing

Timing is not an essential part of the event or activity presented by the content, except for non-interactive synchronized media and real-time events. (Level AAA)

ID Implemented Priority ARIA Transitional Ruleset ARIA Strict Ruleset IITAA 2.0 Ruleset Rule Description
none no rule Rules under development

Requirement 2.2.4 Interruptions

Interruptions can be postponed or suppressed by the user, except interruptions involving an emergency. (Level AAA)

ID Implemented Priority ARIA Transitional Ruleset ARIA Strict Ruleset IITAA 2.0 Ruleset Rule Description
none no rule Rules under development

Requirement 2.2.5 Re-authenticating

When an authenticated session expires, the user can continue the activity without loss of data after re-authenticating. (Level AAA)

ID Implemented Priority ARIA Transitional Ruleset ARIA Strict Ruleset IITAA 2.0 Ruleset Rule Description
none no rule Rules under development

WCAG Guideline 2.3 Seizures: Do not design content in a way that is known to cause seizures.

Requirement 2.3.1 Three Flashes or Below Threshold

Web pages do not contain anything that flashes more than three times in any one second period, or the flash is below the general flash and red flash thresholds. (Level A)

Note: Since any content that does not meet this success criterion can interfere with a user's ability to use the whole page, all content on the Web page (whether it is used to meet other success criteria or not) must meet this success criterion.

ID Implemented Priority ARIA Transitional Ruleset ARIA Strict Ruleset IITAA 2.0 Ruleset Rule Description
none no rule Rules under development

Requirement 2.3.2 Three Flashes

Web pages do not contain anything that flashes more than three times in any one second period. (Level AAA)

ID Implemented Priority ARIA Transitional Ruleset ARIA Strict Ruleset IITAA 2.0 Ruleset Rule Description
none no rule Rules under development

WCAG Guideline 2.4 Navigable: Provide ways to help users navigate, find content, and determine where they are.

Requirement 2.4.1 Bypass Blocks

A mechanism is available to bypass blocks of content that are repeated on multiple Web pages. (Level A)

ID Implemented Priority ARIA Transitional Ruleset ARIA Strict Ruleset IITAA 2.0 Ruleset Rule Description
LANDMARK 1 Yes P1 Recommendation Violation Violation LANDMARK_1: Every page must have at least one container element (e.g. DIV element) with a role attribute set to the value "main".

PURPOSE: Provide a means to navigate to the primary content of the web page by marking the beginning and end of the primary content.

Note:

  1. The container element should contain the "main" or primary content of the web page so assistive technology users can quickly navigate to the main content
  2. Most pages will only have one MAIN landmark, unless the page is composted of content aggregated from multiple sources like portlets

WCAG Sufficient Techniques:

  • none
LANDMARK_2 Yes P2 Recommendation Violation Violation LANDMARK 2: All content must be contained within a container element (e.g. DIV element) with the role attribute set to one of the landmark values (i.e. application, banner, complementary, contentinfo, form, main, navigation, region, search)

PURPOSE: Provide a means to identify the type of content for all sections of a web page and to navigate to each section.


Note:

  1. The landmark for the container should represent the type of content in the contatiner

WCAG Sufficient Techniques:

  • none
TITLE_6 No P1 Recommendation Not Included Violation TITLE 6: Each page should contain at least one H1 element and each H1 element must have content

PURPOSE: Provide a means to navigate to the beginning of primary content of the web page, the H1 should be at the beginning of the primary content.

NOTES:

  1. H1s should be reserved for identifying Main content on the page
  2. Not required in ARIA rule set since main landmarks are used for this purpose

WCAG Sufficient Techniques:

TITLE_7 No P1 Unknown Unknown Unknown TITLE 7: Skip navigation link (Note: MR, HR and TO will provide text)

PURPOSE: Provide a means to compensate for most browsers not providing keyboard access to navigation the structural content of a web page

WCAG Sufficient Techniques:

Requirement 2.4.2 Page Titled

Web pages have titles that describe topic or purpose. (Level A)

ID Implemented Priority Transitional Ruleset ARIA Ruleset IITAA 2.0 Ruleset Rule Description
TITLE_1 No P1 Violation Violation Violation TITLE 1: The page must contain exactly one title element and it must contain content.

PURPOSE: Title element provides important orientation information on the purpose of the page

WCAG Sufficient Techniques:

TITLE_2 No P1 Recommendation Recommendation Violation TITLE 2: If a page contains both MAIN landmarks and H1 elements, each H1 element must be contained within a main landmark and the MAIN landmark should reference the H1 it contains using aria-labelledby

PURPOSE: Provide H1 elements as a redundant way to mark the beginning of the main content and provide speech users with a way to navigate to main content

NOTES:

  1. This is proposing a design practice of reserving H1 elements as a redundant indication of main content in a web page
  2. This does not require every MAIN landmark to have an H1, only that the H1s on a page be used as labels for MAIN Landmarks
  3. It will be considered an error if a MAIN landmark references an H1 element that is NOT one of its descendant elements


WCAG Sufficient Techniques:

  • none
TITLE_X No P1 Recommended Recommended Violation TITLE X: A MAIN landmark must not contain more than one H1 element

PURPOSE: If the main landmark contains more than one H1 element, it will cause speech users confusion over where the start of content begins, use properly nested headings and/or region landmarks (with labels) to provide orientation to sub sections of the main landmark content

WCAG Sufficient Techniques:

  • none
TITLE_3 No P2 Recommendation Recommendation Recommendation TITLE 3: The content of the first H1 element (document order) on the page should be a subset of the words in the content of the TITLE element

PURPOSE: This is a check to make sure the TITLE element and the H1 element on the page provide consistent information

NOTE: 1. She we including first main labels

WCAG Sufficient Techniques:

  • none
TITLE_4_EN No P2 Recommendation Recommendation Recommendation TITLE 4(EN): Title content should be concise (more than one word, but less than 100 characters) (English only)

PURPOSE: The longer the title, the longer it will take for speech users to identify the purpose of the page

WCAG Sufficient Techniques:

  • none
TITLE_5 No P1 Recommendation Recommendation Recommendation TITLE 5: The title element content of the page should be unique within a website

WCAG Sufficient Techniques:

TITLE_6 No P1 Violation Violation Violation TITLE 6: The title must describe topic or purpose of the page

NOTES:

  • This would result in a manual evaluation

WCAG Sufficient Techniques:

Requirement 2.4.3 Focus Order

If a Web page can be navigated sequentially and the navigation sequences affect meaning or operation, focusable components receive focus in an order that preserves meaning and operability. (Level A)

ID Implemented Priority ARIA Transitional Ruleset ARIA Strict Ruleset IITAA 2.0 Ruleset Rule Description
FOCUS_ORDER_1 No P1 Conditional Conditional Conditional FOCUS ORDER 1: If a page contains more than one link, form control, object or widget verify the focus order is meaningful

NOTE:

  • The focus order is highly discretionary

WCAG Sufficient Techniques:

Other references:

Requirement 2.4.4 Link Purpose (In Context)

The purpose of each link can be determined from the link text alone or from the link text together with its programmatically determined link context, except where the purpose of the link would be ambiguous to users in general. (Level A)

ID Implemented Priority ARIA Transitional Ruleset ARIA Strict Ruleset IITAA 2.0 Ruleset Rule Description
LINK_1 Yes P1 Recommendation Recommendation Violation Link 1: The accessible name of a link, including the content referenced using aria-describedby, for links with different HREFs in the same landmark should be unique

NOTES:

  1. If the link text can not be made unique, use ARIA-DESCRIBEDBY to make the accessible name unique

WCAG Sufficient Techniques:

Other Resources:

LINK_2 Yes P3 Informational Informational Informational Link 2: The accessible name of a link, including the content referenced using aria-describedby, for links with same HREF typically have the same accessible name

WCAG Sufficient Techniques:

  • none
LINK_3 Yes P1 Informational Informational Recommendation Link 3: Links should be at least 12 pixels high and 12 pixels wide for selecting and reading

WCAG Sufficient Techniques:

  • none

Requirement 2.4.5 Multiple Ways

More than one way is available to locate a Web page within a set of Web pages except where the Web Page is the result of, or a step in, a process. (Level AA)

ID Implemented Priority ARIA Transitional Ruleset ARIA Strict Ruleset IITAA 2.0 Ruleset Rule Description
LANDMARK_5 No P1 Conditional Conditional Conditional LANDMARK 5: If a web site has multiple web pages and is not part of a pre-ordered sequence of web pages, have at least one navigation landmark section that includes links within the same domain as the current page

NOTE:

  • If navigation to other links in the domain, pass this rule, otherwise just require a manual check

WCAG Sufficient Techniques:

LANDMARK_6 No P1 Conditional Conditional Conditional LANDMARK 6: For any page with multiple sections, have at least one navigation landmark that includes links to same page targets

NOTE:

  • If navigation to internal links, pass this rule, otherwise just require a manual check

WCAG Sufficient Techniques:

LANDMARK_7 No P1 Conditional Conditional Conditional LANDMARK 7: For a web site with multiple web pages and is not part of a pre-ordered sequence of web pages, have at least one search landmark that searches only the pages of the web site

NOTE:

  • Pass if search landmark found, otherwise manual check

WCAG Sufficient Techniques:

Requirement 2.4.6 Headings and Labels

Headings and labels describe topic or purpose. (Level AA)

Heading and Landmarks Rules

ID Implemented Priority ARIA Transitional Ruleset ARIA Strict Ruleset IITAA 2.0 Ruleset Rule Description
HEADING_2T No P2 Recommendation not included not included HEADING 2T: The text content of headings of the same level that share the same parent heading should be unique.

WCAG Sufficient Techniques:

HEADING_2 No P2 not included Recommendation Violation HEADING 2: The text content of headings of the same level that share the same parent heading with in the same landmark role should be unique.

WCAG Sufficient Techniques:

HEADING_3 No P1 Manual Evaluation Manual Evaluation Manual Evaluation HEADING 3: Heading content should describe the section or sub section

WCAG Sufficient Techniques:

LANDMARK_3 Yes P1 Recommendation Violation Violation LANDMARK 3: If there is more than one landmark of the same type on the page, each landmark of the same type must have its own unique label

WCAG Sufficient Techniques:

  • none
LANDMARK_4 Yes P1 Manual Check Manual Check Manual Check LANDMARK 4: If a landmark has a label, the label should describe the content of the landmark

WCAG Sufficient Techniques:

  • none

********* OpenAjax group start here ***********

Control Rules

ID Implemented Priority ARIA Transitional Ruleset ARIA Strict Ruleset IITAA 2.0 Ruleset Rule Description
CONTROL_10 Yes P1 Recommendation Recommendation Violation CONTROL 10: The label must be unique for every textarea, select and input element of type text, password, radio, and checkbox on a page

WCAG Sufficient Techniques:

CONTROL_11 No P1 Recommendation Recommendation Violation CONTROL 11: If there is more than one form on a page, input element of type submit and reset must have unique labels using the value attribute

WCAG Sufficient Techniques:

CONTROL_12A No P1 Manual Check Manual Check Manual Check CONTROL 12: If a html 4 form control is required it must include the aria-required attribute

WCAG Sufficient Techniques:

CONTROL_12B No P1 Manual Check Manual Check Manual Check CONTROL 12: If a html 5 form control is required it must include the required attribute

WCAG Sufficient Techniques:

WIDGET 1 No P1 Manual Check Manual Check Manual Check WIDGET 1: If a widget control is required it must include the aria-required attribute

WCAG Sufficient Techniques:

NOTE: Need to add reference to "Accessible Label" calculation

Requirement 2.4.7 Focus Visible

Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible. (Level AA)

ID Implemented Priority ARIA Transitional Ruleset ARIA Strict Ruleset IITAA 2.0 Ruleset Rule Description
FOCUS_1 No P1 Violation Violation Violation FOCUS 1: If an element is focusable and has onMouseOut and onMouseIn event handlers, it also need to have onFocus and onBlur event handlers.

WCAG Sufficient Techniques:

Requirement 2.4.8 Location

Information about the user's location within a set of Web pages is available. (Level AAA)


ID Implemented Priority ARIA Transitional Ruleset ARIA Strict Ruleset IITAA 2.0 Ruleset Rule Description
LANDMARK 8 No P1 Violation Violation Violation LANDMARK_8: Include a navigation landmark with the label "Breadcrumbs" (English only)

WCAG Sufficient Techniques:

Requirement 2.4.9 Link Purpose (Link Only)

A mechanism is available to allow the purpose of each link to be identified from link text alone, except where the purpose of the link would be ambiguous to users in general. (Level AAA)

ID Implemented Priority ARIA Transitional Ruleset ARIA Strict Ruleset IITAA 2.0 Ruleset Rule Description
LINK_4 Yes P1 Violation Violation Violation Link 4: Links with the same HREF should have the same link text.

WCAG Sufficient Techniques:

LINK_5 Yes P1 Violation Violation Violation Link 5: Links with the different HREFs should have the unique link text.

WCAG Sufficient Techniques:

LINK_6 Yes P1 Violation Violation Violation Link 6: Links that are only images and area elements must have non-empty alt text.

WCAG Sufficient Techniques:

LINK_7 Yes P1 Violation Violation Violation Link 7: Links with images and text content, the alt attribute should be unique to the text content or empty.

WCAG Sufficient Techniques:

Requirement 2.4.10 Section Headings

Section headings are used to organize the content. (Level AAA)

Note 1: "Heading" is used in its general sense and includes titles and other ways to add a heading to different types of content.

Note 2: This success criterion covers sections within writing, not user interface components. User Interface components are covered under

ID Implemented Priority ARIA Transitional Ruleset ARIA Strict Ruleset IITAA 2.0 Ruleset Rule Description
HEADING_4 No P1 Violation Violation Violation HEADING 4: Headings within landmarks must be properly nested, if there are no MAIN landmarks the headings after the last H1 must be properly nested

WCAG Sufficient Techniques:

HEADING_5 No P1 Recommendation Violation Violation HEADING 5: Every navigation and complementary landmark should use an H2 element as its label

WCAG Sufficient Techniques:

  • none
HEADING_7 No P1 Recommendation Recommendation Violation HEADING 7: Heading elements should contain content

WCAG Sufficient Techniques:

  • none
Retrieved from "http://www.openajax.org/member/wiki/WCAG_2.0_Principle_2_Operable_Rules"
Personal tools