Important note: This Wiki page is edited by participants of the EOWG. It does not necessarily represent consensus and it may have incorrect information or information that is not supported by other Working Group participants, WAI, or W3C. It may also have some very useful information.


Accessibility Checkpoint Master List

From Education & Outreach
Jump to: navigation, search

Parent document: https://www.w3.org/WAI/EO/wiki/ARRM_Project_-_Accessibility_Roles_and_Responsibilities_Mapping

IMPORTANT NOTES:
  • This document is internal to the EOWG, and is meant to support the creation of the role-based resources being developed under the ARRM project.
  • The EOWG does not support this resource as an exhaustive list of checkpoints to meet WCAG 2.
  • It SHOULD NOT be referenced outside of this body of work.
  • It is NOT meant to be distributed as a standalone resource.
Success Criteria not covered as of 2021/07/06:
  • 1.3.4 - Orientation
  • 1.3.5 - Identify Input Purpose
  • 1.3.6 - Identify Purpose
  • 1.4.6 - Contrast (Enhanced)
  • 1.4.7 - Low or No Background Audio
  • 1.4.8 - Visual Presentation
  • 1.4.9 - Images of Text (No Exception)
  • 1.4.10 - Reflow
  • 1.4.11 - Non-text Contrast
  • 1.4.12 - Text Spacing
  • 1.4.13 - Content on Hover or Focus
  • 2.1.3 - Keyboard (No Exception)
  • 2.1.4 - Character Key Shortcuts
  • 2.2.3 - No Timing

Images and Graphs

ID WCAG SC Conformance Level Checkpoint Main Role Role Ownership Keep (+) / remove (-)?
Primary Secondary Contributor(s) Jenn Denis Bill Sean Lewis Michael
IMG-001 1.1.1 A Informative alternate text is provided for images (i.e. not "spacer" or image file name). Author Content Authoring UX Design none + + + + + +
IMG-002 1.1.1 A Informative images are described with a clear and meaningful text equivalent (alt attribute or other equivalent means). Author Content Authoring Visual Design UX Design + + + + + +
IMG-003 1.1.1 A Purely decorative images are provided with null alt attribute values (or other equivalent means). Development Front-End Development none none + + + + + +
IMG-004 1.1.1 A Null alt attribute values are used for images that are already described in text in adjacent page content. Development Front-End Development UX Design Content Authoring
Visual Design
+ + + + + +
IMG-005 1.1.1 A Adjacent linked images and text links pointing the same URL are combined into single links. Development Front-End Development UX Design none + + + + + +
IMG-006 1.1.1 A Alt text used for images of text include all relevant text found in the image. Author Content Authoring UX Design
Visual Design
none + + + + + +
IMG-007 1.1.1 A Informative images are marked up as foreground images, and not embedded as part of the CSS. Development Front-End Development none none + + + + + +
IMG-008 1.1.1 A The purpose or function of complex images is accurately described in text. Author Content Authoring UX Design none + + + + + +
IMG-009 1.1.1 A The purpose or function of complex images is conveyed using a descriptive alt attribute value (or other equivalent means). Development Front-End Development none none + + + + + +
IMG-010 1.1.1 A The full explanation of complex images is accurately described in text. Author Content Authoring none none + + + + + +
IMG-011 1.1.1 A A mechanism that conveys the way through which the full explanation of complex images is defined. Design UX Design none none + + + + + +
IMG-012 1.1.1 A The full explanation of complex images is provided through the longdesc attribute (or other equivalent means). Development Front-End Development none none + + + + + +
IMG-013 1.1.1 A Images primarily conveying function use alternative text to describe their purpose, rather than what they look like. Author Content Authoring UX Design none + + + + + +
IMG-014 1.1.1 A Text alternatives of static and linked images do not replicate any information that is already being conveyed by screen reader technology. Author Content Authoring Front End Development none + + + + + +
IMG-015 1.1.1 A Text alternatives of dynamically updated images are simultaneously updated as the images change. Development Front-End Development UX Design Content Authoring + + + + + +
IMG-016 1.1.1 A Alternate means of accessing CAPTCHA information are provided, such as audio CAPTCHA, logical question, or other equivalent means. Design Visual Design UX Design Business Analyst + + + + + +
IMG-017 1.1.1 A Images which do not convey information are defined as decorative. Author Content Authoring Visual Design
UX Design
none + + + + + +
IMG-018 1.1.1 A Charts, graphs, infographics and other visual representations of information don't rely on color alone to convey information. Design Visual Design UX Designer none + + + + + +
IMG-019 1.4.5 AA Text content that conveys information is not part of images. Design Visual Design Content Authoring Front End Development + + + + + +
IMG-020 1.4.5 AA Text that is visually made to be part of an image is handled through HTML and CSS instead. Development Front-End Development Visual Design Content Authoring + + + + + +

Document Structure

