Web Content Accessibility Guidelines 2.0 Ruleset

1. Perceivable - Information and user interface components must be presentable to users in ways they can perceive.

1.1 Text Alternatives: Provide text alternatives for any non-text content so that it can be changed into other forms people need, such as large print, braille, speech, symbols or simpler language.

Requirement 1.1.1 Non-text Content (Level A)

ID Status Priority Severity Rule Description
26 Accepted Priority 1 Violation Rule 26: Images must have valid alt text.
27 Accepted Priority 1 Violation Rule 27: Image file name is not valid alt text.
28 Accepted Priority 1 Violation Rule 28: Certain words cannot be used as a part of valid alt text
29 Accepted Priority 1 Recommendation Rule 29: Length of alt text.
30 Accepted Priority 1 Violation Rule 30: Longdesc must have valid URI.
31 Accepted Priority 1 Violation Rule 31: If an image has an alt or title attribute, it should not have a presentation role.
32 Proposed Priority 1 Potential Violation Rule 32: ALT text must describe content or purpose of image

1.2 Time-based Media: Provide alternatives for time-based media.

Requirement 1.2.1 Audio-only and Video-only (Prerecorded) (Level A)

ID Status Priority Severity Rule Description
46 Proposed Priority 1 Potential Violation Rule 46: Prerecorded audio with no video or image tracks needs a text transcript which includes speaker information.
47 Proposed Priority 1 Potential Violation Rule 47: Prerecorded video with no audio track needs text or audio descriptions of the video content.

Requirement 1.2.2 Captions (Prerecorded) (Level A)

ID Status Priority Severity Rule Description
48 Proposed Priority 1 Potential Violation Rule 48: Prerecorded video with audio track needs synchronized captions.

Requirement 1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A)

ID Status Priority Severity Rule Description
49 Proposed Priority 1 Potential Violation Rule 49: Prerecorded video with audio track needs a audio or text description of the video content.

Requirement 1.2.4 Captions (Live) (Level AA)

ID Status Priority Severity Rule Description
50 Proposed Priority 1 Potential Violation Rule 50: Live audio of speech requires realtime captioning of the speakers.

Requirement 1.2.5 Audio Description (Prerecorded) (Level AA)

ID Status Priority Severity Rule Description
51 Proposed Priority 1 Potential Violation Rule 51: Synchronized audio descriptons of video.

Requirement 1.2.6 Sign Language (Prerecorded) (Level AAA)

ID Status Priority Severity Rule Description
52 Proposed Priority 1 Potential Violation Rule 52: Synchronized sign language for audio track.

Requirement 1.2.7 Extended Audio Description (Prerecorded) (Level AAA)

ID Status Priority Severity Rule Description
53 Proposed Priority 1 Potential Violation Rule 53: Extended audio description if audio track does not provided enhough time to fully describe video content.

Requirement 1.2.8 Media Alternative (Prerecorded) (Level AAA)

ID Status Priority Severity Rule Description
54 Proposed Priority 1 Potential Violation Rule 54: Text alternative to audio and video content

Requirement 1.2.9 Audio-only (Live) (Level AAA)

ID Status Priority Severity Rule Description
55 Proposed Priority 1 Potential Violation Rule 55: Provide text alternatives to live audio

1.3 Adaptable: Create content that can be presented in different ways (for example simpler layout) without losing information or structure.

Requirement 1.3.1 Info and Relationships (Level A)

ID Status Priority Severity Rule Description
3 Accepted Priority 1 Violation Rule 3: Data tables must use summary attribute.
4 Accepted Priority 1 Violation Rule 4: Data tables must use th elements
5 Accepted Priority 1 Violation Rule 5: Summary attribute content must be unique.
6 Accepted Priority 1 Violation Rule 6: Complex data tables must have ids on th elements.
7 Accepted Priority 1 Violation Rule 7: For complex data tables table ids must be unique.
8 Accepted Priority 1 Violation Rule 8: Complex data table td elements must have header attributes.
9 Accepted Priority 1 Violation Rule 9: Complex data tables header ids must be on the page.

