Skip to main content (Press Enter).
Skip to navigation content (Press Enter).
Forms or other interactive content
Animations, moving content, flashing content
A form that causes a legal/financial commitment, grades a test response, or modifies/deletes data
Audio content that plays automatically and lasts longer than 3 seconds
A time limit of any sort
A table containing data
A CAPTCHA (human verification) script
A visual presentation without audio such as a slideshow
A movie that has both audio and visual elements
Audio-only media (such as music, spoken phrases, etc.)
Phrases in the web page that are not in English
Now continue by checking off every checkpoint that your web page satisfies. Once you've checked off all of your boxes, you have completed a WCAG evaluation for your web page!
All non-text content has a text alternative. (See Guideline 1.1)
Text content is organized using <p> tags. (See Section 1.3.1)
Content is emphasized using <em> and <strong> tags, and doesn't use <b> or <i> tags or solely rely on CSS to convey emphasis. (See Section 1.3.1)
Lists, groups of links, or other listable items are listed using <ol>, <ul>, or <dl>. (See Section 1.3.1)
The content of a web page can be perceived easily when reading from top to bottom in the source code. (See Section 1.3.2)
The presentation of a web page does not rely on a single sensory characteristic such as shape, size, visual location, orientation, or sound. (See Section 1.3.3)
Colour is not the only way to distinguish information or indicating anything else on a web page. (See Section 1.4.1)
All text and images of text have a contrast ratio of at least 4.5:1, large-scale text has a contrast ratio of at least 3:1. (See Section 1.4.3)
Web page does not lose quality when resized to 200%. (See Section 1.4.4)
Text is used to convey information rather than images of text if it's possible at all. (See Section 1.4.5)
All functionality of the web page is available through keyboard without requiring specific timing for keystrokes. (See Section 2.1.1)
All components that receive keyboard focus can be unfocused via the keyboard. (See Section 2.1.2)
A mechanism exists to bypass reoccuring blocks on a web page, such as the navigation menus. (See Section 2.4.1)
The web page has a <title> tag that describes the topic/purpose accurately. (See Section 2.4.2)
Components receive focus in a predictable order. (See Section 2.4.3)
All links describe its purpose accurately by itself or within the context of the links. (See Section 2.4.4)
There are at least two ways to navigate from the web page. (See Section 2.4.5)
Headings are used properly in a hierchical fashion, and describe the topic accurately. (See Guideline 1.1 and Section 2.4.6)
All elements that receive focus from keyboard navigation retains its focus indicator. (See Section 2.4.7)
The <html> tag includes xml:lang="en" and lang="en" attributes. (See Section 3.1.1)
A component doesn't change the context of the web page when it receives focus from either the mouse or keyboard. (See Section 3.2.1)
A user interface component (such as a drop-down box) doesn't change the context of a web page when it's changed. (See Section 3.2.2)
Navigation menus that appear on multiple web pages appear in the same order. (See Section 3.2.3)
Functional components (search boxes, etc.) that appear in multiple web pages are identified consistently. (See Section 3.2.4)
Web page passes the W3C Validator. (See Section 4.1.1)
Labels or title attributes are provided for every text field, radio button, check box, or any other type of user interface component. (See Guideline 1.1)
Radio selection and checkbox options are grouped together using the <fieldset> tag with a proper <legend> tag inside of it. (See Section 1.3.1)
<select> options are grouped together using the <optgroup> tag. (See Section 1.3.1)
Input error is automatically detected and described to the user in text, with suggestions for corrections as well. (See Section 3.3.3)
Labels include instructions on entering the necessary input, or instructions are described at the beginning of the form. (See Section 3.3.2)
Required fields are labeled with the phrase "(required)". (See Section 3.3.2)
Checkboxes and radio buttons are placed before the labels and not after. (See Section 3.3.2)
Page does not change context when any element in the form is changed (i.e. the page doesn't reload when selecting a different country to reflect different states/provinces).
If any moving/blinking/scrolling content starts automatically and lasts longer than 5 seconds, a mechanism exists to pause/stop/hide the content. (See Section 2.2.2)
If a live feed such as an automatically updated Twitter feed or anything of the like is integrated into the page, there is a mechanism to pause/stop/hide the content or change the frequency of the updates. (See Section 2.2.2)
There is absolutely no flashing content that flashes more than 3 times per second. (See Guideline 2.3)
A confirmation page exists when any irreversible user action is performed, such as a financial transaction, a legal commitment, a test grading system, or irreversible deletion of data. (See Section 3.3.4)
Audio content that plays automatically and lasts longer than 3 seconds has a mechanism to stop the audio or turn down the volume of the audio. (See Section 1.4.2)
One of the following is true: (see Section 2.2.1)
The user is allowed to turn off the time limit before encountering it
The user is allowed to multiply the time limit by a factor of 10 before encountering it
The user is warned before the time expires and is given at least 20 seconds to multiply the time limit by a factor of 10 with a simple action (i.e. pressing the spacebar)
The time limit is part of a real-time event (therefore no extension is possible)
The time limit is essential (therefore no extension is possible)
The time limit is longer than 20 hours (therefore no extension is needed)
See WebAIM's Tutorial on Accessible Tables
A summary attribute exists in the <table> tag if the table is relaying complex information.
<th> header cells exist and use either scope attributes or header attributes to convey relationships with cells.
Cells that have coloured backgrounds to signify special properties are given a text alternative.
<th> header cell tags are not used to visually style non-header cells.
See Guideline 1.1
A text alternative describes the purpose of the CAPTCHA image.
Alternative forms of the CAPTCHA verification are provided (such as an audio CAPTCHA or a trivia question)
A text alternative or an audio track exists that accurately describes everything presented in the visual presentation. (See Section 1.2.1)
See Guideline 1.2
Captions are provided on the video track and/or is encoded through the audio track of the movie.
An alternative to the movie is provided, such as a transcript which describes actions, cues, and what is spoken in the movie.
A text alternative exists that accurately describes everything presented in the audio presentation. (See Section 1.2.1)
Non-English phrases are programmatically tagged using the lang and xml:lang attributes. (See Section 3.1.2)