ID WCAG SC Conformance Level Checkpoint Main Role Role Ownership Keep (+) / remove (-)?
Primary Secondary Contributor(s) Jenn Denis Bill Sean Lewis Michael
DOC-001 1.3.1 A Informative content is provided through HTML markup. Development Front-End Development UX Design
Content Authoring
none + + + + + +
DOC-002 1.3.1 A HTML elements are used according to the HTML specification. Development Front-End Development UX Design none + + + + + +
DOC-003 1.3.1 A Navigation groupings are marked up using HTML list or nav elements (or other equivalent means). Development Front-End Development UX Design none + + + + + +
DOC-004 1.3.1 A Header sections are marked up using HTML header elements (or other equivalent means). Development Front-End Development UX Design none + + + + + +
DOC-005 1.3.1 A The main section of a page is marked up using a HTML main element (or other equivalent means). Development Front-End Development UX Design none + + + + + +
DOC-006 1.3.1 A The footer of the page is marked up using a HTML footer element (or other equivalent means). Development Front-End Development UX Design none + + + + + +
DOC-007 1.3.1 A Content that is complementary to the main section is marked up using HTML aside elements (or other equivalent means). Development Front-End Development UX Design none + + + + + +
DOC-008 1.3.1 A HTML elements are used based on the semantics they provide, not based on what they look like. Development Front-End Development UX Design none + + + + + +
DOC-009 1.3.1 A Decorative elements are embedded through the CSS presentation. Development Front-End Development Visual Design UX Design + + + + + +
DOC-010 1.3.1 A All scripting behaviors are handled through JavaScript. Development Front-End Development none none + + + + + +
DOC-011 1.3.1 A Elements that act as headings are marked up as such. Development Front-End Development UX Design
Content Authoring
none + + + + + +
DOC-012 1.3.1 A Headings follow a hierarchical sequence without skipping any levels. Design Visual Design UX Design
Content Authoring
none + + + + + +
DOC-013 1.3.1 A Headings are marked up using h1 to h6 elements or other equivalent means. Development Front-End Development UX Design none + + + + + +
DOC-014 1.3.1 A Page contains a level 1 heading that describes the page content. Development Front-End Development UX Design
Content Authoring
none + + + + + +
DOC-015 1.3.1 A Whitespace or pre-formatted text is not used to render content to appear as multiple columns or tabular information. Development Front-End Development none none + + + + + +
DOC-016 1.3.1 A Use of native, semantic HTML elements are prioritized over other methods. Development Front-End Development UX Design none + + + + + +
DOC-017 1.3.2 A The source code (or DOM) order matches the suggested visual order of the design. Development Front-End Development Visual Design
UX Design
none + + + + + +
DOC-018 2.4.1 A Iframes displaying content are provided clear, informative title attribute values. Author Content Authoring UX Design none + + + + + +
DOC-019 2.4.2 A Page title text matches the level 1 heading text. Author Content Authoring UX Design none + + + + + +
DOC-020 2.4.2 A Pages are described using unique and descriptive page title values. Author Content Authoring none none + + + + + +
DOC-021 2.4.3 A The tab order logically and predictably follows the expected interaction order of the visual design. Development Front-End Development UX Design
Visual Design
none + + + + + +
DOC-022 2.4.6 AA Heading text meaningfully describes the content's topic or purpose. Author Content Authoring none none + + + + + +
DOC-023 2.4.6 AA The main heading of the page describes the content of the page. Author Content Authoring none none + + + + + +
DOC-024 4.1.1 A Source code is properly nested, according to its specification. Development Front-End Development none none + + + + + +
DOC-025 4.1.1 A Source code elements are provided with complete start and end tags (or are self-closed) according to specification. Development Front-End Development none none + + + + + +
DOC-026 4.1.1 A ID attribute values assigned to elements are unique. Development Front-End Development none none + + + + + +
DOC-027 4.1.1 A Elements do not contain duplicate attributes. Development Front-End Development none none + + + + + +
DOC-028 4.1.2 A Tracking or hidden Iframes are defined as such through the title attribute value. Design UX Design none Content Authoring + + + + + +
DOC-029 4.1.2 A Iframes are assigned title attribute values that describe their content. Development Front-End Development none none + + + + + +

Keyboard Access

