IBM AccessibilityWCAG 2.1 (A, AA)WCAG 2.0 (A, AA)

1.1.1 Non-text Content [A]

All non-text content that is presented to the user has a text alternative that serves the equivalent purpose.
WCAG20_Applet_HasAlt: <applet> elements must provide an 'alt' attribute and an alternative description  Violation — An <applet> element does not have an 'alt' attribute that provides a short text alternative Violation — The 'alt' attribute value for an <applet> element duplicates the 'code' attribute Violation — An <applet> element provides alternative text, but does not provide inner content WCAG20_Img_HasAlt: Images must have an 'alt' attribute with a short text alternative if they convey meaning, or 'alt="" if decorative  Violation — Image 'alt' attribute value consists only of whitespace Violation — Image does not have an 'alt' attribute short text alternative Violation — Image does not have an 'alt' attribute and 'title' attribute value consists only of whitespace WCAG20_Img_LinkTextNotRedundant: The text alternative for an image within a link should not repeat the link text or adjacent link text  Violation — Link text is repeated in an image 'alt' value within the same link Violation — Link text of previous link is repeated in image 'alt' value of a link Violation — Image 'alt' value within a link is repeated in link text of the link after WCAG20_Input_ExplicitLabel: Each form control must have an associated label  Violation — Form control element <{0}> has no associated label Violation — Form control with "{0}" role has no associated label WCAG20_Area_HasAlt: <area> elements in an image map must have a text alternative  Violation — <area> element in an image map has no text alternative HAAC_Figure_label: A <figure> element must have an associated label  Violation — The <figure> element does not have an associated label WCAG20_Img_PresentationImgHasNonNullAlt: Image designated as decorative must have 'alt=""  Violation — Image designated as decorative has non-null 'alt' attribute WCAG20_Img_TitleEmptyWhenAltNull: When the image 'alt' attribute is empty, the 'title' attribute must also be empty  Violation — The image 'alt' attribute is empty, but the 'title' attribute is not empty HAAC_Img_UsemapAlt: An image map and each <area> element in an image map must have text alternative(s)  Violation — Rule Passed WCAG20_Input_ExplicitLabelImage: The <input> element of type "image" should have a text alternative  Violation — The <input> element of type "image" has no text alternative WCAG20_Object_HasText: <object> elements must have a text alternative for the content rendered by the object  Violation — An <object> element does not have a text alternative RPT_Img_UsemapValid: Server-side image map hot-spots must have duplicate text links  Needs review — Server-side image map hot-spots do not have duplicate text links RPT_Img_AltCommonMisuse: 'alt' attribute value must be a good inline replacement for the image  Needs review — Verify that the file name serves as a good inline replacement for the image RPT_Img_LongDescription2: The 'longdesc' attribute must reference HTML content  Needs review — Verify that the file designated by the 'longdesc' attribute contains valid HTML content (file extension not recognized) RPT_Media_AudioVideoAltFilename: Audio or video on the page must have a short text alternative that describes the media content  Needs review — Filename used as label for embedded audio or video RPT_Style_BackgroundImage: Images included by using CSS alone must not convey important information  Needs review — Verify the CSS background image does not convey important information WCAG20_Text_Emoticons: Emoticons must have a short text alternative that describes their purpose  Needs review — Verify that emoticons have a text alternative RPT_Pre_ASCIIArt: ASCII art must have a text alternative  Needs review — Verify that ASCII art has a text alternative RPT_Style_Trigger2: Windows high contrast mode must be supported when using CSS to include, position or alter non-decorative content  Needs review — Confirm Windows high contrast mode is supported when using CSS to include, position or alter non-decorative content WCAG20_Embed_HasNoEmbed: <embed> elements should be immediately followed by a non-embedded element  Recommendation — Verify that the <embed> element is immediately followed by a non-embedded element Valerie_Noembed_HasContent: <noembed> elements should contain descriptive text  Recommendation — Add descriptive text to the <noembed> element RPT_Embed_HasAlt: Provide alternative content for <embed> elements  Recommendation — Verify that the <embed> element has alternative content RPT_Media_AltBrief: Alternative text in 'alt' attribute should be brief (<150 characters)  Recommendation — Text alternative is more than 150 characters HAAC_Canvas: The <canvas> element may not be accessible  Recommendation — Verify accessibility of the <canvas> element HAAC_BackgroundImg_HasTextOrTitle: Background images that convey important information must have a text alternative that describes the image  Recommendation — Verify important background image information has a text alternative in system high contrast mode

1.2.1 Audio-only and Video-only (Prerecorded) [A]

For prerecorded audio-only or video-only media, an alternative provides equivalent information.
HAAC_Video_HasNoTrack: A <video> element must have a text alternative for any meaningful audio content  Needs review — Verify that captions are available for any meaningful audio or provide a caption track for the <video> element RPT_Media_AudioTrigger: Audio information should also be available in text form  Recommendation — Provide transcripts for audio files

