This check identifies pages that potentially require color for visual checking.

Organize documents so they may be read without style sheets. For example, when an HTML document is rendered without associated style sheets, it must still be possible to read the page.

Users with vision loss or cognitive challenges often require specific foreground (text) and background color combinations. For instance, many people with low vision find it much easier to see a Web page that has white text on a black background, so they may have set their user agent to create this contrast. If the author specifies that the text must be black, then it may override the settings of the user agent and render a page that has black text (specified by the author) on black background (that was set in the user agent). This principle also works in reverse. If the Webmaster forces the background to be white, then the white background specified by the author would be the same color as the white text (which was set in the user agent) rendering the page unusable to the user. Therefore, if the author specifies a foreground (text) color then they should also specify a background color which has sufficient contrast (link) with the foreground and vice versa.

If a Text Only Equivalent of a page is provided it must be updated every time the primary content changes. This checkpoint typically gets marked N/A because there are sufficient techniques for making complex web content accessible. This checkpoint may need to be customized.

The objective of this technique is to provide users with all the time they need to complete an activity. This technique involves providing a specified activity which does not require timed interaction. Users are allowed as much time as they need to interact with the activity.

Until user agents provide the ability to stop the refresh, do not create periodically auto-refreshing pages.

The ALT or LONGDESC attribute is used by user agents to supply information about an image when images cannot be shown.

APPLET elements provide functionality that is not available to all users. Either the element content or the ALT attribute are used to describe the purpose of the applet, depending on the user agent.

EMBED elements present functionality not available to all users. The NOEMBED element can be used to provide a deion. ARIA attributes can be use as an alternative of NOEMBED element for providing deion.

OBJECT elements typically use technologies that are not available to all users. The element content is used to describe the purpose of the object/applet.

SVG elements requires title or desc child elements or ARIA attributes which describe purpose of element.

Figcaption contains describe the purpose of the figure or any other element which is inside figure element.

For any time-based multimedia presentation (e.g., a movie or animation), synchronize equivalent alternatives (e.g., captions or auditory deions of the visual track) with the presentation.

For any time-based multimedia presentation (e.g., a movie or animation), synchronize equivalent alternatives (e.g., captions or auditory deions of the visual track) with the presentation.

If you must use a server-side image map, provide redundant text links for each active region. You should use client-side image maps where possible.

Client-side image maps present functionality that is not available to all users. The ALT attribute can be used for AREA elements to provide a text equivalent.

This check identifies data tables that do not have any TH elements. Data tables are recognised as having a border attribute greater than 0. Tables with no border require a visual check, unless they contain input, image or child table elements, or cells with long text, indicating they are most likely layout tables.

Describe the table structure using the SUMMARY attribute or ARIA attributes. Identify structural groups of rows using THEAD, TFOOT, TBODY, COLGROUP and COL. Label table elements with the "scope", "headers", and "axis" attributes to assist user agents.

IFRAME elements provide functionality that is not available to all users. The element content should describe the purpose of the IFRAME.

Pages with frames are not available to all users. The NOFRAMES element should used to provide an alternative.

This checkpoint may require customization.

Until user agents support explicit associations between labels and form controls, for all form controls with implicitly associated labels, ensure that the label is properly positioned.

All visible INPUT elements must have a label, either by using a linked or containing LABEL element, or by using the ALT or TITLE attribute. Buttons are considered to be self-labeling.

All SELECT elements must have a label, either by using a linked or containing LABEL element, or by using the TITLE or ALT attribute.

All TEXTAREA elements must have a label, either by using a linked or containing LABEL element, or by using the TITLE or ALT attribute.

The placeholder attribute represents a short hint (a word or short phrase) intended to aid the user with data entry. A hint could be a sample value or a brief deion of the expected format. The placeholder text gets removed as the form is being filled out and forms needs to be usable even when placeholder text is not there.

This checkpoint may require customization.