ID WCAG SC Conformance Level Checkpoint Main Role Role Ownership Keep (+) / remove (-)?
Primary Secondary Contributor(s) Jenn Denis Bill Sean Lewis Michael
KBD-001 2.1.1 A All actionable elements can be reached, using only the keyboard. Development Front-End Development UX Design none + + + + + +
KBD-002 2.1.1 A All active elements can be triggered, using only the keyboard. Development Front-End Development UX Design none + + + + + +
KBD-003 2.1.1 A Device-specific programmatic event handlers are not used as the only way to trigger interactions. Development Front-End Development none none + + + + + +
KBD-004 2.1.1 A Programmatically scripted behaviors are planned for both hover and focus states. Design UX Design Visual Design none + + + + + +
KBD-005 2.1.1 A Keyboard focus states are planned for every active elements. Design UX Design Visual Design none + + + + + +
KBD-006 2.1.1 A Keyboard focus is not applied to non-active or static elements. Development Front-End Development UX Design none + + + + + +
KBD-007 2.1.2 A Users can navigate away from all active elements, using only the keyboard. Development Front-End Development none none + + + + + +
KBD-008 2.4.3 A Users can tab through active elements in an order that reflects the intended interaction order of the design. Development Front-End Development UX Design
Visual Design
none + + + + + +
KBD-009 2.4.3 A Tabindex attributes are not assigned positive integer values. Development Front-End Development none none + + + + + +
KBD-010 2.4.7 AA Every element that receives keyboard focus is designed to display a visible focus indicator. Design Visual Design UX Design none + + + + + +
KBD-011 2.4.7 AA Every element that receives keyboard focus displays a visible focus indicator. Development Front-End Development Visual Design none + + + + + +
KBD-012 3.2.2 A Keyboard focus does not move automatically from one form control to the next. Design UX Design Front End Development none + + + + + +
KBD-013 2.1.1 A Custom active elements replicate all inherent keyboard behaviors of native active HTML elements. Development Front-End Development UX Design none + + + + + +
KBD-014 2.1.1 A Non-interactive elements are not assigned JavaScript event handlers. Development Front-End Development none none + + + + + +

Form Interactions

ID WCAG SC Conformance Level Checkpoint Main Role Role Ownership Keep (+) / remove (-)?
Primary Secondary Contributor(s) Jenn Denis Bill Sean Lewis Michael Julianna
FRM-001 1.3.1 A Text labels are marked up using the label element or other equivalent means. Development Front-End Development none none + + + + + + +
FRM-002 1.3.1 A Text labels and form controls are programmatically associated (using the FOR and ID attributes, or equivalent means). Development Front-End Development none none + + + + + + +
FRM-003 1.3.1 A Submit buttons in forms rely on a submit input type, a button element, or other equivalent means. Development Front-End Development none none + + + + + + +
FRM-004 3.3.2 A Radio buttons and checkbox labels are positioned to the right of their respective form controls (for left-to-right languages). Design UX Design Visual Design none + + + + + + +
FRM-005 1.3.1 A Related form controls are programmatically associated using fieldset and legend elements or other equivalent means. Development Front-End Development none none + + + + + + +
FRM-006 3.3.2 A Related form controls and their respective labels are grouped together visually. Design UX Design Visual Design none + + + + + + +
FRM-007 1.3.1 A Long option lists in select elements are grouped semantically (using the optgroup element, or other equivalent means). Development Front-End Development UX Design none + + + + + + +
FRM-008 1.3.1 A Common group label text is informative, meaningful and provides context for the grouping. Author Content Authoring UX Design none + + + + + + +
FRM-009 1.3.1 A Instructions and messages are programmatically conveyed to assistive technologies. Development Front-End Development none none + + + + + + +
FRM-010 3.3.2 A Instructions are in close visual proximity to their related controls. Design Visual Design UX Design none + + + + + + +
FRM-011 1.3.2 A Information that is relevant to a form does not appear after the submit button. Design UX Design Visual Design Front-End Developement + + + + + + +
FRM-012 3.2.1 A Changes of context are not initiated automatically as user interface components receive focus. Design UX Design Front-End Development none + + + + + + +
FRM-013 3.2.2 A Event handlers are not used to automatically trigger a change of context upon input that would otherwise require explicit user action unless previously communicated. Development Front-End Development UX Design none + + + + + + +
FRM-014 3.2.2 A Form interactions are not designed to include automatic changes of context upon input that would otherwise require explicit user action unless previously communicated. Design UX Design Front-End Development none + + + + + + +
FRM-015 1.3.1 A Use of native HTML controls are prioritized over other methods. Development Front-End Development none UX Design + + + + + + +
FRM-016 3.2.4 A Error messages and alerts are visually displayed across the site in a consistent manner. Design Visual Design UX Design none + + + + + + +
FRM-017 3.2.4 A Visual indicators are presented to support error messages when errors are returned. Design Visual Design UX Design none + + + + + + +
FRM-018 3.3.1 A Inline error messages are displayed next to their related form controls. Design Visual Design UX Design none + + + + + + +
FRM-019 3.3.1 A Error messages are grouped as a list at the top of the form. Design UX Design Visual Design none + + + + + + +
FRM-020 3.3.3 AA Error messages returned provide clear instructions on how to fix them. Author Content Authoring UX Design none + + + + + + +
FRM-021 3.3.3 AA Instructions on how to fix errors are provided in text, inside their corresponding label elements (or other equivalent means). Development Front-End Development UX Design Content Authoring + + + + + + +
FRM-022 2.4.3 A Keyboard focus is dynamically moved to the error message when errors are returned. Development Front-End Development UX Design none + + + + + + +
FRM-023 1.3.1 A Required fields are programmatically conveyed as such to assistive technologies. Development Front-End Development UX Design none + + + + + + +
FRM-024 3.3.2 A Form controls are coded to have persistent visual labels. Development Front-End Development UX Design Visual Design + + + + + + +
FRM-025 3.3.2 A Form controls are designed to have persistent visual labels. Design UX Design Visual Design none + + + + + + +
FRM-026 3.3.2 A Clear text-based instructions are provided on how to use the form controls. Author Content Authoring UX Design Visual Design + + + + + + +
FRM-027 3.3.2 A Instructions provided in forms are presented in a clear and unambiguous way. Design Visual Design UX Design none + + + + + + +
FRM-028 1.3.1 A Instructions on how to use forms are programmatically conveyed to assistive technologies. Development Front-End Development UX Design Content Authoring + + + + + + +
FRM-029 3.3.2 A Placeholder text is not used in lieu of regular text label elements. Design UX Design none none + + + + + + +
FRM-030 3.3.3 AA Text-based instructions are provided to help users correct errors. Design UX Design Content Authoring
Visual Design
none + + + + + + +
FRM-031 3.3.4 AA Users are provided with means to prevent and correct form errors. Design UX Design Business none + + + + + + +
FRM-032 3.3.4 AA When legal, financial, or data information is involved, confirmation screens are provided prior to any final form submission. Design UX Design Business Front-End Development + + + + + + +
FRM-033 2.4.6 AA The purpose of the form control is clearly described in text. Author Content Authoring UX Design none + + + + + + +

CSS Presentation

ID WCAG SC Conformance Level Checkoint Main Role Role Ownership Keep (+) / remove (-)?
Primary Secondary Contributor(s) Jenn Denis Bill Sean Lewis Michael
CSS-001 1.1.1 A Icon fonts used to convey information are provided with a text equivalent. Design UX Design Content Authoring none + + + + + +
CSS-002 1.1.1 A The meaning of icon fonts is available through HTML or a programmatic equivalent such as the aria-label attribute. Development Front-End Development none none + + + + + +
CSS-003 1.1.1 A Icon fonts used to convey information are hidden from assistive technologies using the aria-hidden attribute (or other equivalent means). Development Front-End Development none none + + + + + +
CSS-004 1.1.1 A Background images are embedded for decorative purposes only. Development Front-End Development UX Design
Visual Design
none + + + + + +
CSS-005 1.3.1 A CSS pseudo-selectors such as :before and :after are not used to integrate informative content. Development Front-End Development none none + + + + + +
CSS-006 1.3.3 A Shape and location are never used as the only way to convey information and relationships between page components. Design Visual Design UX Design none + + + + +
CSS-007 1.3.3 A Users relying High Contrast themes don't lose information as a result of doing so. Development Front-End Development none none + + + + + +
CSS-008 1.4.1 A Color is never used as the only way to convey information, context, indicate selection or the presence of errors. Design Visual Design UX Design none + + + + + +
CSS-009 1.4.1 A Link text color is sufficiently contrasted by providing a luminosity ratio of at least 3:1 against its surrounding text. Design Visual Design none none + + + + + +
CSS-011 1.4.3 AA Regular-sized text is sufficiently contrasted against its background, with a ratio of at least 4.5:1. Design Visual Design none none + + + + + +
CSS-012 1.4.3 AA Large-sized text is sufficiently contrasted against its background, with a ratio of at least 3:1. Design Visual Design none none + + + + + +
CSS-013 1.4.4 AA Users can resize the text on the page up to 200% without any loss of content or functionality. Design UX Design Front End Development Visual Design + + + + + +
CSS-015 1.4.4 AA CSS techniques are used to ensure that content doesn't overflow, overlap or get truncated as a result of increasing the text size. Development Front-End Development UX Design Visual Design + + + + + +
CSS-016 1.4.5 AA CSS background sprites don't include images of text, unless equivalent text alternatives are also provided as part of the HTML. Development Front-End Development Content Authoring none + + + + + +
CSS-017 2.4.7 AA The CSS outline property of objects that receive keyboard focus are not set to zero or none. Development Front-End Development none none + + + + + +

Navigation