1.2.2 Captions (Prerecorded) [A]

Captions are provided for all prerecorded audio content in synchronized media.
HAAC_Video_HasNoTrack: A <video> element must have a text alternative for any meaningful audio content  Needs review — Verify that captions are available for any meaningful audio or provide a caption track for the <video> element

1.2.3 Audio Description or Media Alternative (Prerecorded) [A]

An alternative for time-based media or audio description of the prerecorded video content is provided for synchronized media.
RPT_Media_VideoReferenceTrigger: Pre-recorded media should have an audio track that describes visual information  Recommendation — Verify availability of a user-selectable audio track with description of visual content

1.2.4 Captions (Live) [AA]

Captions are provided for all live audio content in synchronized media.
HAAC_Video_HasNoTrack: A <video> element must have a text alternative for any meaningful audio content  Needs review — Verify that captions are available for any meaningful audio or provide a caption track for the <video> element RPT_Media_VideoObjectTrigger: Live media (streaming video with audio) should have captions for audio content  Recommendation — Verify captions are provided for live media (streaming video with audio)

1.2.5 Audio Description (Prerecorded) [AA]

Audio description is provided for all prerecorded video content in synchronized media.
RPT_Media_VideoReferenceTrigger: Pre-recorded media should have an audio track that describes visual information  Recommendation — Verify availability of a user-selectable audio track with description of visual content

1.3.1 Info and Relationships [A]

Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text.
WCAG20_Input_RadioChkInFieldSet: Related sets of radio buttons or checkboxes should be programmatically grouped  Violation — {0} input found that has the same name, "{2}" as a {1} input Violation — {0} input is not in the group with another {0} with the name "{1}" Violation — {0} input and others with the name "{1}" are not grouped together Violation — {0} input is in a different group than another {0} with the name "{1}" Needs review — Verify that this ungrouped checkbox input is not related to other checkboxes Needs review — Verify that this un-named, ungrouped checkbox input is not related to other checkboxes table_headers_ref_valid: The 'headers' attribute should refer to a valid cell in the same table  Violation — The 'headers' attribute value "{0}" does not reference a valid 'id' in this document Violation — The 'headers' attribute value "{0}" refers to itself Violation — The 'headers' attribute value "{0}" does not refer to a cell in the same table Violation — The 'headers' attribute value "{0}" does not refer to a cell indicated with <th> or a role of "columnheader" or "rowheader" WCAG20_Fieldset_HasLegend: <fieldset> elements must have a single, non-empty <legend> as a label  Violation — <fieldset> element does not have a <legend> Violation — <fieldset> element has more than one <legend> Violation — <fieldset> element <legend> is empty group_withInputs_hasName: Groups with nested inputs must have unique accessible name  Violation — Group/Fieldset does not have an accessible name Violation — Group/Fieldset "{0}" has a duplicate name to another group WCAG20_Table_Scope_Valid: Value for 'scope' attribute must be "row", "col", "rowgroup", or "colgroup"  Violation — Value provided is invalid for the 'scope' attribute Violation — The 'scope' attribute should only be used on a <th> element aria_hidden_focus_misuse: A focusable element should not be within the subtree of an element with 'aria-hidden' set to "true"  Violation — Element "{0}" should not be focusable within the subtree of an element with an 'aria-hidden' attribute with value 'true' landmark_name_unique: Multiple landmarks should have a unique 'aria-labelledby' or 'aria-label' or be nested in a different parent regions  Violation — Multiple "{0}" landmarks with the same parent region are not distinguished from one another because they have the same "{1}" label RPT_Label_UniqueFor: Form controls should have exactly one label  Violation — Form control has more than one label WCAG20_Label_RefValid: The 'for' attribute must reference a non-empty, unique 'id' attribute of an <input> element  Violation — The value "{0}" of the 'for' attribute is not the 'id' of a valid <input> element WCAG20_Table_CapSummRedundant: The table summary must not duplicate the caption  Violation — The table summary duplicates the caption Valerie_Caption_HasContent: A <caption> element for a <table> element must contain descriptive text  Violation — The <table> element has an empty <caption> element Valerie_Caption_InTable: The <caption> element must be nested inside the associated <table> element  Violation — <caption> element is not nested inside a <table> element RPT_Table_DataHeadingsAria: Data table must identify headers  Violation — Table has no headers identified Valerie_Table_DataCellRelationships: For a complex data table, all <th> and <td> elements must be related via 'header' or 'scope' attributes  Violation — Complex table does not have headers for each cell properly defined with 'header' or 'scope' WCAG20_Table_Structure: Table elements with 'role="presentation" or 'role="none" should not have structural elements or attributes  Violation — The <{0}> element with "presentation" role or "none" role has structural element(s) and/or attribute(s) '{1}' RPT_Blockquote_HasCite: Use <blockquote> only for quotations, not indentation  Needs review — Verify that <blockquote> is used only for quotations, not indentation RPT_Blockquote_WrapsTextQuote: Quotations should be marked with <q> or <blockquote> elements  Needs review — If the following text is a quotation, mark it as a <q> or <blockquote> element: {0} RPT_Headers_FewWords: Heading elements must not be used for presentation  Needs review — Verify that the heading element is a genuine heading RPT_Block_ShouldBeHeading: Heading text must use a heading element  Needs review — Check if this text should be marked up as a heading: {0} RPT_List_UseMarkup: Use proper HTML list elements to create lists  Needs review — Verify whether this is a list that should use HTML list elements RPT_Script_OnclickHTML1: Scripts should not be used to emulate links  Needs review — Possible use of a script to emulate a link WCAG20_Style_BeforeAfter: Do not use CSS '::before' and '::after' pseudo-elements to insert non-decorative content  Needs review — Verify the '::before' and '::after' pseudo-elements do not insert non-decorative content WCAG20_Input_InFieldSet: Groups of logically related input elements should be contained within a <fieldset> element  Recommendation — Use the <fieldset> element to group logically related input elements RPT_List_Misuse: List elements should only be used for lists of related items  Recommendation — List element is missing or improperly structured RPT_Script_OnclickHTML2: Scripts should not be used to emulate links  Recommendation — Verify that 'onclick' events are not used in script to emulate a link WCAG20_Select_HasOptGroup: Groups of related options within a selection list should be grouped with <optgroup>  Recommendation — Group of related options may need <optgroup> RPT_Table_LayoutTrigger: Avoid using tables to format text documents in columns unless the table can be linearized  Recommendation — Verify table is not being used to format text content in columns unless the table can be linearized

1.3.2 Meaningful Sequence [A]

When the sequence in which content is presented affects its meaning, a correct reading sequence can be programmatically determined.
Valerie_Elem_DirValid: 'dir' attribute value must be "ltr", "rtl", or "auto"  Violation — Invalid value used for the 'dir' attribute WCAG20_Text_LetterSpacing: Use CSS 'letter-spacing' to control spacing within a word  Needs review — Verify space characters are not being used to create space between the letters of a word

1.3.3 Sensory Characteristics [A]

Instructions provided for understanding and operating content do not rely solely on sensory characteristics of components such as shape, size, visual location, orientation, or sound.
RPT_Text_SensoryReference: Instructions must be meaningful without shape or location words  Needs review — If the word(s) '{0}' is part of instructions for using page content, check it is still understandable without this location or shape information

1.3.4 Orientation [AA]

Content does not restrict its view and operation to a single display orientation, such as portrait or landscape.

1.3.5 Identify Input Purpose [AA]

The purpose of each input field that collects information about the user can be programmatically determined when the field serves a common purpose.
WCAG21_Input_Autocomplete: The 'autocomplete' attribute's token(s) must be appropriate for the input form field  Violation — The 'autocomplete' attribute's token(s) are not appropriate for the input form field

1.4.1 Use of Color [A]

Color is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element.
RPT_Font_ColorInForm: Combine color and descriptive markup to indicate required form fields  Needs review — Check color is not used as the only visual means to convey which fields are required RPT_Style_ColorSemantics1: Combine color and descriptive markup to convey information  Needs review — Verify color is not used as the only visual means of conveying information

1.4.2 Audio Control [A]

If any audio plays automatically for more than 3 seconds, either a mechanism is available to pause or stop the audio, or a mechanism is available to control audio volume independently from the overall system volume level.
RPT_Embed_AutoStart: Mechanism must be available to pause or stop and control the volume of the audio that plays automatically  Needs review — Verify there is a mechanism to pause or stop and control the volume for the audio that plays automatically

1.4.3 Contrast (Minimum) [AA]

The visual presentation of text and images of text has a contrast ratio of at least 4.5:1, with a 3:1 ratio for large-scale text.
IBMA_Color_Contrast_WCAG2AA: The contrast ratio of text with its background must meet WCAG 2.1 AA requirements  Violation — Text contrast of {0} with its background is less than the WCAG AA minimum requirements for text of size {1}px and weight of {2} Needs review — The foreground text and its background color are both detected as {3}. Verify the text meets the WCAG 2.1 AA requirements for minimum contrast IBMA_Color_Contrast_WCAG2AA_PV: The contrast ratio of text with its background (i.e. background with a color gradient or a background image) must meet WCAG 2.1 AA requirements  Needs review — Verify the contrast ratio of the text against the lightest and the darkest colors of the background meets the WCAG 2.1 AA minimum requirements for text of size {1}px and weight of {2}

1.4.4 Resize Text [AA]

Text can be resized without assistive technology up to 200 percent without loss of content or functionality.
WCAG21_Style_Viewport: Text must scale up to 200% without loss of content or functionality  Needs review — Verify that text sized using viewport units can be resized up to 200% meta_viewport_zoom: The 'meta[name=viewport]' should not prevent the browser zooming the content  Recommendation — Confirm the 'meta[name=viewport]' with "{0}" can be zoomed by user

