Common found WCAG 2.0 issues
A database of WCAG issues found in our audits.
Important information
- Our soon to be awesome site is new and still under construction. Please open an issue on our Github project if you see anything that needs to be fixed or if you have any recommendations.
Different views:
- Full list
- Grouped Success Criterion
Issues:
- <object> elements must have alternate text
Related Success Criterion: 1.1.1 Non-text Content - Elements containing <code>role="img"</code> have an alternative text
Related Success Criterion: 1.1.1 Non-text Content - Image buttons must have alternate text
Related Success Criterion: 1.1.1 Non-text Content - Images must have alternate text
Related Success Criterion: 1.1.1 Non-text Content - SVG images and graphics require accessible text
Related Success Criterion: 1.1.1 Non-text Content - Using CSS to include images that convey important information
Related Success Criterion: 1.1.1 Non-text Content - Not marking up decorative images in HTML in a way that allows assistive technology to ignore them
Related Success Criterion: 1.1.1 Non-text Content - Providing a text alternative that is not null (e.g., alt=spacer" or alt="image") for images that should be ignored by assistive technology"
Related Success Criterion: 1.1.1 Non-text Content - Omitting the alt attribute or text alternative on img elements, area elements, and input elements of type "image"
Related Success Criterion: 1.1.1 Non-text Content - Using text look-alikes to represent text without providing a text alternative
Related Success Criterion: 1.1.1 Non-text Content - Using ASCII art without providing a text alternative
Related Success Criterion: 1.1.1 Non-text Content - Using text alternatives that are not alternatives (e.g., filenames or placeholder text)
Related Success Criterion: 1.1.1 Non-text Content; 1.2.1 Audio-onle and Video-only (Prerecorded) - Providing long descriptions for non-text content that does not serve the same purpose or does not present the same information
Related Success Criterion: 1.1.1 Non-text Content; 1.2.1 Audio-onle and Video-only (Prerecorded) - Having a text alternative that does not include information that is conveyed by color differences in the image
Related Success Criterion: 1.1.1 Non-text Content; 1.4.1 Use of Color - Active <area> elements must have alternate text
Related Success Criterion: 1.1.1 Non-text Content; 2.4.4 Link Purpose (In Context); 4.1.2 Name, Role, Value - Not updating text alternatives when changes to non-text content occur
Related Success Criterion: 1.1.1 Non-text Content; 4.1.2 Name, Role, Value - Captions omitting some dialogue or important sound effects
Related Success Criterion: 1.2.2 Captions (Prerecorded) - Providing synchronized media without captions when the synchronized media presents more information than is presented on the page
Related Success Criterion: 1.2.2 Captions (Prerecorded) - Not labeling a synchronized media alternative to text as an alternative
Related Success Criterion: 1.2.2 Captions (Prerecorded); 1.2.8 Media Alternative (Prerecorded) - <dl> elements must only directly contain properly-ordered <dt> and <dd> groups, <script>, or <template> elements
Related Success Criterion: 1.3.1 Info and Relationships - <dt> and <dd> elements must be contained by a <dl>
Related Success Criterion: 1.3.1 Info and Relationships - <li> elements must be contained in a <ul> or <ol>
Related Success Criterion: 1.3.1 Info and Relationships - <ul> and <ol> must only directly contain <li>, <script> or <template> elements
Related Success Criterion: 1.3.1 Info and Relationships - All <th> elements and elements with role="columnheader" or role="rowheader" must have data cells they describe
Related Success Criterion: 1.3.1 Info and Relationships - All cells in a <table> element that use the headers attribute must only refer to other cells of that same <table>
Related Success Criterion: 1.3.1 Info and Relationships - All non-empty <td> elements in tables larger than 3 by 3 must have an associated table header
Related Success Criterion: 1.3.1 Info and Relationships - Bold, italic text and font-size are not used to style <p> elements as a heading
Related Success Criterion: 1.3.1 Info and Relationships - Certain ARIA roles must be contained by particular parent elements
Related Success Criterion: 1.3.1 Info and Relationships - Certain ARIA roles must contain particular children
Related Success Criterion: 1.3.1 Info and Relationships - Data or header cells should not be used to give caption to a data table
Related Success Criterion: 1.3.1 Info and Relationships - Using changes in text presentation to convey information without using the appropriate markup or text
Related Success Criterion: 1.3.1 Info and Relationships - Using structural markup in a way that does not represent relationships in the content
Related Success Criterion: 1.3.1 Info and Relationships - Using th elements, layout tables
Related Success Criterion: 1.3.1 Info and Relationships - Inserting non-decorative content by using :before and :after pseudo-elements and the 'content' property in CSS
Related Success Criterion: 1.3.1 Info and Relationships - Incorrectly associating table headers and content via the headers and id attributes
Related Success Criterion: 1.3.1 Info and Relationships - Not correctly marking up table headers
Related Success Criterion: 1.3.1 Info and Relationships - The use of role presentation on content which conveys semantic information
Related Success Criterion: 1.3.1 Info and Relationships - Using white space characters to create multiple columns in plain text content
Related Success Criterion: 1.3.1 Info and Relationships; 1.3.2 Meaningful Sequence - Using white space characters to format tables in plain text content
Related Success Criterion: 1.3.1 Info and Relationships; 1.3.2 Meaningful Sequence - Improperly emulating links
Related Success Criterion: 1.3.1 Info and Relationships; 2.1.1 Keyboard; 2.1.3 Keyboard (No exceptions); 4.1.2 Name, Role, Value - Form <input> elements must have labels
Related Success Criterion: 1.3.1 Info and Relationships; 4.1.2 Name, Role, Value - Using the pre element to markup tabular information
Related Success Criterion: 1.3.2 Info and Relationships - Changing the meaning of content by positioning information with CSS
Related Success Criterion: 1.3.2 Meaningful Sequence - Using white space characters to control spacing within a word
Related Success Criterion: 1.3.2 Meaningful Sequence - Using an HTML layout table that does not make sense when linearized
Related Success Criterion: 1.3.2 Meaningful Sequence - Identifying content only by its shape or location
Related Success Criterion: 1.3.3 Sensory Characteristics - Using a graphical symbol alone to convey information
Related Success Criterion: 1.3.3 Sensory Characteristics - CSS Media queries are not used to lock display orientation
Related Success Criterion: 1.3.4 Orientation - Locking the orientation to landscape or portrait view
Related Success Criterion: 1.3.4 Orientation - Autocomplete attribute must be used correctly
Related Success Criterion: 1.3.5 Identify Input Purpose - Links must be distinguished from surrounding text in a way that does not rely on color
Related Success Criterion: 1.4.1 Use of Color - Creating links that are not visually evident without color vision
Related Success Criterion: 1.4.1 Use of Color - Identifying required or error fields using color differences only
Related Success Criterion: 1.4.1 Use of Color - Using fixed sized containers and fixed position content (CSS)
Related Success Criterion: 1.4.10 Reflow - Using preformatted text or excluding preformatting text as an exception to no two dimensional scrolling.
Related Success Criterion: 1.4.10 Reflow - Styling element outlines and borders in a way that removes or renders non-visible the visual focus indicator
Related Success Criterion: 1.4.11 Non-text Contrast; 2.4.7 Focus Visible; 2.4.11 Focus Visible (Enhanced) - Inline text spacing must be adjustable with custom stylesheets
Related Success Criterion: 1.4.12 Text Spacing - Not allowing for spacing override.
Related Success Criterion: 1.4.12 Text Spacing - Content shown on hover not being hoverable
Related Success Criterion: 1.4.13 Content on Hover or Focus - Failure to make content dismissable without moving pointer hover or keyboard focus
Related Success Criterion: 1.4.13 Content on Hover or Focus - Failure to meet by content on hover or focus not remaining visible until dismissed or invalid
Related Success Criterion: 1.4.13 Content on Hover or Focus - Audio must have controls that provide users with the ability to stop automatically played audio after three seconds
Related Success Criterion: 1.4.2 Audio Control - Playing a sound longer than 3 seconds where there is no mechanism to turn it off
Related Success Criterion: 1.4.2 Audio Control - Absence of a way to pause or stop an HTML5 media element that autoplays
Related Success Criterion: 1.4.2 Audio Control - Text elements must have sufficient color contrast against the background
Related Success Criterion: 1.4.3 Contrast (Minimum) - Specifying foreground colors without specifying background colors or vice versa
Related Success Criterion: 1.4.3 Contrast (Minimum) - Using background images that do not provide sufficient contrast with foreground text (or images of text)
Related Success Criterion: 1.4.3 Contrast (Minimum); 1.4.6 Contrast (Enhanced) - Zooming and scaling must not be disabled
Related Success Criterion: 1.4.4 Resize text - Resizing visually rendered text up to 200 percent causes the text, image or controls to be clipped, truncated or obscured
Related Success Criterion: 1.4.4 Resize text - Text-based form controls do not resize when visually rendered text is resized up to 200%
Related Success Criterion: 1.4.4 Resize text - Text sized in viewport units
Related Success Criterion: 1.4.4 Resize text - Server-side image maps must not be used
Related Success Criterion: 2.1.1 Keyboard - Using only pointing-device-specific event handlers (including gesture) for a function
Related Success Criterion: 2.1.1 Keyboard - Using script to remove focus when focus is received
Related Success Criterion: 2.1.1 Keyboard; 2.4.7 Focus Visible; 2.4.1 Focus Visibile (Enhanced); 3.2.1 On Focus - Combining multiple content formats in a way that traps users inside one format type
Related Success Criterion: 2.1.2 No Keyboard Trap - A webpage or web app that includes single-key shortcuts not including a control that allows users to turn the shortcuts off or a control that allows users to change the shortcuts to key combinations that include keys that are not upper or lower-case letters, punctuation, number, or symbol characters.
Related Success Criterion: 2.1.4 Character Key Shortcuts - Using server-side techniques to automatically redirect pages after a time-out
Related Success Criterion: 2.2.1 Timing Adjustable - Timed refresh must not exist
Related Success Criterion: 2.2.1 Timing Adjustable; 2.2.4 Interruptions; 3.2.5 Change on Request - Using meta redirect with a time limit
Related Success Criterion: 2.2.1 Timing Adjustable; 2.2.4 Interruptions; 3.2.5 Change on Request - Using meta refresh to reload the page
Related Success Criterion: 2.2.1 Timing Adjustable; 2.2.4 Interruptions; 3.2.5 Change on Request - <blink> elements are deprecated and must not be used
Related Success Criterion: 2.2.2 Pause, Stop, Hide - <marquee> elements are deprecated and must not be used
Related Success Criterion: 2.2.2 Pause, Stop, Hide - Using text-decoration:blink without a mechanism to stop it in less than five seconds
Related Success Criterion: 2.2.2 Pause, Stop, Hide - An object or applet, such as Java or Flash, that has blinking content without a mechanism to pause the content that blinks for more than five seconds
Related Success Criterion: 2.2.2 Pause, Stop, Hide - Including scrolling content where movement is not essential to the activity without also including a mechanism to pause and restart the content
Related Success Criterion: 2.2.2 Pause, Stop, Hide - Using the blink element
Related Success Criterion: 2.2.2 Pause, Stop, Hide - A script that causes a blink effect without a mechanism to stop the blinking at 5 seconds or less
Related Success Criterion: 2.2.2 Pause, Stop, Hide - Page must have means to bypass repeated blocks
Related Success Criterion: 2.4.1 Bypass Blocks - Frames must have title attribute
Related Success Criterion: 2.4.1 Bypass Blocks; 4.1.2 Name, Role, Value - Documents must contain a title element to aid in navigation
Related Success Criterion: 2.4.2 Page Titled - The title of a Web page not identifying the contents
Related Success Criterion: 2.4.2 Page Titled - Using tabindex to create a tab order that does not preserve meaning and operability
Related Success Criterion: 2.4.3 Focus Order - Using dialogs or menus that are not adjacent to their trigger control in the sequential navigation order
Related Success Criterion: 2.4.3 Focus Order - Providing link context only in content that is not related to the link
Related Success Criterion: 2.4.4 Link Purpose (In Context) - Not providing an accessible name for an image which is the only content in a link
Related Success Criterion: 2.4.4 Link Purpose (In Context); 2.4.9 Link Purpose (Link Only); 4.1.2 Name, Role, Value - Links must have discernible text
Related Success Criterion: 2.4.4 Link Purpose (In Context); 4.1.2 Name, Role, Value - Ensure that scrollable region has keyboard access
Related Success Criterion: 2.4.7 Focus Visible - Ensure that links with the same accessible name serve a similar purpose
Related Success Criterion: 2.4.9 Link Purpose (Link Only) - Using a non-specific link such as "click here" or "more" without a mechanism to change the link text to specific text.
Related Success Criterion: 2.4.9 Link Purpose (Link Only) - Functionality can be operated by pointer input but not with single-point activation alone
Related Success Criterion: 2.5.1 Pointer Gestures - Activating a button on initial touch location rather than the final touch location.
Related Success Criterion: 2.5.2 Pointer Cancellation - Label and name from content mismatch
Related Success Criterion: 2.5.3 Label in Name - The accessible name not containing the visible label text
Related Success Criterion: 2.5.3 Label in Name - Accessible name contains the visible label text, but the words of the visible label are not in the same order as they are in the visible label text
Related Success Criterion: 2.5.3 Label in Name - Accessible name contains the visible label text, but one or more other words are interspersed in the label
Related Success Criterion: 2.5.3 Label in Name - Functionality that can only be activated via device motion events (e.g., shaking or tilting)
Related Success Criterion: 2.5.4 Motion Actuation - An inability to disable motion actuation
Related Success Criterion: 2.5.4 Motion Actuation - Disrupting or disabling system level features which allow the user to disable motion actuation
Related Success Criterion: 2.5.4 Motion Actuation - <html> element must have a lang attribute
Related Success Criterion: 3.1.1 Language of Page - <html> element must have a valid value for the lang attribute
Related Success Criterion: 3.1.1 Language of Page - <html> elements with lang and xml:lang must have the same base language
Related Success Criterion: 3.1.1 Language of Page - lang attribute must have a valid value
Related Success Criterion: 3.1.2 Language of Parts - Opening a new window as soon as a new page is loaded
Related Success Criterion: 3.2.1 On Focus; 3.2.5 Change on Request - Automatically submitting a form and given a value
Related Success Criterion: 3.2.2 On Input - Launching a new window without prior warning when the selection of a radio button, check box or select list is changed
Related Success Criterion: 3.2.2 On Input - Presenting navigation links in a different relative order on different pages
Related Success Criterion: 3.2.3 Consistent Navigation - Using two different labels for the same function on different Web pages within a set of Web pages
Related Success Criterion: 3.2.4 Consistent Identification - Form fields do not have duplicate labels
Related Success Criterion: 3.3.2 Labels or Instructions - Visually formatting a set of phone number fields but not including a text label
Related Success Criterion: 3.3.2 Labels or Instructions - ID attribute value must be unique
Related Success Criterion: 4.1.1 Parsing - ID attribute values must be unique
Related Success Criterion: 4.1.1 Parsing - IDs used in ARIA and labels must be unique
Related Success Criterion: 4.1.1 Parsing - Incorrect use of start and end tags or attribute markup
Related Success Criterion: 4.1.1 Parsing - Duplicate values of type ID
Related Success Criterion: 4.1.1 Parsing - ARIA attributes must conform to valid names
Related Success Criterion: 4.1.2 Name, Role, Value - ARIA attributes must conform to valid values
Related Success Criterion: 4.1.2 Name, Role, Value - ARIA input fields have an accessible name
Related Success Criterion: 4.1.2 Name, Role, Value - ARIA roles used must conform to valid values
Related Success Criterion: 4.1.2 Name, Role, Value - ARIA toggle fields have an accessible name
Related Success Criterion: 4.1.2 Name, Role, Value - aria-hidden elements do not contain focusable elements
Related Success Criterion: 4.1.2 Name, Role, Value - aria-hidden="true" must not be present on the document <body>
Related Success Criterion: 4.1.2 Name, Role, Value - Buttons must have discernible text
Related Success Criterion: 4.1.2 Name, Role, Value - Elements must only use allowed ARIA attributes
Related Success Criterion: 4.1.2 Name, Role, Value - Input buttons must have discernible text
Related Success Criterion: 4.1.2 Name, Role, Value - Required ARIA attributes must be provided
Related Success Criterion: 4.1.2 Name, Role, Value - Use aria-roledescription on elements with a semantic role
Related Success Criterion: 4.1.2 Name, Role, Value - Implementing custom controls that do not use an accessibility API for the technology, or do so incompletely
Related Success Criterion: 4.1.2 Name, Role, Value - Using script to make div or span a user interface control in HTML without providing a role for the control
Related Success Criterion: 4.1.2 Name, Role, Value - A user interface control not having a programmatically determined name
Related Success Criterion: 4.1.2 Name, Role, Value - The focus state of a user interface component not being programmatically determinable or no notification of change of focus state available
Related Success Criterion: 4.1.2 Name, Role, Value - Not providing names for each part of a multi-part form field, such as a US telephone number
Related Success Criterion: 4.1.2 Name, Role, Value - Using role="alert" or aria-live="assertive" on content which is not important and time-sensitive
Related Success Criterion: 4.1.3 Status Messages - Using a visibility change event to hide or display a document without switching the document's live regions between active and inactive
Related Success Criterion: 4.1.3 Status Messages - ARIA role must be appropriate for the element
Best Practice - accesskey attribute value must be unique
Best Practice - All page content must be contained by landmarks
Best Practice - Banner landmark must not be contained in another landmark
Best Practice - Complementary landmarks and/or asides are top level
Best Practice - Contentinfo landmark must not be contained in another landmark
Best Practice - Elements in the focus order need a role appropriate for interactive content
Best Practice - Elements should not have tabindex greater than zero
Best Practice - Ensures the document has at most one main landmark
Best Practice - Form <input> elements should have a visible label
Best Practice - Frames must be tested with axe-core
Best Practice - Frames must have a unique title attribute
Best Practice - Heading levels should only increase by one
Best Practice - Headings must not be empty
Best Practice - Hidden content on the page cannot be analyzed
Best Practice - Landmarks must have a unique role or role/label/title (i.e. accessible name) combination
Best Practice - Main landmark must not be contained in another landmark
Best Practice - Page must contain a level-one heading
Best Practice - Page must have one main landmark
Best Practice - Page must not have more than one banner landmark
Best Practice - Page must not have more than one contentinfo landmark
Best Practice - Scope attribute should be used correctly on tables
Best Practice - Text of buttons and links should not be repeated in the image alternative
Best Practice - The <caption> element should not contain the same text as the summary attribute
Best Practice - The skip-link target should exist and be focusable
Best Practice - Users should be able to zoom and scale the text up to 500%
Best Practice
- Date modified: