Accessibility Checking for Large Sites

Rocket Validator automatically scans your sites for accessibility issues using the axe-core a11y engine, hosted on our own servers and integrated into our web crawler.

Try Rocket Validator Pro

WCAG: Best Practice Landmarks must have a unique role or role/label/title (i.e. accessible name) combination

Landmarks must have a unique role or role/label/title (i.e. accessible name) combination.

landmark-unique is a new best practice rule ensures that landmarks have a unique role or accessible name (i.e. role, label, title) combination.

Learn more about this accessibility rule at Deque University >>

Accessibility Rules checked by Rocket Validator

WCAG: Best Practice accesskey attribute value must be unique

All accesskey attribute values in a document must be unique. Put another way, accesskeys must not be repeated to prevent unexpected effects for keyboard users.

WCAG: 1.1.1, 2.4.4, 4.1.2 Active <area> elements must have alternate text

An image map is a single image with many clickable areas. Like all images, an image map must have alternate text for each of the different clickable areas, as well as for the larger image itself, since screen readers have no way of translating graphics into text.

WCAG: 1.3.1 All cells in a <table> element that use the headers attribute must only refer to other cells of that same <table>

Data table markup can be tedious and confusing. Markup tables semantically and with the correct header structure. Screen readers have features to ease table navigation, but tables must be marked up accurately for these features to work correctly.

WCAG: 1.3.1 All <th> elements and elements with role="columnheader" or role="rowheader" must have data cells they describe

Data table markup can be tedious and confusing. Markup tables semantically and with the correct header structure. Screen readers have features to ease table navigation, but tables must be marked up accurately for these features to work correctly.

WCAG: 1.3.1 All non-empty <td> elements in tables larger than 3 by 3 must have an associated table header

Data table markup can be tedious and confusing. Tables must be marked up done semantically and with the correct header structure. Screen readers have features to ease table navigation, but tables must be marked up accurately for these features to work correctly.

WCAG: Best Practice All page content must be contained by landmarks

It is best practice to contain all content excepting skip links, within distinct regions such as the header, nav, main, and footer.

WCAG: 4.1.2 ARIA attributes must conform to valid names

ARIA attributes starting with aria- must have valid names. Referring to a misspelled attribute or to one that does not exist will result in an invalid attribute and thus failure of this rule.

WCAG: 4.1.2 ARIA attributes must conform to valid values

ARIA attributes starting with aria- must contain valid values. These values must be spelled correctly and correspond to values that make sense for a particular attribute in order to perform the intended accessibility function.

WCAG: 4.1.2 ARIA button, link, and menuitem must have an accessible name

ARIA command elements must have discernible text that clearly describes the destination, purpose, function, or action for screen reader users.

WCAG: Best Practice ARIA dialog and alertdialog must have an accessible name

Aria dialog elements must have discernible text that clearly describes the destination, purpose, function, or action for screen reader users.

WCAG: 4.1.2 aria-hidden elements do not contain focusable elements

This rule checks aria-hidden elements do not contain focusable elements.

WCAG: 4.1.2 aria-hidden="true" must not be present on the document <body>

Document content is not accessible to assistive technology if <body aria-hidden="true">.

WCAG: 4.1.2 ARIA input fields must have an accessible name

Ensures every ARIA input field has an accessible name.

WCAG: 1.1.1 ARIA meter must have an accessible name

Aria meter elements must have discernible text that clearly describes the destination, purpose, function, or action for screen reader users.

WCAG: 1.1.1 ARIA progressbar must have an accessible name

Aria progressbar elements must have discernible text that clearly describes the destination, purpose, function, or action for screen reader users.

WCAG: Best Practice ARIA role must be appropriate for the element

Values assigned to WAI-ARIA role attributes must be valid. This means values must be spelled correctly, correspond to existing ARIA role values, and must not be abstract roles in order to correctly expose the purpose of the element.

WCAG: 4.1.2 ARIA roles used must conform to valid values

Values assigned to ARIA role values must be valid. Role values must be spelled correctly, correspond to existing ARIA role values, and must not be abstract roles to correctly expose the purpose of the element.

WCAG: 4.1.2 ARIA toggle fields have an accessible name

Ensures every ARIA toggle field has an accessible name.

WCAG: 4.1.2 ARIA tooltip must have an accessible name

Aria tooltip elements must have discernible text that clearly describes the destination, purpose, function, or action for screen reader users.