1.4.5 Images of Text [AA]

If the technologies being used can achieve the visual presentation, text is used to convey information rather than images of text.

1.4.10 Reflow [AA]

Content can reflow without loss of information or functionality, and without requiring scrolling in two dimensions.
meta_viewport_zoom: The 'meta[name=viewport]' should not prevent the browser zooming the content  Recommendation — Confirm the 'meta[name=viewport]' with "{0}" can be zoomed by user

1.4.11 Non-text Contrast [AA]

The parts of graphical objects required to understand the content, and the visual information required to identify UI components and states, have a contrast ratio of at least 3:1 against adjacent colors.

1.4.12 Text Spacing [AA]

No loss of content or functionality occurs when users change letter, word and paragraph spacing, as well as line height.

1.4.13 Content on Hover or Focus [AA]

Where hover or focus actions cause additional content to become visible and hidden, the additional content is dismissable, hoverable and persistent.
style_hover_persistent: The pointer should be able to move over content displayed on hover  Needs review — Confirm the pointer can be positioned over the displayed element, not just the trigger Needs review — Confirm the pointer can be positioned over all the information displayed on hover Needs review — Confirm the margin style attribute has not prevented the pointer from hovering over the displayed element, not just the trigger

2.1.1 Keyboard [A]

All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes.
Rpt_Aria_InvalidTabindexForActivedescendant: Element using 'aria-activedescendant' property must have its 'tabindex' attribute value set to 0 or -1 to be keyboard accessible  Violation — The <{0}> element using 'aria-activedescendant' set to "{1}" does not have its 'tabindex' attribute value set to 0 or -1 Rpt_Aria_MissingFocusableChild: UI component must have at least one focusable child element for keyboard access  Violation — The descendent <{0}> element with "{1}" role has no focusable child element HAAC_Application_Role_Text: Non-decorative static text and image content within an element with "application" role must be accessible  Needs review — Verify that the non-decorative static text and image content within an element with "application" role are accessible Rpt_Aria_MissingKeyboardHandler: Interactive WAI_ARIA UI components must provide keyboard access  Needs review — Verify the <{0}> element with "{1}" role has keyboard access HAAC_Audio_Video_Trigger: Media using <audio> and/or <video> elements must have keyboard accessible controls  Needs review — Verify media using <audio> and/or <video> elements have keyboard accessible controls RPT_Elem_EventMouseAndKey: All interactive content with mouse event handlers must have equivalent keyboard access  Recommendation — Confirm the <{0}> element with mouse event handler(s) '{1}' has a corresponding keyboard handler(s)

2.1.2 No Keyboard Trap [A]

If keyboard focus can be moved to a component 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.
HAAC_Media_DocumentTrigger2: File download mechanisms should be keyboard-operable and preserve page focus location  Recommendation — Verify that the file download mechanism does not cause a keyboard trap

2.1.4 Character Key Shortcuts [A]

If a keyboard shortcut is implemented using only letter, punctuation, number or symbol characters, then the shortcut can be turned off, remapped or activated only on focus.

2.2.1 Timing Adjustable [A]

For each time limit that is set by the content, the user can turn off, adjust, or extend the limit.
WCAG20_Meta_RedirectZero: Page should not automatically refresh without warning or option to turn it off or adjust the time limit  Violation — Check page does not automatically refresh without warning or options RPT_Meta_Refresh: Pages should not refresh automatically  Needs review — Verify page is not being caused to refresh automatically

2.2.2 Pause, Stop, Hide [A]

For moving, blinking, scrolling, or auto-updating information, the user can pause, stop, hide or adjust the information.
WCAG20_Blink_AlwaysTrigger: Content that blinks persistently must not be used  Violation — Content found that blinks persistently RPT_Marquee_Trigger: The <marquee> element is obsolete and should not be used  Violation — Scrolling content found that uses the obsolete <marquee> element RPT_Blink_CSSTrigger1: Do not use the "blink" value of the 'text-decoration' property for longer than five seconds  Needs review — Check the "blink" value of the CSS 'text-decoration' property is not used for more than than five seconds

2.3.1 Three Flashes or Below Threshold [A]

Content does 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.

2.4.1 Bypass Blocks [A]