ID WCAG SC Conformance Level Checkoint Main Role Role Ownership Keep (+) / remove (-)?
Primary Secondary Contributor(s) Jenn Denis Bill Sean Lewis Michael
NAV-001 1.3.1 A Active objects and other calls to action are visually identifiable as such. Design Visual Design none none + + + + + +
NAV-002 1.3.3 A Instructions are conveyed through more than shape, size, position, or sound alone. Author Content Authoring UX Design none + + + + +
NAV-003 1.4.1 A Additional visual and/or textual cues are provided when color is used to convey information. Design UX Design Visual Design
Content Authoring
none + + + + + +
NAV-004 2.2.1 A Users are notified when time limits are about to expire. Design UX Design Business none + + + + + +
NAV-005 2.2.1 A Options to extend, or even turn off time limits are provided. Design UX Design Business none + + + + + +
NAV-006 2.2.2 A Users are given means to pause, stop or hide content that automatically updates. Design UX Design Visual Design none + + + + + +
NAV-007 2.2.4 AAA Users are provided with means to turn off all updates, except in case of emergencies. Design UX Design none none + + + + + +
NAV-008 2.2.5 AAA Users are provided with means to re-authenticate sessions without loss of data. Design UX Design none none + + + + + +
NAV-009 2.4.1 A Users can bypass blocks of content using skip links or similar mechanisms. Design UX Design none none + + + + + +
NAV-010 2.4.1 A Skip links and similar mechanisms are provided at the most effective location in the interface (such as the very first tab stop for a skip to main content link). Design UX Design none Content Authoring + + + + + +
NAV-011 2.4.1 A The functionality and expected destination of skip links and similar mechanisms is clearly defined. Design UX Design Content Authoring none + + + + + +
NAV-012 2.4.1 A Skip links and similar mechanisms point to the expected destination. Development Front-End Development none none + + + + + +
NAV-013 2.4.3 A All active elements receive focus in a logical and predictable order that is prescribed by the visual presentation. Development Front-End Development none UX Design, Visual Design + + + + + +
NAV-014 2.4.3 A A logical and predictable focus order is defined for complex interactions. Design UX Design none none + + + + + +
NAV-015 2.4.3 A Objects that are not actionable are not part of the tabbing order. Development Front-End Development UX Design none + + + + + +
NAV-016 2.4.3 A Focus is sent back to the initiating point when modal dialogs and controls are dismissed. Development Front-End Development UX Design none + + + + + +
NAV-017 2.4.3 A Event handlers do not unexpectedly send the focus somewhere else on the page. Development Front-End Development none none + + + + + +
NAV-018 2.4.4 A Link text and alternate text for images, when used as links describe the destination or purpose of the link. Author Content Authoring none none + + + + + +
NAV-019 2.4.4 A Links are marked up using the anchor element and have a valid href attribute value (or use other equivalent means). Development Front-End Development none none + + + + + +
NAV-020 3.2.4 AA Users can consistently distinguish between links internal to a page and links going to different locations. Design Visual Design none none + + + + + +
NAV-021 3.2.5 AAA Links that open new windows visually indicate they will do so. Design UX Design Visual Design none + + + + + +
NAV-022 3.2.5 AAA Links that open new windows programmatically declare they will do so in text. Development Front-End Development Content Authoring none + + + + + +
NAV-023 2.4.5 AA Multiple mechanisms are provided for wayfinding, such as navigation menus, breadcrumbs, search features, site map, progress bar, steps, etc. Design UX Design none none + + + + + +
NAV-024 2.4.8 AAA Indications are provided to help users identify their current location within the site. Design Visual Design UX Design none + + + + + +
NAV-025 3.2.1 A Setting the focus to a new element doesn't automatically trigger a context change, such as content updates or the opening of new windows. Design UX Design Front-End Development none + + + + + +
NAV-026 3.2.2 A Interacting with input controls or other equivalent elements doesn't automatically trigger a change of context, unless the user has been notified ahead of time. Development Front-End Development none none + + + + + +
NAV-027 3.2.3 AA Navigation mechanisms are repeated consistently throughout the site or application in the same relative order. Design UX Design Visual Design none + + + + + +
NAV-028 3.2.4 AA Navigational graphics and icons used throughout the site or application are designed to always serve the same function and or meaning. Design Visual Design UX Design none + + + + + +
NAV-029 3.2.4 AA The accessible name of user interface components used across the site or application are defined consistently. Author Content Authoring UX Design none + + + + + +

Data Tables

ID WCAG SC Conformance Level Checkpoint Main Role Role Ownership Keep (+) / remove (-)?
Primary Secondary Contributor(s) Jenn Denis Bill Sean Michael
TAB-001 1.3.1 A Tables are only to be used to lay out tabular information or data. Development Front-End Development UX Design none + + + + +
TAB-002 1.3.1 A Table row and/or column headers provide context for data within the table. Design UX Design none none + + + + +
TAB-003 1.3.1 A Data table structure is appropriate for the data being included. Design UX Design none none + + + + +
TAB-004 1.3.1 A Tabular data and corresponding header cells for that data are part of the same table. Development Front-End Development UX Design none + + + + +
TAB-005 1.3.1 A Header cell rows are marked up using THEAD elements. Development Front-End Development none none + + + + +
TAB-006 1.3.1 A Header cells are marked up using TH elements. Development Front-End Development none none + + + + +
TAB-007 1.3.1 A The relationship between table header rows and table header columns with data cells in simple data tables is provided through the SCOPE attributes. Development Front-End Development UX Design none + + + + +
TAB-008 1.3.1 A The relationship between table header rows and table header columns with data cells in complex data tables is provided through the HEADERS and ID attributes. Development Front-End Development UX Design none + + + + +
TAB-009 1.3.1 A Caption elements are used to associate caption information with data tables. Development Front-End Development none none + + + + +
TAB-010 1.3.1 A Large, complex data tables are broken into smaller, simpler data tables (when possible). Design UX Design Visual Design
Content Authoring
none + + + + +
TAB-011 1.3.1 A Unrelated data is not included in the same data table. Design UX Design Visual Design none + + + + +
TAB-012 1.3.1 A Tables are not used for layout purposes. Development Front-End Development none none + + + + +
TAB-013 1.3.1 A Tables are not used to layout lists. Development Front-End Development none none + + + + +
TAB-014 1.3.1 A Caption elements, aria-labelledby attributes or other equivalent means are used to explain the structure of data tables. Development Front-End Development none none + + + + +
TAB-015 1.3.1 A A meaningful description of the structure of data tables is provided. Design Content Authoring UX Design Visual Design + + + + +
TAB-016 1.3.2 A The footer information of the table comes after the main content in the source order. Design UX Design Front-End Development none + + + + +
TAB-017 2.4.6 AA All data table header cells are identified. Design UX Design Front-End Development none + + + + +