WCAG: Best Practice ARIA treeitem must have an accessible name

Aria treeitem elements must have discernible text that clearly describes the destination, purpose, function, or action for screen reader users.

WCAG: 1.4.2 Audio must have controls that provide users with the ability to stop automatically played audio after three seconds

Ensures <video> or <audio> elements do not autoplay audio for more than three seconds without a control mechanism to stop or mute the audio.

WCAG: 1.3.5 Autocomplete attribute must be used correctly

The purpose for each common input field that collects an individual's personal data is programmatically defined based on the list of 53 Input Purposes for User Interface Components. The autocomplete attribute values must be valid and correctly applied for screen readers to function correctly.

WCAG: Best Practice Banner landmark must not be contained in another landmark

Banner landmark must not be contained in another landmark.

WCAG: 1.3.1 Bold, italic text and font-size are not used to style <p> elements as a heading

Styled p elements must not be used to represent headings because the structure of the document cannot otherwise be determined by screen reader users.

WCAG: 4.1.2 Buttons must have discernible text

Buttons must have discernible text that clearly describes the destination, purpose, function, or action for screen reader users.

The input-button-name rule separates functionality from the button-name rule to ensure that input buttons have discernible text; advise relevant to input button names was incorrect for button elements.

WCAG: 1.3.1 Certain ARIA roles must be contained by particular parent elements

Certain ARIA roles must be contained by particular parent roles in order to perform the intended accessibility functions.

WCAG: 1.3.1 Certain ARIA roles must contain particular children

Some ARIA parent role values applied to elements must contain specific child elements and role values to perform intended accessibility function.

WCAG: Best Practice Complementary landmarks and/or asides are top level

Ensures the complementary landmark or aside is at top level

WCAG: Best Practice Contentinfo landmark must not be contained in another landmark

Contentinfo landmark must be at top level.

WCAG: 1.3.4 CSS Media queries are not used to lock display orientation

The screen orientation (e.g. portrait or landscape) of mobile applications should not be locked in one mode. Users should be able to change the orientation of their device between portrait and landscape with the page adjusting accordingly in order to remain understandable. Also, when opening a page, it should display in the user’s current orientation.

WCAG: 1.3.1 Data or header cells should not be used to give caption to a data table

Data table markup can be tedious and confusing. Screen readers have some features to ease table navigation, but tables must be marked up accurately for these features to work correctly. Some tables use cells with a colspan element to visually indicate a caption, instead of using an actual caption element.

WCAG: 2.4.2 Documents must contain a title element to aid in navigation

The HTML document must have a title element to provide users with an overview of its content, and when present, it must not be empty.

WCAG: 1.1.1 Elements containing role="img" have an alternative text

Ensures elements marked role="img" elements have alternate text.

WCAG: Best Practice Elements in the focus order need a role appropriate for interactive content

User input elements must have appropriate roles, whether native HTML or a custom widget, to convey to screen reader users their meaning when landed on and given focus. If a custom widget, appropriate ARIA role values must be used instead of abstract roles to correctly expose the purpose of the element.

WCAG: 4.1.2 Elements must only use allowed ARIA attributes

Not all ARIA role-attribute combinations are valid. This Rule checks that each role is supplied with allowed attributes.

WCAG: Best Practice Elements should not have tabindex greater than zero

A tabindex attribute must never have a value greater than 0 to prevent an unexpected tab order that can give the appearance of skipping some elements entirely.

WCAG: Best Practice Elements whose role is none or presentation must not conflict with other roles.

Ensures elements which are marked to be removed from the accessibility tree are in fact removed.

WCAG: Best Practice Ensures the document has at most one main landmark

It is a best practice to ensure that there is only one main landmark to navigate to the primary content of the page and that if the page contains iframe elements, each should either contain no landmarks, or just a single landmark.

WCAG: 2.4.9 Ensure that links with the same accessible name serve a similar purpose

Ensure that links with the same accessible name serve a similar purpose.

WCAG: 2.4.7 Ensure that scrollable region has keyboard access
Elements that have scrollable content should be accessible by keyboard
WCAG: 3.3.2 Form fields do not have duplicate labels

Ensures form field does not have multiple labels.

WCAG: 1.3.1, 4.1.2 Form <input> elements must have labels

Each form element must have a programmatically associated label element.

WCAG: Best Practice Form <input> elements should have a visible label