A mechanism is available to bypass blocks of content that are repeated on multiple Web pages.
Rpt_Aria_RegionLabel_Implicit: Each element with "region" role must have a label that describes its purpose  Violation — Section element with an implicit "region" role is not labeled with an 'aria-label' or 'aria-labelledby' Violation — The element with "region" role is not labeled with an 'aria-label' or 'aria-labelledby' Rpt_Aria_OrphanedContent_Native_Host_Sematics: All content must reside within an element with a landmark role  Violation — Content is not within a landmark element Rpt_Aria_MultipleMainsRequireLabel_Implicit_2: Elements with "main" role must have unique labels  Violation — Multiple elements with "main" role do not have unique labels Rpt_Aria_MultipleBannerLandmarks_Implicit: Each element with "banner" role must have a unique label that describes its purpose  Violation — Multiple elements with "banner" role do not have unique labels Rpt_Aria_OneBannerInSiblingSet_Implicit: There must be only one element with "banner" role on the page  Violation — There is more than one element with "banner" role on the page Rpt_Aria_ComplementaryRequiredLabel_Implicit: An element with "complementary" role must have a label  Violation — The element with "complementary" role does not have a label Rpt_Aria_MultipleComplementaryLandmarks_Implicit: Each element with "complementary" role must have a unique label that describes its purpose  Violation — Multiple elements with "complementary" role do not have unique labels Rpt_Aria_MultipleContentinfoLandmarks_Implicit: Each element with "contentinfo" role must have a unique label that describes its purpose  Violation — Multiple elements with "contentinfo" role do not have unique labels Rpt_Aria_MultipleContentinfoInSiblingSet_Implicit: A page, document or application should only have one element with "contentinfo" role  Violation — Multiple elements with "contentinfo" role found on a page Rpt_Aria_MultipleFormLandmarks_Implicit: Each element with "form" role must have a unique label that describes its purpose  Violation — Multiple elements with "form" role do not have unique labels Rpt_Aria_MultipleNavigationLandmarks_Implicit: Each element with "navigation" role must have a unique label that describes its purpose  Violation — Multiple elements with "navigation" role do not have unique labels Rpt_Aria_MultipleSearchLandmarks: Each element with "search" role must have a unique label that describes its purpose  Violation — Multiple elements with "search" role do not have unique labels Rpt_Aria_MultipleRegionsUniqueLabel_Implicit: Each element with a "region" role must have a unique label  Violation — Multiple elements with "region" role do not have unique labels Rpt_Aria_ApplicationLandmarkLabel: An element with "application" role must have a label that describes its purpose  Violation — Element with "application" role does not have a label Rpt_Aria_MultipleApplicationLandmarks: Each element with "application" role must have a unique label that describes its purpose  Violation — Multiple elements with "application" role do not have unique labels Rpt_Aria_MultipleDocumentRoles: All elements with a "document" role must have unique labels  Violation — Multiple elements with a "document" role do not have unique labels Rpt_Aria_MultipleArticleRoles_Implicit: Each element with "article" role must have a unique label that describes its purpose  Violation — Multiple elements with "article" role do not have unique labels WCAG20_Body_FirstASkips_Native_Host_Sematics: Pages must provide a way to skip directly to the main content  Violation — The page does not provide a way to quickly navigate to the main content (ARIA "main" landmark or a skip link) WCAG20_Frame_HasTitle: Inline frames must have a unique, non-empty 'title' attribute  Violation — Inline frame does not have a 'title' attribute RPT_Html_SkipNav: Provide a way to bypass blocks of content that are repeated on multiple Web pages  Needs review — Verify there is a way to bypass blocks of content that are repeated on multiple Web pages WCAG20_Body_FirstAContainsSkipText_Native_Host_Sematics: The description of a hyperlink used to skip content must communicate where it links to  Needs review — Verify that if this hyperlink skips content, the description communicates where it links to Valerie_Frame_SrcHtml: A <frame> containing non-HTML content must be made accessible  Needs review — Verify <frame> content is accessible Rpt_Aria_MultipleMainsVisibleLabel_Implicit: Each element with "main" role should have a unique visible label that describes its purpose  Recommendation — Multiple elements with "main" role do not have unique visible labels Rpt_Aria_ComplementaryLandmarkLabel_Implicit: Each element with "complementary" role should have a visible label that describes its purpose  Recommendation — The element with "complementary" role does not have a visible label Rpt_Aria_ContentinfoWithNoMain_Implicit: An element with "contentinfo" role is only permitted with an element with "main" role  Recommendation — The element with "contentinfo" role is present without an element with "main" role

2.4.2 Page Titled [A]

Web pages, non-web documents, and software have titles that describe topic or purpose.
WCAG20_Doc_HasTitle: The page should have a title that correctly identifies the subject of the page  Violation — Missing <head> element so there can be no <title> element present Violation — Missing <title> element in <head> element Violation — The <title> element is empty (no innerHTML) RPT_Title_Valid: Page <title> should be a descriptive title, rather than a filename  Needs review — Verify that using the filename as the page <title> value is descriptive

2.4.3 Focus Order [A]

If content can be navigated sequentially and the navigation sequences affect meaning or operation, focusable components receive focus in an order that preserves meaning and operability.
IBMA_Focus_Tabbable: Component must have at least one tabbable element  Needs review — Component with "{0}" role does not have a tabbable element IBMA_Focus_MultiTab: Certain components must have no more than one tabbable element  Needs review — Component with "{0}" role has more than one tabbable element

2.4.4 Link Purpose (In Context) [A]