Multimedia

ID WCAG SC Conformance Level Checkpoint Main Role Role Ownership Keep (+) / remove (-)?
Primary Secondary Contributor(s) Jenn Denis Bill Sean Michael
MMD-001 1.2.1 A Text transcripts are provided for prerecorded audio files. Author Content Authoring UX Design none + + + + +
MMD-002 1.2.1 A Text transcripts are provided for prerecorded video-only files. Author Content Authoring UX Design none + + + + +
MMD-003 1.2.1 A Links to transcript files are provided in close proximity to the audio files. Design UX Design Visual Design none + + + + +
MMD-004 1.2.1 A The relationship between multimedia files and their associated transcript is clearly communicated through content sequence or focus order. Development Front-End Developer UX Design none + + + + +
MMD-005 1.2.3 A Text transcripts report all significant information from the audio track. Author Content Authoring none none + + + + +
MMD-006 1.2.1 A Copy on the page identifies when video content has no sound. Design UX Design Content Authoring none + + + + +
MMD-007 1.2.1 A Adjacent links for further information about the multimedia file are provided, when appropriate. Design UX Design none none + + + + +
MMD-008 1.2.2 A Synchronized captions are provided for all prerecorded video content. Author Content Authoring UX Design none + + + + +
MMD-009 1.2.2 A Captions are not skipping dialogues or important sounds. Author Content Authoring none none + + + + +
MMD-010 1.2.2 A Multimedia player controls are provided to turn captions on or off. Design UX Design none none + + + + +
MMD-011 1.2.3 A Text transcripts or audiodescription report all significant information from the visual track. Author Content Authoring none none + + + + +
MMD-012 1.2.4 AA Synchronized captions are provided for all live video content. Author Content Authoring none none + + + + +
MMD-013 1.2.4 AA Captions for live audio content are generated using real-time text transcription services. Author Content Authoring UX Design none + + + + +
MMD-014 1.2.5 AA Prerecorded videos have audiodescription that captures all significant information from the visual track. Author Content Authoring none none + + + + +
MMD-015 1.2.5 AA Controls to toggle audiodescription features are provided as part of the media player controls. Design UX Design none none + + + + +
MMD-016 1.2.5 AA Multimedia player controls are provided to access a version of the video with audio description. Design UX Design none none + + + + +
MMD-017 1.2.6 AAA Sign language interpretation is provided for all prerecorded audio content in synchronized media. Author Content Authoring UX Design none + + + + +
MMD-018 1.2.7 AAA Extended audio description is provided for all prerecorded synchronized video content when pauses in foreground audio are insufficient to allow audio descriptions to convey the sense of the video. Author Content Authoring UX Design none + + + + +
MMD-019 1.2.8 AAA Text alternatives are provided for all prerecorded audio and video files. Author Content Authoring UX Design none + + + + +
MMD-020 1.2.8 AAA Brief descriptions summarizing multimedia content are provided in close proximity to the audio and video files. Author UX Design Content Authoring none + + + + +
MMD-021 1.2.9 AAA Live transcripts are provided for all audio content happening in real-time. Author Content AuthoringAuthoring UX Design none + + + + +
MMD-022 1.4.2 A Multimedia player controls are provided to turn sound on and off. Design UX Design none none + + + + +
MMD-023 1.4.2 A Volume controls for page-level multimedia files are independent from general computer audio controls. Development Front-End Developer UX Design none + + + + +
MMD-024 1.4.2 A Volume controls for page-level multimedia files are visually located at the top of the page. Design UX Design none none + + + + +
MMD-025 1.4.2 A Audio content that automatically starts on page load lasts no longer than 3 seconds. Development Front-End Developer UX Design none + + + + +
MMD-026 1.4.2 A Prerecorded or live video content is not set to auto-play. Design UX Design none none + + + + +
MMD-027 2.1.1 A Multimedia player controls can be fully operated using only the keyboard. Development Front-End Developer UX Design none + + + + +
MMD-028 2.2.2 A Multimedia player controls are provided to pause or play the multimedia file. Design UX Design Visual Design none + + + + +
MMD-029 4.1.2 A Information conveyed by multimedia player controls are programmatically announced through assistive technologies. Development Front-End Developer UX Design none + + + + +


Static Content