Requirement 1.3.2 Meaningful Sequence (Level A)

ID Status Priority Severity Rule Description
36 Accepted Priority 1 Potential Violation Rule 36: Do not use nested tables for positioning.
56 Proposed Priority 1 Potential Violation Rule 56: Document reading order makes sense when layout tables and css positioning is disabled.

Requirement 1.3.3 Sensory Characteristics (Level A)

ID Status Priority Severity Rule Description
37 Proposed Priority 1 Potential Violation Rule 37: Document reading order makes sense when layout tables and css positioning is disabled.
72 Accepted Priority 1 Potential Violation Rule 72: Instructions and operation must be accessible and not depend on solely on color, size, location or sound .

1.4 Distinguishable: Make it easier for users to see and hear content including separating foreground from background.

Requirement 1.4.1 Use of Color (Level A)

ID Status Priority Severity Rule Description
64 Proposed Priority 1 Potential Violation Rule 64: Verify that color is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element.

Requirement 1.4.2 Audio Control (Level A)

ID Status Priority Severity Rule Description
57 Accepted Priority 1 Potential Violation Rule 57: Verify audio does not start playing automatically when document is loaded.

Requirement 1.4.3 Contrast (Minimum) (Level AA)

ID Status Priority Severity Rule Description
65 Accepted Priority 1 Violation Rule 65: Color contrast ratio must be > 3 for large text

Requirement 1.4.4 Resize text (Level AA)

ID Status Priority Severity Rule Description
58 Accepted Priority 2 Potential Violation Rule 58: Verify only relative font sizes are used to define font sizes.

Requirement 1.4.5 Images of Text (Level AA)

ID Status Priority Severity Rule Description
33 Accepted Priority 2 Potential Violation Rule 33: Verify that images are not being used only to stylize text.

Requirement 1.4.6 Contrast (Enhanced) (Level AAA)

ID Status Priority Severity Rule Description
66 Accepted Priority 2 Violation Rule 66: Color contrast ratio should be > 4.5

Requirement 1.4.7 Low or No Background Audio (Level AAA)

No rules

Requirement 1.4.8 Visual Presentation (Level AAA)

No rules

Requirement 1.4.9 Images of Text (No Exception) (Level AAA)

No rules

2. Operable - User interface components and navigation must be operable.

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

Requirement 2.1.1 Keyboard (Level A)

ID Status Priority Severity Rule Description
59 Accepted Priority 1 Violation Rule 59: Focusable elements with MouseOver should also have OnFocus event handlers.
60 Accepted Priority 1 Violation Rule 60: Focusable elements with an OnMouseOut should also have OnBlur event handlers.
61 Accepted Priority 1 Violation Rule 61: Every onClick event handler should be on a focusable element.
62 Accepted Priority 2 Violation Rule 62: OnChange event handler should not be used with the select element.
63 Accepted Priority 1 Violation Rule 63: onmousedown, onmouseup and onmousemove event handlers should have keyboard equivalents.
94 Accepted Priority 1 Violation Rule 94: Check that non-form and non-anchor elements with event handlers have valid roles.
95 Accepted Priority 1 Violation Rule 95: Check that elements with mouse event handlers also have key event handlers
96 Accepted Priority 1 Violation Rule 96: Check that enabled elements with ACTIVE-DESCENDANT have valid tab index
97 Accepted Priority 1 Violation Rule 97: Check that elements without 'aria-activedescendant' that have roles requiring a container have focusable children
98 Accepted Priority 1 Violation Rule 98: Check that elements without 'aria-activedescendant' that have roles requiring a container have key event handlers

Requirement 2.1.2 No Keyboard Trap (Level A)

No rules

Requirement 2.1.3 Keyboard (No Exception) (Level AAA)

ID Status Priority Severity Rule Description
1 Accepted Priority 2 Violation Rule 1: Accesskey attribute values should be unique.
2 Accepted Priority 2 Violation Rule 2: Accesskey attribute values should not interfere with IE shortcuts.

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

Requirement 2.2.1 Timing Adjustable (Level A)