The purpose of each link can be determined from the link text alone or from the link text together with its programmatically determined link content.
WCAG20_A_HasText: Hyperlinks must have a text description of their purpose  Violation — Hyperlink has no link text, label or image with a text alternative

2.4.5 Multiple Ways [AA]

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.

2.4.6 Headings and Labels [AA]

Headings and labels describe topic or purpose.
RPT_Header_HasContent: Heading elements must provide descriptive text  Violation — Heading element has no descriptive content

2.4.7 Focus Visible [AA]

Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible.
WCAG20_Script_FocusBlurs: Scripting must not remove focus from content that normally receives focus  Needs review — Verify script does not remove focus from content that normally receives focus RPT_Style_HinderFocus1: The keyboard focus indicator must be highly visible when default border or outline is modified by CSS  Needs review — Check the keyboard focus indicator is highly visible when using CSS elements for border or outline

2.5.1 Pointer Gestures [A]

All functionality that uses multipoint or path-based gestures for operation can be operated with a single pointer without a path-based gesture.

2.5.2 Pointer Cancellation [A]

For functionality that can be operated using a single pointer, completion of the function is on the up-event with an ability to abort, undo or reverse the outcome.

2.5.3 Label in Name [A]

For user interface components with labels that include text or images of text, the accessible name contains the text that is presented visually.
WCAG21_Label_Accessible: Accessible name must match or contain the visible label text  Violation — Accessible name does not match or contain the visible label text

2.5.4 Motion Actuation [A]

Functionality that can be operated by motion can also be operated by user interface components, and the motion trigger can be disabled.

3.1.1 Language of Page [A]

The default human language of Web pages, non-Web documents, or software can be programmatically determined.
WCAG20_Html_HasLang: Page must identify the default language of the document with a 'lang' attribute  Violation — Page detected as XHTML 1.0, but has neither 'lang' nor 'xml:lang' attributes Violation — Page detected as XHTML, but does not have an 'xml:lang' attribute Violation — Page detected as HTML, but does not have a 'lang' attribute Violation — Page detected with 'lang' and 'xml:lang' attributes and primary languages do not match: "{0}", "{1}" Violation — Page detected with 'lang' and 'xml:lang' attributes that do not match: "{0}", "{1}" Needs review — Page detected as XHTML 1.0 with only a 'lang' attribute. Confirm that page is only delivered via text/html mime type Needs review — Page detected as XHTML 1.0 with only an 'xml:lang' attribute. Confirm that page is only delivered via xml mime type

3.1.2 Language of Parts [AA]

The human language of each passage or phrase in the content can be programmatically determined.
WCAG20_Elem_Lang_Valid: The language of content must be valid and specified in accordance with BCP 47  Violation — Specified 'lang' attribute does not include a valid primary language Violation — Specified 'lang' attribute does not conform to BCP 47 Violation — Specified 'lang' attribute does not include a valid primary language Violation — Specified 'xml:lang' attribute does not conform to BCP 47

3.2.1 On Focus [A]

When any component receives focus, it does not initiate a change of context.
WCAG20_Script_FocusBlurs: Scripting must not remove focus from content that normally receives focus  Needs review — Verify script does not remove focus from content that normally receives focus WCAG20_Select_NoChangeAction: No changes of context should occur when a selection value receives focus  Needs review — Verify that no change of context or action occurs when selection options in this component receive focus

3.2.2 On Input [A]

Changing the setting of any user interface component does not automatically cause a change of context unless the user has been advised of the behavior before using the component.
WCAG20_Form_HasSubmit: A <form> element should have a submit button or an image button  Needs review — Verify the <form> element has a submit button or an image button WCAG20_Form_TargetAndText: User should be informed in advance when interacting with content causes a change of context  Needs review — Verify that interacting with content will not open pop-up windows or change the active window without informing the user WCAG20_Input_HasOnchange: Verify that any changes of context are explained in advance to the user  Needs review — Verify that any changes of context are explained in advance to the user WCAG20_A_TargetAndText: Users should be warned in advance if their input action will open a new window or otherwise change their context  Recommendation — Inform the user when their input action will open a new window or otherwise change their context RPT_Form_ChangeEmpty: A form should not be submitted automatically without warning the user  Recommendation — Confirm the form does not submit automatically without warning

3.2.3 Consistent Navigation [AA]

Navigational mechanisms that are repeated on multiple Web pages within a set of Web pages occur in the same relative order each time they are repeated, unless a change is initiated by the user.

3.2.4 Consistent Identification [AA]

Components that have the same functionality within a set of Web pages are identified consistently.

3.3.1 Error Identification [A]

If an input error is automatically detected, the item that is in error is identified and the error is described to the user in text.
HAAC_Aria_ErrorMessage: A custom error message must reference a valid 'id' value and when triggered the message must be appropriately exposed  Violation — Custom error message has invalid reference 'id' value Violation — Custom error message is not visible

3.3.2 Labels or Instructions [A]

Labels or instructions are provided when content requires user input.
group_withInputs_hasName: Groups with nested inputs must have unique accessible name  Violation — Group/Fieldset does not have an accessible name Violation — Group/Fieldset "{0}" has a duplicate name to another group WCAG20_Input_LabelBefore: Text inputs and <select> elements must have a label before the input control  Violation — Text input is nested in label such that input precedes the label text Violation — Label text is located after its associated text input or <select> element WCAG20_Input_LabelAfter: Checkboxes and radio buttons must have a label after the input control  Violation — Checkbox or radio button is nested in label, so label is not after the input control Violation — Label text is located before its associated checkbox or radio button element HAAC_Aria_Or_HTML5_Attr: HTML5 attributes must not conflict with the associated ARIA attribute used on an input element  Violation — HTML5 attribute is in conflict with the associated ARIA attribute used on an input element HAAC_Input_Placeholder: HTML5 'placeholder' attribute must not be used as a visible label replacement  Needs review — HTML5 placeholder is the only visible label Needs review — Additional visible label referenced by 'aria-labelledby' is not valid WCAG20_Input_VisibleLabel: An input element must have an associated visible label  Needs review — The input element does not have an associated visible label HAAC_Accesskey_NeedLabel: An HTML element with an assigned 'accesskey' attribute must have an associated label  Recommendation — The HTML element with an assigned 'accesskey' attribute does not have an associated label

3.3.3 Error Suggestion [AA]

If an input error is automatically detected and suggestions for correction are known, then the suggestions are provided to the user, unless it would jeopardize the security or purpose of the content.

3.3.4 Error Prevention (Legal, Financial, Data) [AA]

For content that cause legal commitments or financial transactions for the user to occur, that modify or delete user-controllable data in data storage systems, or that submit user test responses, the user can reverse, correct, or confirm the action.

4.1.1 Parsing [A]

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.
RPT_Elem_UniqueId: Element 'id' attribute values must be unique within a document  Violation — The <{0}> element has the id "{1}" that is empty Violation — The <{0}> element has the id "{1}" that is already in use WCAG20_Elem_UniqueAccessKey: 'accesskey' attribute values on each element must be unique for the page  Violation — 'accesskey' attribute value on the element is not unique element_attribute_deprecated: Avoid use of obsolete features if possible  Recommendation — The <{0}> element is deprecated in HTML 5 Recommendation — The HTML attribute(s) "{0}" is deprecated in HTML 5 Recommendation — The HTML attribute(s) "{0}" is deprecated for the <{1}> element in HTML 5 Recommendation — The ARIA role "{0}" is deprecated in ARIA 1.2 Recommendation — The ARIA attribute(s) "{0}" is deprecated in ARIA 1.2 Recommendation — The ARIA attribute(s) "{0}" is deprecated for the role "{1}"