Width is no more than 80 characters or glyphs (40 if CJK). Line spacing (leading) is at least space-and-a-half within paragraphs, and paragraph spacing is at least 1.5 times larger than the line spacing. Text can be resized without assistive technology up to 200 percent in a way that does not require the user to scroll horizontally to read a line of text on a full-screen window.
ID WCAG SC Conformance Level Checkpoint Main Role Role Ownership Keep (+) / remove (-)?
Primary Secondary Contributor(s) Jenn Denis Bill Sean Michael Julianna
SCT-001 1.1.1 A Emoticons, emojis, ASCII art, and other non-markup language constructs are supported with equivalent text alternatives and conveyed to assistive technologies. Design UX Design Content Authoring Front-End Development + + + + + +
SCT-002 1.3.1 A Emoticons, emojis, ASCII art, and other non-markup language constructs are not used as the only way to structure content or convey information. Design UX Design Front-End Development none + + + + + +
SCT-003 1.3.1 A Proper markup is used to render emphasized, bolded text and other stylistic or presentational effects. Development Front-End Development none none + + + + + +
SCT-004 1.3.1 A Proper markup is used to structure quotes, blockquotes and citations. Development Front-End Development none Content Authoring + + + + + +
SCT-005 1.3.1 A Heading markup is only used for text which acts as a section heading. Development Front-End Development UX Design none + + + + + +
SCT-006 1.3.1 A Heading markup is not used for formatting effects. Development Front-End Development none none + + + + + +
SCT-007 1.3.1 A The headings used in a page provide a logical outline for the document. Author Content Author UX Design none + + + + + +
SCT-008 1.3.2 A The intended reading order of the content remains logical when CSS and images are turned off. Development Front-End Development UX Design
Visual Design
none + + + + + +
SCT-009 1.3.2 A The source code order reflects the intended reading order of the document. Development Front-End Development none none + + + + + +
SCT-010 1.3.3 A Site supports internationalization with multiple languages, including right-to-left languages. Development Business Analysis UX Design
Content Authoring
none + + + ? + +
SCT-011 1.3.3 A Text direction is properly marked up as such, especially for right-to-left languages. Development Front-End Development none none + + + ? + +
SCT-012 1.3.3 A Objects that rely on shape to be properly perceived are supported with additional text information. Design UX Design Visual Design Content Authoring + + + ? + +
SCT-013 1.3.3 A Objects that rely on size to be properly perceived are supported with additional text information. Design UX Design Visual Design Content Authoring + + + ? + +
SCT-014 1.3.3 A Objects that rely on visual location to be properly perceived are supported with additional text information. Design UX Design Visual Design Content Authoring + + + ? + +
SCT-015 1.3.3 A Objects that rely on orientation to be properly perceived are supported with additional text information. Design UX Design Visual Design Content Authoring + + + ? + +
SCT-016 1.3.3 A Objects that rely on sound to be properly perceived are supported with additional text information. Design UX Design none Content Authoring + + + ? + +
SCT-017 1.4.5 AA Mathematical formulas are marked up using MathML. Development Front-End Development Content Authoring none + + + + + +
SCT-018 1.4.8 AAA Text content in design assets is left-aligned in left-to-right languages. Design Visual Design none Ux Design + + + + + +
SCT-019 1.4.8 AAA Fully justified text can easily be changed to ragged right text with a simple action. Design UX Designer Front-End Development none + + + + + +
SCT-019 3.1.1 A The primary language used in the document is properly identified using the lang attribute. Development Front-End Development + +
SCT-020 3.1.2 AA Changes in natural language are programatically identified as such. Development Front-End Development Content Authoring + +
SCT-021 3.1.3 AAA Unusual words, phrases and abbreviations are organized into a glossary. Design UX Design? Content Authoring?
(or vice versa?)
Content first, UX second +
SCT-022 3.1.3 AAA Unusual words found in content link to their definition in a glossary. Development Front-End Development Content Authoring + +
SCT-023 3.1.4 AAA Abbreviations are programmatically associated with their definition. Development Front-End Development Content Authoring + +
SCT-024 3.1.5 AAA Complex or hard to understand content is supported by an easy-to-understand text summary. Author Content Authoring + +
SCT-025 3.1.5 AAA Ideas conveyed through text are supported with illustrations and other visuals. Author Content Authoring UX Design Content first, Visual second +
SCT-026 3.1.5 AAA Content is displayed and structured in a way that makes it easier to read. Design Visual Design UX Design + +
SCT-027 3.1.6 AAA Ambiguous words are supported by a mechanism that helps users identify their specific pronunciation. Development Front-End Development UX Design? + +
UX to specify technique(s)?

Dynamic Interactions

ID WCAG SC Conformance Level Checkpoint Main Role Role Ownership Keep (+) / remove (-)?
Primary Secondary Contributor(s) Jenn Denis Bill Sean Michael Julianna
DCT-001
DCT-002
DCT-003
DCT-004
DCT-005
DCT-006
DCT-007
DCT-008
DCT-009
DCT-010
DCT-011
DCT-012
DCT-013
DCT-014
DCT-015
DCT-016
DCT-017
DCT-018
DCT-019
DCT-020
DCT-021
DCT-022
DCT-023
DCT-024
DCT-025