Form <input> elements may be given a title using the title or aria-describedby attributes (but not both). These attributes are used to provide additional information such as a hint.

WCAG: Best Practice Frames must be tested with axe-core

Frames must be tested with axe-core.

WCAG: Best Practice Frames must have a unique title attribute

All frame or iframe elements in the document must have a unique title to describe their contents to screen reader users.

WCAG: 2.4.1, 4.1.2 Frames must have title attribute

All frame or iframe elements in the document must have a title that is not empty to describe their contents to screen reader users.

WCAG: Best Practice Heading levels should only increase by one

Headings must be in a valid logical order, meaning h1 through h6 element tags must appear in a sequentially-descending order.

WCAG: Best Practice Headings must not be empty

When at least one heading element (marked by <h1> through <h6>) is present, it is a best practice to ensure it contains content.

WCAG: Best Practice Hidden content on the page cannot be analyzed

Informs users about hidden content that cannot be analyzed for accessibility violations.

WCAG: 4.1.1 ID attribute value must be unique

The value assigned to active ID attributes on focusable elements must be unique to prevent the second instance from being overlooked by assistive technology. Put another way, active ID attributes may not be used more than once on focusable elements in the same document; focusable active elements require unique IDs for assistive technology to distinguish one element from another.

WCAG: 4.1.1 ID attribute values must be unique

The value assigned to an ID attribute must be unique to prevent the second instance from being overlooked by assistive technology. Put another way; ID attributes may not be used more than once in the same document to differentiate each element from another.

WCAG: 4.1.1 IDs used in ARIA and labels must be unique

The value assigned to an ARIA ID must be unique to prevent the second instance from being overlooked by assistive technology. Put another way; ARIA ID values may not be used more than once in the same document to differentiate each element from another.

WCAG: 1.1.1 Image buttons must have alternate text

Ensures <input type="image"> elements have alternate text.

WCAG: 1.1.1 Images must have alternate text

All images must have alternate text to convey their purpose and meaning to screen reader users.

WCAG: 1.4.12 Inline text spacing must be adjustable with custom stylesheets

Ensure that text spacing set through style attributes can be adjusted with custom stylesheets.

WCAG: 4.1.2 Input buttons must have discernible text

Ensures input buttons have discernible text.

The input-button-name rule separates functionality from the button-name rule to ensure that input buttons have discernible text; advise relevant to input button names was incorrect for button elements.

WCAG: 2.5.3 Label and name from content mismatch

Interactive elements labeled through their content must have their visible label as part of their accessible name

WCAG: Best Practice Landmarks must have a unique role or role/label/title (i.e. accessible name) combination
Landmarks must have a unique role or role/label/title (i.e. accessible name) combination.
WCAG: 3.1.2 lang attribute must have a valid value

The language specified in the HTML document must be one of the valid languages to ensure text is pronounced correctly for screen reader users.

WCAG: 1.4.1 Links must be distinguished from surrounding text in a way that does not rely on color

Ensures users who cannot distinguish between colors can tell when text is a link by verifying the link has either a distinct style that does not rely on color or has a contrast difference of greater than 3:1 (which alerts you that manual testing is required).

WCAG: 2.4.4, 4.1.2 Links must have discernible text

Link text and alternate text for images, when used as links, must be discernible by a screen reader, must not have a duplicate label, and must be focusable.

WCAG: 2.2.2 <blink> elements are deprecated and must not be used

This rule requires that no blink elements are present. Flashing text can be difficult to read and blinking objects can be difficult to activate. The associated automated check finds the presence of all blink elements so that they can be removed.

WCAG: 1.3.1 <dl> elements must only directly contain properly-ordered <dt> and <dd> groups, <script>, or <template> elements

Definition lists (dl) must contain only properly-ordered dt and dd groups, script or template elements.

WCAG: 1.3.1 <dt> and <dd> elements must be contained by a <dl>

Definition list items (dt and/or dd) must be wrapped in parent dl elements to be valid. This enables screen reader users to understand the proper hierarchy of information in the list.

WCAG: 3.1.1 <html> element must have a lang attribute

The HTML document element must contain a valid lang attribute or must correspond to a valid lang code for multilingual screen reader users who may prefer a language other than the default.

WCAG: 3.1.1 <html> element must have a valid value for the lang attribute

The HTML document must contain a valid lang attribute or must correspond to a valid lang code for multilingual screen reader users who may prefer a language other than the default.