4.1.2 Name, Role, Value [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.
combobox_popup_reference: The 'aria-controls' (for ARIA 1.2) or the 'aria-owns' (for ARIA 1.0) attribute of the expanded combobox must reference a valid popup 'id' value  Violation — The 'aria-owns' attribute of the expanded combobox is missing Violation — The 'aria-controls' attribute of the expanded combobox is missing Violation — The 'aria-owns' attribute "{0}" of the expanded combobox does not reference a valid popup 'id' value Violation — The 'aria-controls' attribute "{0}" of the expanded combobox does not reference a valid popup 'id' value Violation — The combobox 'aria-expanded' attribute is true, but the combobox popup is not visible Violation — The combobox 'aria-expanded' attribute is false, but the combobox popup is visible combobox_active_descendant: 'aria-activedescendant' must be used to define focus within the combobox popup, except when using a dialog popup  Violation — The element referenced by 'aria-activedescendant' "{0}" does not exist Violation — The 'aria-activedescendant' "{0}" references an element with the roles "{1}", which does not have a valid ARIA role of 'option', 'gridcell', 'row', or 'treeitem' Violation — The 'aria-activedescendant' "{0}" references an element that does not have 'aria-selected' set to true HAAC_ActiveDescendantCheck: The 'aria-activedescendant' property must reference the 'id' of a non-empty, non-hidden active child element  Violation — The 'aria-activedescendant' property is empty Violation — The 'aria-activedescendant' property references a hidden node Violation — Element is not a combobox, and the referenced active-descendant element is not a valid descendant aria_semantics_role: ARIA roles must be valid for the element to which they are assigned  Violation — The ARIA role '{0}' is not valid for the element <{1}> Violation — The ARIA role '{0}' is not valid for the element <{1}> and may be ignored by the browser since the element is focusable combobox_haspopup: The combobox attribute 'aria-haspopup' value must be appropriate for the role of the element referenced by 'aria-controls' (ARIA 1.2) or 'aria-owns' (ARIA 1.0)  Violation — The 'role' value "{0}" of the popup element "{1}" should be one of "listbox", "grid", "tree" or "dialog" Violation — The value of the combobox 'aria-haspopup' attribute "{0}" does not match the 'role' value of the popup element "{1}" combobox_focusable_elements: Tabbable focus for the combobox must be allowed only on the text input, except when using a dialog popup  Violation — The combobox element does not allow DOM focus as required Violation — The popup of the combobox has DOM focus or has 'aria-activedescendant' defined, which is not allowed combobox_autocomplete: A combobox that supports autocompletion behavior must have the 'aria-autocomplete' attribute only on its text input element with a valid value; a value of '"inline"' is not supported  Violation — The combobox has the 'aria-autocomplete' attribute incorrectly set on an element within the popup referenced by "{0}" Violation — The combobox does not support an 'aria-autocomplete' attribute value set to '"inline"' WCAG20_Input_ExplicitLabel: Each form control must have an associated label  Violation — Form control element <{0}> has no associated label Violation — Form control with "{0}" role has no associated label Rpt_Aria_ValidRole: Elements must have a valid 'role' per ARIA specification  Violation — The role '{0}' defined on the element is not valid per ARIA specification Needs review — Some of the roles, '{0}', defined on the element are not valid per ARIA specification aria_hidden_focus_misuse: A focusable element should not be within the subtree of an element with 'aria-hidden' set to "true"  Violation — Element "{0}" should not be focusable within the subtree of an element with an 'aria-hidden' attribute with value 'true' Rpt_Aria_RequiredProperties: When using a ARIA role on an element, the required attributes for that role must be defined  Violation — An element with ARIA role '{0}' does not have the required ARIA attribute(s): '{1}' Rpt_Aria_ValidProperty: ARIA attributes must be valid for the element's role  Violation — The attribute(s) '{0}' referenced by the element <{1}> is not a valid ARIA state or property Rpt_Aria_EmptyPropertyValue: When specifying a required ARIA attribute, the value must not be empty  Violation — The element attribute(s): '{0}' value is empty Rpt_Aria_ValidPropertyValue: ARIA property values must be valid  Violation — The value "{0}" specified for attribute '{1}' on element <{2}> is not valid Rpt_Aria_ValidIdRef: The ARIA property must reference a non-empty unique id of an existing element that is visible  Violation — The 'id' "{0}" specified for the ARIA property '{1}' value is not valid Rpt_Aria_RequiredParent_Native_Host_Sematics: An element with an implicit or explicit role must be contained within a valid element  Violation — The element with role "{0}" is not contained in or owned by an element with one of the following roles: "{1}" Rpt_Aria_EventHandlerMissingRole_Native_Host_Sematics: Elements with event handlers must have a valid ARIA role  Violation — The <{0}> element with '{1}' does not have a valid ARIA role specified aria_semantics_attribute: ARIA attributes must be valid for the element and ARIA role to which they are assigned  Violation — The ARIA attribute '{0}' is not valid for the element <{1}> with ARIA role '{2}' Rpt_Aria_WidgetLabels_Implicit: Interactive component must have a programmatically associated name  Violation — Interactive component with ARIA role '{0}' does not have a programmatically associated name Rpt_Aria_MultipleToolbarUniqueLabel: All toolbar components on a page must have unique labels specified  Violation — Multiple toolbar components do not have unique labels combobox_version: The combobox design pattern must be valid for ARIA 1.2  Violation — The combobox design pattern is detected as ARIA 1.1, which is not allowed by ARIA 1.2 HAAC_List_Group_ListItem: List component with "group" role must limit children to <listitem> elements  Violation — List component with "group" role has children that are not <listitem> elements HAAC_Aria_ImgAlt: An element with "img" role must have a non-empty label  Violation — Element with "img" role has no label or an empty label HAAC_Aria_SvgAlt: An element with a graphics role must have a non-empty label  Violation — Element with "{0}" graphics role has no label or an empty label Valerie_Label_HasContent: A <label> element must have non-empty descriptive text that identifies the purpose of the interactive component  Violation — The <label> element does not have descriptive text that identifies the expected input table_aria_descendants: Table structure elements cannot specify an explicit 'role' within table containers  Violation — An explicit ARIA 'role' is not valid for <{0}> element within a ARIA role '{1}' per the ARIA in HTML specification input_haspopup_invalid: <input> element with 'list' attribute should not also use 'aria-haspopup' attribute  Needs review — <input> element with 'list' attribute also uses 'aria-haspopup' attribute with type="{0}" Needs review — <input> element with 'list' attribute also uses 'aria-haspopup' attribute with missing or invalid input type Rpt_Aria_RequiredChildren_Native_Host_Sematics: An element with a ARIA role must contain required children  Needs review — The element with role "{0}" does not contain or own at least one child element with each of the following roles: "{1}" HAAC_Canvas: The <canvas> element may not be accessible  Recommendation — Verify accessibility of the <canvas> element

4.1.3 Status Messages [AA]

In content implemented using markup languages, status messages can be programmatically determined through role or properties such that they can be presented to the user by assistive technologies without receiving focus.