Automated Considerations

This is the current set of checkpoints covered in axe-core... not sure we can or even want to use this list. Or if we can add to it, with other open-sourced tools (like maybe SiteImprove)

  1. <blink> elements are deprecated and must not be used
  2. <dl> elements must only directly contain properly-ordered <dt> and <dd> groups, <script>, or <template> elements
  3. <dt> and <dd> elements must be contained by a <dl>
  4. <html> element must have a lang attribute
  5. <html> element must have a valid value for the lang attribute
  6. <html> elements with lang and xml:lang must have the same base language
  7. <li> elements must be contained in a <ul> or <ol>
  8. <marquee> elements are deprecated and must not be used
  9. <object> elements must have alternate text
  10. <ul> and <ol> must only directly contain <li>, <script> or <template> elements
  11. <video> elements must have a <track> for captions
  12. accesskey attribute value must be unique
  13. Active <area> elements must have alternate text
  14. All <th> elements and elements with role="columnheader" or role="rowheader" must have data cells they describe
  15. All cells in a <table> element that use the headers attribute must only refer to other cells of that same <table>
  16. All non-empty <td> elements in tables larger than 3 by 3 must have an associated table header
  17. All page content must be contained by landmarks
  18. ARIA attributes must conform to valid names
  19. ARIA attributes must conform to valid values
  20. ARIA buttons, links, and menuitems must have an accessible name
  21. ARIA dialog must have an accessible name
  22. ARIA input fields must have an accessible name
  23. ARIA meter must have an accessible name
  24. ARIA progressbar must have an accessible name
  25. ARIA role must be appropriate for the element
  26. ARIA roles used must conform to valid values
  27. ARIA toggle fields have an accessible name
  28. ARIA tooltip must have an accessible name
  29. ARIA treeitem must have an accessible name
  30. aria-hidden elements do not contain focusable elements
  31. aria-hidden="true" must not be present on the document <body>
  32. Audio must have controls that provide users with the ability to stop automatically played audio after three seconds
  33. Autocomplete attribute must be used correctly
  34. Banner landmark must not be contained in another landmark
  35. Bold, italic text and font-size are not used to style <p> elements as a heading
  36. Buttons must have programmatically determinable text
  37. Certain ARIA roles must be contained by particular parent elements
  38. Certain ARIA roles must contain particular children
  39. Complementary landmarks and/or asides are top level
  40. Contentinfo landmark must not be contained in another landmark
  41. CSS Media queries are not used to lock display orientation
  42. Data or header cells should not be used to give caption to a data table
  43. Documents must contain a title element to aid in navigation
  44. Elements containing role="img" have an alternative text
  45. Elements in the focus order need a role appropriate for interactive content
  46. Elements must only use allowed ARIA attributes
  47. Elements should not have tabindex greater than zero
  48. Elements whose role is none or presentation must not conflict with other roles
  49. Elements with role="text" must not have focusable descendants.
  50. Ensure that links with the same accessible name serve a similar purpose
  51. Ensure that scrollable region has keyboard access
  52. Ensures the document has at most one main landmark
  53. Form <input> elements must have labels
  54. Form <input> elements should have a visible label
  55. Form fields do not have duplicate labels
  56. Frame focusable content
  57. Frames must be tested with axe-core
  58. Frames must have a unique title attribute
  59. Frames must have title attribute
  60. Heading levels should only increase by one
  61. Headings must not be empty
  62. Hidden content on the page cannot be analyzed
  63. ID attribute value must be unique
  64. ID attribute values must be unique
  65. IDs used in ARIA and labels must be unique
  66. Image buttons must have alternate text
  67. Images must have alternate text
  68. Inline text spacing must be adjustable with custom stylesheets
  69. Input buttons must have programmatically determinable text
  70. Interactive controls must not have focusable descendants.
  71. Label and name from content mismatch
  72. Landmarks must have a unique role or role/label/title (i.e. accessible name) combination
  73. lang attribute must have a valid value
  74. Links must be distinguished from surrounding text in a way that does not rely on color
  75. Links must have programmatically determinable text
  76. Main landmark must not be contained in another landmark
  77. Page must contain a level-one heading
  78. Page must have means to bypass repeated blocks
  79. Page must have one main landmark
  80. Page must not have more than one banner landmark
  81. Page must not have more than one contentinfo landmark
  82. Required ARIA attributes must be provided
  83. Scope attribute should be used correctly on tables
  84. select element must have an accessible name
  85. Server-side image maps must not be used
  86. SVG images and graphics require accessible text
  87. Table header elements must have visible text that clearly describes the purpose for screen reader users.
  88. Text elements must have sufficient color contrast against the background
  89. Text of buttons and links should not be repeated in the image alternative
  90. The <caption> element should not contain the same text as the summary attribute
  91. The skip-link target should exist and be focusable
  92. Timed refresh must not exist
  93. Use aria-roledescription on elements with a semantic role
  94. Users should be able to zoom and scale the text up to 500%
  95. Zooming and scaling must not be disabled