No rules

Requirement 2.2.2 Pause, Stop, Hide (Level A)

ID Status Priority Severity Rule Description
68 Accepted Priority 1 Violation Rule 68: The blink and marquee elements must not be used.

Requirement 2.2.3 No Timing (Level AAA)

No rules

Requirement 2.2.4 Interruptions (Level AAA)

No rules

Requirement 2.2.5 Re-authenticating (Level AAA)

No rules

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

No rules

Requirement 2.3.2 Three Flashes (Level AAA)

No rules

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

Requirement 2.4.1 Bypass Blocks (Level A)

ID Status Priority Severity Rule Description
10 Accepted Priority 1 Violation Rule 10: Frame element must have a title attribute.
11 Accepted Priority 1 Violation Rule 11: Title attributes for frames must be unique.
12 Accepted Priority 2 Recommendation Rule 12: Frames should not be hidden or empty.

Requirement 2.4.2 Page Titled (Level A)

ID Status Priority Severity Rule Description
13 Accepted Priority 1 Violation Rule 13: Title element should not be empty.
14 Accepted Priority 1 Recommendation Rule 14: Missing or empty H1 element.
15 Accepted Priority 1 Recommendation Rule 15: H1 element content should not come only from the alt text of an image.
16 Accepted Priority 1 Recommendation Rule 16: H1 should match a subset of the words in the title element.
17 Accepted Priority 1 Recommendation Rule 17: No more than two h1 elements.
24 Accepted Priority 1 Violation Rule 24: Title content should be concise.
25 Accepted Priority 1 Violation Rule 25: Title text must contain more than one word.

Requirement 2.4.3 Focus Order (Level A)

No rules

Requirement 2.4.4 Link Purpose (In Context) (Level A)

ID Status Priority Severity Rule Description
38 Accepted Priority 1 Recommendation Rule 38: Link text should be as least four 4 characters long.
40 Accepted Priority 1 Violation Rule 40: Links that point to different HREFs should have different link text context.
42 Accepted Priority 1 Recommendation Rule 42: Images should be at least 16 pixels by 16 pixels when used as links.
43 Accepted Priority 1 Violation Rule 43: Links with images and text content, the alt attribute should be unique to the text content or empty.
44 Accepted Priority 1 Potential Violation Rule 44: Purpose of link must be determined from context.

Requirement 2.4.5 Multiple Ways (Level AA)

No rules

Requirement 2.4.6 Headings and Labels (Level AA)

ID Status Priority Severity Rule Description
18 Accepted Priority 1 Violation Rule 18: Headings must have text content.
19 Accepted Priority 1 Recommendation Rule 19: Text content for a heading must not come just from image alt text.
20 Accepted Priority 1 Recommendation Rule 20: Heading content should be concise.
21 Accepted Priority 1 Violation Rule 21: Heading elements should be properly nested.
22 Accepted Priority 1 Recommendation Rule 22: The content of the headings of the same level within the same section should be unique.
23 Accepted Priority 1 Potential Violation Rule 23: Heading elements (h1..h6) should be used for structuring information on the page.

Requirement 2.4.7 Focus Visible (Level AA)

No rules

Requirement 2.4.8 Location (Level AAA)

No rules

Requirement 2.4.9 Link Purpose (Link Only) (Level AAA)

ID Status Priority Severity Rule Description
39 Accepted Priority 1 Violation Rule 39: Links with the same HREF should have the same link text.
41 Accepted Priority 1 Violation Rule 41: Links that point to different HREFs should have different link text.
45 Accepted Priority 1 Potential Violation Rule 45: Purpose of link must be determined from link text.

Requirement 2.4.10 Section Headings (Level AAA)

No rules

3. Understandable - Information and the operation of user interface must be understandable.

3.1 Readable: Make text content readable and understandable.

Requirement 3.1.1 Language of Page (Level A)

ID Status Priority Severity Rule Description
34 Accepted Priority 1 Violation Rule 34: Each page must have a lang attribute on its html element.
35 Accepted Priority 1 Violation Rule 35: lang attribute on html element must have a valid two-character language code.