WCAG: 3.1.1 <html> elements with lang and xml:lang must have the same base language

The HTML document must contain a valid lang attribute or must correspond to a valid lang code for multilingual screen reader users who may prefer a language other than the default. The xml:lang attribute value, if included on the html element, must duplicate the value of the lang exactly.

WCAG: 1.3.1 <li> elements must be contained in a <ul> or <ol>

All list items (li) must be contained within ul or ol parent elements.

WCAG: 2.2.2 <marquee> elements are deprecated and must not be used

<marquee> elements must not be present because they are deprecated, increase difficulty for users with limited dexterity, and are distracting for users with cognitive or attention deficits.

WCAG: 1.1.1 <object> elements must have alternate text

All embedded objects must have text alternatives to be read out to screen reader users.

WCAG: 1.3.1 <ul> and <ol> must only directly contain <li>, <script> or <template> elements

Lists must be marked up correctly, meaning they must not contain content elements other than li elements.

WCAG: Best Practice Main landmark must not be contained in another landmark

It is a best practice to ensure the main landmark is not contained within another landmark. All content should be contained within distinct regions such as the header (role="banner"), content (role="main"), and footer (role="contentinfo").

WCAG: Best Practice Page must contain a level-one heading

Ensures that the page, or at least one of its frames, contains an h1 element that appears before the start of the main content to allow screen reader users to use keyboard shortcuts to navigate the heading structure instead of wasting time listening to more of the web page to understand its structure.

WCAG: 2.4.1 Page must have means to bypass repeated blocks

Each page must have a main landmark to provide a mechanism to bypass repeated blocks of content or interface elements (like header and navigation) and quickly arrive at the main content.

WCAG: Best Practice Page must have one main landmark

It is a best practice to ensure that there is only one main landmark to navigate to the primary content of the page and that if the page contains iframe elements, each should either contain no landmarks, or just a single landmark.

WCAG: Best Practice Page must not have more than one banner landmark

Ensures the page has at most one banner landmark.

WCAG: Best Practice Page must not have more than one contentinfo landmark

Ensures the page has at most one contentinfo landmark.

WCAG: 4.1.2 Required ARIA attributes must be provided

ARIA widget roles must have appropriate attributes describing the state or properties of the widget.

WCAG: Best Practice Scope attribute should be used correctly on tables

The scope attribute must be used correctly on tables in accordance with either HTML4 or HTML5 specifications to enable efficient table navigation for screen reader users.

WCAG: 4.1.2 select element must have an accessible name

Each select element must have a programmatically associated label element.

WCAG: 2.1.1 Server-side image maps must not be used

The document contains an image map that is server-side instead of client-side.

WCAG: 1.1.1 SVG images and graphics require accessible text

Ensures SVG elements with an <img>, graphics-document or graphics-symbol role have an accessible text alternative.

WCAG: 1.4.3 Text elements must have sufficient color contrast against the background

All text elements must have sufficient contrast between text in the foreground and background colors behind it in accordance with WCAG 2 AA contrast ratio thresholds.

WCAG: Best Practice Text of buttons and links should not be repeated in the image alternative

When button and link text repeats in a alt attribute value, screen reader users hear the same information twice, which renders the alt text meaningless and confusing.

WCAG: Best Practice The <caption> element should not contain the same text as the summary attribute

Data table markup can be tedious and confusing. Make sure the caption and summary table attributes are not identical. Screen readers have some features to manage table navigation, but tables must be marked up accurately for these features to work correctly.

WCAG: Best Practice The skip-link target should exist and be focusable

The page must have a link at the top before the navigation that allows users to skip lengthy navigation and proceed to a page's main content to save time.

WCAG: 2.2.1, 2.2.4, 3.2.5 Timed refresh must not exist

The document must not use <meta http-equiv="refresh"> because it can prevent control over when the refresh occurs for users with disabilities.

WCAG: 4.1.2 Use aria-roledescription on elements with a semantic role

Ensures that the aria-roledescription attribute is only used on elements with an implicit or explicit role values.

WCAG: Best Practice Users should be able to zoom and scale the text up to 500%

The document must not use the user-scalable="no" parameter in the <meta name="viewport"> element because it disables text scaling and zooming which is essential to users with low vision.

WCAG: 1.4.4 Zooming and scaling must not be disabled

The document must not use the user-scalable="no" parameter in the <meta name="viewport"> element because it disables text scaling and zooming which is essential to users with low vision.