Skip to content
Accessibility Audit Template
Share
Explore
Principle
Guideline
Success Criteria
Level
Recommendation
Claim Audit
Auditor
Add Task
Conformance
Notes
1 Perceivable 🔍
52
1.1 Text Alternatives
7
1.1.1 Non-text Content
7
A
Images, form image buttons, and image map hot spots have appropriate, equivalent
alternative text
.
Claim
Add Task
A
Images that do not convey content, are decorative, or contain content that is already conveyed in text are given null alt text (alt="") or implemented as CSS backgrounds. All linked images have descriptive alternative text.
Claim
Add Task
A
Equivalent alternatives to complex images are provided in context or on a separate linked page.
Claim
Add Task
A
Form buttons have a descriptive value.
Claim
Add Task
A
Form inputs have associated
text labels
.
Claim
Add Task
A
Embedded multimedia is identified via accessible text.
Claim
Add Task
A
Frames and iFrames are appropriately
titled
.
Claim
Add Task
1.2 Time-based Media
10
1.2.1 Prerecorded Audio-only and Video-only
2
A
A
transcript
of relevant content is provided for non-live audio-only (audio podcasts, MP3 files, etc.).
Claim
Add Task
A
A transcript or
audio description
of relevant content is provided for non-live video-only, unless the video is decorative.
Claim
Add Task
1.2.2 Captions (prerecorded)
1
A
Synchronized captions
are provided for non-live video (YouTube videos, etc.).
Claim
Add Task
1.2.5 Audio Description (prerecorded)
1
A
A transcript or audio description is provided for non-live video. (NOTE: Only required if there is relevant visual content that is not presented in the audio.)
Claim
Add Task
1.2.4 Captions (Live)
1
AA
Synchronized captions are provided for live media that contains audio (audio-only broadcasts, web casts, video conferences, etc.)
Claim
Add Task
1.2.5 Audio Description (Prerecorded)
1
AA
Audio descriptions are provided for non-live video. (NOTE: Only required if there is relevant visual content that is not presented in the audio. Also, while not required at Level AA, for optimal accessibility WebAIM recommends transcripts in addition to audio descriptions.)
Claim
Add Task
1.2.6 Sign Language (Prerecorded)
1
AAA
A sign language video is provided for media that contains audio.
Claim
Add Task
1.2.7 Extended Audio Description (Prerecorded)
1
AAA
When audio description cannot be added to video due to audio timing (e.g., insufficient pauses in the audio), an alternative version of the video with pauses that allow audio descriptions is provided.
Claim
Add Task
1.2.8 Media Alternative (Prerecorded)
1
AAA
A transcript is provided for pre-recorded media that has a video track. For optimal accessibility, WebAIM strongly recommends transcripts for all multimedia.
Claim
Add Task
1.2.9 Audio-only (Live)
1
AAA
A descriptive text transcript (e.g., the script of the live audio) is provided for live content that has audio.
Claim
Add Task
1.3 Adaptable
10
1.3.1 Info and Relationships
3
A
Semantic markup
is used to designate headings (<h1>), regions/landmarks, lists (<ul>, <ol>, and <dl>), emphasized or special text (<strong>, <code>, <abbr>, <blockquote>, for example), etc. Semantic markup is used appropriately.
Claim
Add Task
A
Tables
are used for tabular data and data cells are associated with their headers. Data table captions, if present, are associated to data tables.
Claim
Add Task
A
Text labels
are associated with form input elements. Related form elements are grouped with fieldset/legend. ARIA labelling may be used when standard HTML is insufficient.
Claim
Add Task
1.3.2 Meaningful Sequence
1
A
The
reading and navigation order
(determined by code order) is logical and intuitive.
Claim
Add Task
1.3.3 Sensory Characteristics
2
A
Instructions do not rely upon shape, size, or visual location (e.g., "Click the square icon to continue" or "Instructions are in the right-hand column").
Claim
Add Task
A
Instructions do not rely upon sound (e.g., "A beeping sound indicates you may continue.").
Claim
Add Task
1.3.4 Orientation
1
AA
Orientation of web content is not restricted to only portrait or landscape, unless a specific orientation is necessary.
Claim
Add Task
1.3.5 Identify Input Purpose
1
AA
Input fields that collect
certain types of user information
have an appropriate autocomplete attribute defined.
Claim
Add Task
1.3.6 Identify Purpose
2
AAA
HTML5 regions or ARIA landmarks are used to identify page regions.
Claim
Add Task
AAA
ARIA is used, where appropriate, to enhance HTML semantics to better identify the purpose of interface components.
Claim
Add Task
1.4 Distinguishable
25
1.4.1 Use of Color
2
A
Color is not used as the sole method of conveying content or distinguishing visual elements.
Claim
Add Task
A
Color alone is not used to distinguish
links
from surrounding text unless the
contrast ratio
between the link and the surrounding text is at least 3:1
and
an additional distinction (e.g., it becomes underlined) is provided when the link is hovered over and receives focus.
Claim
Add Task
1.4.2 Audio Control
1
A
A mechanism is provided to stop, pause, mute, or adjust volume for audio that automatically plays on a page for more than 3 seconds.
Claim
Add Task
1.4.3 Contrast (Minimum)
2
AA
Text and images of text have a contrast ratio of at least 4.5:1.
Claim
Add Task
AA
Large text - at least 18 point (typically 24px) or 14 point (typically 18.66px) and bold - has a contrast ratio of at least 3:1.
Claim
Add Task
1.4.4 Resize text
1
AA
The page is readable and functional when the page is zoomed to 200%. NOTE: 1.4.10 introduces a much higher requirement for zoomed content.
Claim
Add Task
1.4.9 Images of Text (No Exception)
2
AA
If the same visual presentation can be made using text alone, an image is not used to present that text.
Claim
Add Task
AAA
Text is used within an image only for decoration (image does not convey content) OR when the information cannot be presented with text alone.
Claim
Add Task
1.4.10 Reflow
2
AA
No loss of content or functionality occurs and horizontal scrolling is avoided when content is presented at a width of 320 pixels. This requires responsive design for most web sites. This is best tested by setting the browser window to 1280 pixels wide and then zooming the page content to 400%.
Claim
Add Task
AA
Content that requires horizontal scrolling, such as data tables, complex images (such as maps and charts), toolbars, etc. are exempted.
Claim
Add Task
1.4.11 Non-text Contrast
2
AA
A contrast ratio of at least 3:1 is present for differentiating graphical objects (such as icons and components of charts or graphs) and author-customized interface components (such as buttons, form controls, and focus indicators/outlines).
Claim
Add Task
AA
At least 3:1 contrast must be provided in the various states (focus, hover, active, etc.) of author-customized interactive components.
Claim
Add Task
1.4.12 Text Spacing
2
AA
No loss of content or functionality occurs when the user adapts paragraph spacing to 2 times the font size, text line height/spacing to 1.5 times the font size, word spacing to .16 times the font size, and letter spacing to .12 times the font size.
Claim
Add Task
AA
This is best supported by avoiding pixel height definitions for elements that contain text.
Claim
Add Task
1.4.13 Content on Hover or Focus
3
AA
When additional content is presented on hover or keyboard focus. the newly revealed content can be dismissed (generally via the Esc key) without moving the pointer or keyboard focus, unless the content presents an input error or does not obscure or interfere with other page content.
Claim
Add Task
AA
When additional content is presented on hover or keyboard focus, the pointer can be moved to the new content without the content disappearing.
Claim
Add Task
AA
When additional content is presented on hover or keyboard focus, the new content must remain visible until the pointer or keyboard focus is moved away from the triggering control, the new content is dismissed, or the new content is no longer relevant.
Claim
Add Task
1.4.6 Contrast (Enhanced)
2
AAA
Text and images of text have a contrast ratio of at least 7:1.
Claim
Add Task
AAA
Large text - at least 18 point (typically 24px) or 14 point (typically 18.66px) bold - has a contrast ratio of at least 4.5:1.
Claim
Add Task
1.4.7 Low or No Background Audio
1
AAA
Audio with speech has no or very low background noise so the speech is easily distinguished.
Claim
Add Task
1.4.8 Visual Presentation
5
AAA
Blocks of text over one sentence in length are no more than 80 characters wide.
Claim
Add Task
AAA
Blocks of text over one sentence in length are NOT fully justified (aligned to both the left and the right margins).
Claim
Add Task
AAA
Blocks of text over one sentence in length have adequate line spacing (at least 1/2 the height of the text) and paragraph spacing (1.5 times line spacing).
Claim
Add Task
AAA
Blocks of text over one sentence in length have a specified foreground and background color. These can be applied to specific elements or to the entire page using CSS (and thus inherited by all other elements).
Claim
Add Task
AAA
Blocks of text over one sentence in length do NOT require horizontal scrolling when the text size is doubled.
Claim
Add Task
2 Operable 🔧
33
2.1 Keyboard Accessible
5
2.1.1 Keyboard
2
A
All page functionality is available using the
keyboard
, unless the functionality cannot be accomplished in any known way using a keyboard (e.g., free hand drawing).
Claim
Add Task
A
Page-specified shortcut keys and accesskeys (accesskey should typically be avoided) do not conflict with existing browser and screen reader shortcuts.
Claim
Add Task
2.1.2 No Keyboard Trap
1
A
Keyboard
focus is never locked or trapped at one particular page element. The user can navigate to and from all navigable page elements using only a keyboard.
Claim
Add Task
2.1.3 Keyboard (No Exception)
1
AAA
All page functionality is available using the keyboard.
Claim
Add Task
2.1.4 Character Key Shortcuts
1
A
If a keyboard shortcut uses printable character keys, then the user must be able to disable the key command, change the defined key to a non-printable key (Ctrl, Alt, etc.), or only activate the shortcut when an associated interface component or button is focused.
Claim
Add Task
2.2 Enough Time
7
2.2.1 Timing Adjustable
1
A
If a page or application has a time limit, the user is given options to turn off, adjust, or extend that time limit. This is not a requirement for real-time events (e.g., an auction), where the time limit is absolutely required, or if the time limit is longer than 20 hours.
Claim
Add Task
2.2.2 Pause, Stop, Hide
2
A
Automatically moving, blinking, or scrolling content (such as carousels, marquees, or animations) that lasts longer than 5 seconds can be paused, stopped, or hidden by the user.
Claim
Add Task
A
Automatically updating content (e.g., a dynamically-updating news ticker, chat messages, etc.) can be paused, stopped, or hidden by the user or the user can manually control the timing of the updates.
Claim
Add Task
2.2.3 No Timing
1
AAA
The content and functionality have no time limits or constraints.
Claim
Add Task
2.2.4 Interruptions
1
AAA
Interruptions (alerts, page updates, etc.) can be postponed or suppressed by the user.
Claim
Add Task
2.2.5 Re-authenticating
1
AAA
If an authentication session expires, the user can re-authenticate and continue the activity without losing any data from the current page.
Claim
Add Task
2.2.6 Timeouts
1
AAA
Users must be warned of any timeout that could result in data loss, unless the data is preserved for longer than 20 hours of user inactivity.
Claim
Add Task
2.3 Seizures and Physical Reactions
3
2.3.1 Three Flashes or Below Threshold
1
A
No page content
flashes
more than 3 times per second unless that flashing content is sufficiently small and the flashes are of low contrast and do not contain too much red. (
See general flash and red flash thresholds
)
Claim
Add Task
2.3.2 Three Flashes
1
AAA
No page content flashes more than 3 times per second.
Claim
Add Task
2.3.3 Animation from Interactions
1
AAA
Users can disable non-essential animation and movement that is triggered by user interaction.
Claim
Add Task
2.4 Navigable
12
2.4.1 Bypass Blocks
2
A
A link is provided to skip navigation and other page elements that are repeated across web pages.
Claim
Add Task
A
A proper heading structure and/or identification of page regions/landmarks may be considered a sufficient technique. Because navigating by headings or regions is not supported in most browsers, WebAIM recommends a "skip" link (in addition to headings and regions) to best support sighted keyboard users.
Claim
Add Task
2.4.2 Page Titled
1
A
The web page has a descriptive and informative page title.
Claim
Add Task
2.4.3 Focus Order
1
A
The navigation order of links, form elements, etc. is logical and intuitive.
Claim
Add Task
2.4.4 Link Purpose (In Context)
2
A
The purpose of each link (or form image button or image map hotspot) can be determined from the link text alone, or from the link text and its context (e.g., surrounding text, list item, previous heading, or table headers).
Claim
Add Task
A
Links (or form image buttons) with the same text that go to different locations are readily distinguishable.
Claim
Add Task
2.4.5 Multiple Ways
1
AA
Multiple ways
are available to find other web pages on the site - at least two of: a list of related pages, table of contents, site map, site search, or list of all available web pages.
Claim
Add Task
2.4.7 Focus Visible
1
AA
Page headings and labels for form and interactive controls are informative. Avoid duplicating heading (e.g., "More Details") or label text (e.g., "First Name") unless the structure provides adequate differentiation between them.
Claim
Add Task
2.4.8 Location
1
AAA
If a web page is part of a sequence of pages or within a complex site structure, an indication of the current page location is provided, for example, through breadcrumbs or specifying the current step in a sequence (e.g., "Step 2 of 5 - Shipping Address").
Claim
Add Task
2.4.9 Link Purpose (Link Only)
2
AAA
The purpose of each link (or form image button or image map hotspot) can be determined from the link text alone.
Claim
Add Task
AAA
There are no links (or form image buttons) with the same text that go to different locations.
Claim
Add Task
2.4.10 Section Headings
1
AAA
Beyond providing an overall document structure, individual sections of content are designated using headings, where appropriate.
Claim
Add Task
2.5 Input Modalities
6
2.5.1 Pointer Gestures
1
A
If multipoint or path-based gestures (such as pinching, swiping, or dragging across the screen) are not essential to the functionality, then the functionality can also be performed with a single point activation (such as activating a button).
Claim
Add Task
2.5.2 Pointer Cancellation
1
A
To help avoid inadvertent activation of controls, avoid non-essential down-event (e.g., onmousedown) activation when clicking, tapping, or long pressing the screen. Use onclick, onmouseup, or similar instead. If onmouseup (or similar) is used, you must provide a mechanism to abort or undo the action performed.
Claim
Add Task
2.5.3 Label in Name
1
A
If an interface component (link, button, etc.) presents text (or images of text), the accessible name (label, alternative text, aria-label, etc.) for that component must include the visible text.
Claim
Add Task
2.5.4 Motion Actuation
1
A
Functionality that is triggered by moving the device (such as shaking or panning a mobile device) or by user movement (such as waving to a camera) can be disabled and equivalent functionality is provided via standard controls like buttons.
Claim
Add Task
2.5.5 Target Size
1
AAA
Clickable targets are at least 44 by 44 pixels in size unless an alternative target of that size is provided, the target is inline (such as a link within a sentence), the target is not author-modified (such as a default checkbox), or the small target size is essential to the functionality.
Claim
Add Task
2.5.6 Concurrent Input Mechanisms
1
AAA
Content does not restrict input to a specific modality, such as touch-only or keyboard-only, but must support alternative inputs (such as using a keyboard on a mobile device).
Claim
Add Task
3 Understandable 🗣️
18
3.1 Readable
6
3.1.1 Language of Page
1
A
The language of the page is identified using the HTML lang attribute (e.g., <html lang="en">).
Claim
Add Task
3.1.2 Language of Parts
1
AA
The language of page content that is in a different language is identified using the lang attribute (e.g., <blockquote lang="es">).
Claim
Add Task
3.1.3 Unusual Words
1
AAA
Words
that may be ambiguous, unfamiliar, or used in a very specific way are defined through adjacent text, a definition list, a glossary, or other suitable method.
Claim
Add Task
3.1.4 Abbreviations
1
AAA
The meaning of an unfamiliar abbreviation is provided by expanding it the first time it is used, using the <abbr> element, or linking to a definition or glossary.
Claim
Add Task
3.1.5 Reading Level
1
AAA
A more understandable alternative is provided for content that is more advanced than can be reasonably read by a person with roughly 9 years of primary education.
Claim
Add Task
3.1.6 Pronunciation
1
AAA
If the pronunciation of a word is vital to understanding that word, its pronunciation is provided immediately following the word or via a link or glossary.
Claim
Add Task
3.2 Predictable
5
3.2.1 On Focus
1
A
When a page element receives focus, it does not result in a substantial change to the page, the spawning of a pop-up window, an additional change of keyboard focus, or any other change that could confuse or disorient the user.
Claim
Add Task
3.2.2 On Input
1
A
When a user inputs information or interacts with a control, it does not result in a substantial change to the page, the spawning of a pop-up window, an additional change of keyboard focus, or any other change that could confuse or disorient the user unless the user is informed of the change ahead of time.
Claim
Add Task
3.2.3 Consistent Navigation
1
AA
Navigation links that are repeated on web pages do not change order when navigating through the site.
Claim
Add Task
3.2.5 Change on Request
1
AAA
Substantial changes to the page, the spawning of pop-up windows, uncontrolled changes of keyboard focus, or any other change that could confuse or disorient the user must be initiated by the user. Alternatively, the user is provided an option to disable such changes.
Claim
Add Task
3.2.4 Consistent Identification
1
AA
Elements that have the same functionality across multiple web pages are consistently identified. For example, a search box at the top of the site should always be labeled the same way.
Claim
Add Task
3.3 Input Assistance
7
3.3.1 Error Identification
2
A
Required form elements or form elements that require a specific format, value, or length provide this information within the element's label.
Claim
Add Task
A
Form validation
errors are efficient, intuitive, and accessible. The error is clearly identified, quick access to the problematic element is provided, and the user can easily fix the error and resubmit the form.
Claim
Add Task
3.3.2 Labels or Instructions
1
A
Sufficient labels, cues, and instructions for required interactive elements are provided via instructions, examples, properly positioned form labels, and/or fieldsets/legends.
Claim
Add Task
3.3.3 Error Suggestion
1
AA
If an input error is detected (via client-side or server-side validation), suggestions are provided for fixing the input in a timely and accessible manner.
Claim
Add Task
3.3.4 Error Prevention (Legal, Financial, Data)
1
AA
If the user can change or delete legal, financial, or test data, the changes/deletions can be reversed, verified, or confirmed.
Claim
Add Task
3.3.5 Help
1
AAA
Instructions and cues are provided in context to help in form completion and submission.
Claim
Add Task
3.3.6 Error Prevention (All)
1
AAA
If the user can submit information, the submission is reversible, verified, or confirmed.
Claim
Add Task
4 Robust 📖
4
4.1 Compatible
4
4.1.1 Parsing
1
A
Significant HTML/XHTML validation/parsing errors are avoided. Check at
http://validator.w3.org/
Claim
Add Task
4.1.2 Name, Role, Value
2
A
Markup is used in a way that facilitates accessibility. This includes following the HTML/XHTML specifications and using forms, form labels, frame titles, etc. appropriately.
Claim
Add Task
A
ARIA is used appropriately to enhance accessibility when HTML is not sufficient.
Claim
Add Task
4.1.3 Status Messages
1
AA
If an important status message is presented and focus is not set to that message, the message must be announced to screen reader users, typically via an ARIA alert or live region.
Claim
Add Task
Want to print your doc?
This is not the way.
This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (
CtrlP
) instead.