Requirement 3.1.2 Language of Parts (Level AA)

No rules

Requirement 3.1.3 Unusual Words (Level AAA)

No rules

Requirement 3.1.4 Abbreviations (Level AAA)

No rules

Requirement 3.1.5 Reading Level (Level AAA)

No rules

Requirement 3.1.6 Pronunciation (Level AAA)

No rules

3.2 Predictable: Make Web pages appear and operate in predictable ways.

Requirement 3.2.1 On Focus (Level A)

No rules

Requirement 3.2.2 On Input (Level A)

No rules

Requirement 3.2.3 Consistent Navigation (Level AA)

No rules

Requirement 3.2.4 Consistent Identification (Level AA)

No rules

Requirement 3.2.5 Change on Request (Level AAA)

No rules

3.3 Input Assistance: Help users avoid and correct mistakes.

Requirement 3.3.1 Error Identification (Level A)

No rules

Requirement 3.3.2 Labels or Instructions (Level A)

ID Status Priority Severity Rule Description
73 Accepted Priority 1 Violation Rule 73: Each fieldset element should contain a legend element.
74 Accepted Priority 1 Recommendation Rule 74: The label element should not encapsulate select and textarea elements.
75 Accepted Priority 1 Violation Rule 75: Each input element with type=text | password | checkbox | radio | file and each select and textarea element should either be referenced by the for attribute of a label element via its id attribute, or have a title attribute.
76 Accepted Priority 1 Violation Rule 76: Inputs element of type=[image] must have an alt or a title attribute.
77 Accepted Priority 2 Recommendation Rule 77: Input elements where type=[button|submit|reset] must have a value or title attribute.
78 Accepted Priority 1 Violation Rule 78: Each button element must contain content.
79 Accepted Priority 1 Violation Rule 79: Effective labels should be unique.
80 Accepted Priority 1 Violation Rule 80: Labels must have text content.
81 Accepted Priority 1 Violation Rule 81: Legends must have text content.
82 Accepted Priority 1 Recommendation Rule 82: Title attributes used for labeling form controls must have content.
83 Accepted Priority 1 Violation Rule 83: Form controls must have unique ids.

Requirement 3.3.3 Error Suggestion (Level AA)

No rules

Requirement 3.3.4 Error Prevention (Legal, Financial, Data) (Level AA)

No rules

Requirement 3.3.5 Help (Level AAA)

No rules

Requirement 3.3.6 Error Prevention (All) (Level AAA)

No rules

4. Robust - Content must be robust enough that it can be interpreted reliably by a wide variety of user agents, including assistive technologies.

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

Requirement 4.1.1 Parsing Content (Level A)

ID Status Priority Severity Rule Description
67 Accepted Priority 2 Violation Rule 67: Do not use the FONT element to style text
69 Accepted Priority 2 Violation Rule 69: Do not use the B element.
70 Accepted Priority 2 Violation Rule 70: Do not use the I element.
71 Accepted Priority 2 Violation Rule 71: Do not use the U element.
85 Accepted Priority 1 Violation Rule 85: ARIA attributes have valid values
86 Accepted Priority 1 Violation Rule 86: ARIA ID references must be valid IDRefs
87 Accepted Priority 1 Violation Rule 87: ARIA attributes can only be used with certain roles

Requirement 4.1.2 Name, Role, Value (Level A)

ID Status Priority Severity Rule Description
84 Accepted Priority 1 Violation Rule 84: Check aria properties and states for valid roles and properties
88 Accepted Priority 1 Violation Rule 88: Roles must contain their required child roles
89 Accepted Priority 1 Violation Rule 89: Child roles must be contained by the proper parent role
90 Accepted Priority 1 Violation Rule 90: Required properties and states should be defined
91 Accepted Priority 1 Violation Rule 91: Required properties and states must not be empty
92 Accepted Priority 1 Violation Rule 92: Role value must be valid
93 Accepted Priority 1 Violation Rule 93: Check that 'ARIA-' attributes are valid properties and states