WCAG 2.2 Accessibility Checklist

1. Structure and Semantics

The page <title> MUST be present and MUST contain text. (WCAG 2.4.2) [cite: 23] The primary language of the page MUST be identified accurately, using a standard language code, on the <html> element (e.g. <html lang="en">). (WCAG 3.1.1) [cite: 26] Text that acts as a heading visually or structurally MUST be designated as a true heading (<h1>, <h2>, etc.) in the markup. (WCAG 1.3.1) [cite: 28] Headings SHOULD NOT skip hierarchical levels. (Best practice) [cite: 29] Landmarks are an effective way to bypass blocks of content, as required by WCAG 2.4.1. (WCAG 2.4.1) [cite: 31] Lists MUST be constructed using the appropriate semantic markup (i.e. <ul> or <ol> with <li> child elements, or <dl> with <dt> and <dd> child elements). (WCAG 1.3.1) [cite: 33] Table headers MUST be designated with <th>. (WCAG 1.3.1) [cite: 36] The iframe title attribute (on the parent page) MUST be accurate and descriptive. (WCAG 2.4.1) [cite: 39]

2. Links and Navigation

Links MUST be semantically designated as such (ideally using an <a> element with a valid `href` value). (WCAG 4.1.2) [cite: 48] The purpose of each link MUST be understandable and distinguishable from other links on the same page. (WCAG 2.4.4) [cite: 48] Links MUST be keyboard-focusable. (WCAG 2.1.1) [cite: 48] The navigation order of focusable elements (links, form elements, etc.) MUST be logical and intuitive. (WCAG 2.4.3) [cite: 51] All links MUST show a visual focus indicator when in focus. (WCAG 2.4.7) [cite: 51] Multiple ways must be available to find other web pages on the site (at least two of: related pages list, table of contents, site map, site search, or list of all available web pages). (WCAG 2.4.5) [cite: 56]

3. Images and Visual Design

Meaningful images MUST have alternative text that accurately conveys the purpose of the image. (WCAG 1.1.1) [cite: 65] Decorative images SHOULD be given null (empty) alternative text (`alt=""`) or handled with CSS. (Best practice) [cite: 65] Any information conveyed by color MUST be accompanied by a programmatically discernible text alternative. (WCAG 1.4.1) [cite: 71] Small text (under 18 point regular font or 14 point bold font) MUST have a contrast ratio of at least 4.5 to 1 with the background. (WCAG 1.4.3) [cite: 71] The page MUST allow users to zoom in on mobile devices (e.g., `` is NOT allowed). (WCAG 1.4.4) [cite: 74] Content MUST NOT rely solely on visual characteristics such as shape, size, visual location, or orientation to convey meaning. (WCAG 1.3.3) [cite: 80]

4. Multimedia, Animations, and Motion

Prerecorded audio-only content MUST have a transcript of dialog, narration, and other meaningful sounds. (WCAG 1.2.1) [cite: 85] A method MUST be provided to pause, stop, or hide any media content that begins playing automatically and which lasts 5 seconds or more. (WCAG 2.2.2) [cite: 85] Prerecorded multimedia content MUST have synchronized captions. (WCAG 1.2.2) [cite: 86] A page MUST NOT contain content that flashes more than 3 times per second unless sufficiently small and low contrast. (WCAG 2.3.1) [cite: 96] A method MUST be provided to allow users to control time limits by turning them off, adjusting them, or extending them. (WCAG 2.2.1) [cite: 96]

5. User Input, Forms, and Dynamic Content

Links, buttons, and interactive controls MUST be keyboard-focusable. (WCAG 2.1.1) [cite: 99] Keyboard focus MUST NOT be locked or trapped in a particular page element. (WCAG 2.1.2) [cite: 99] The size of the target for pointer inputs MUST be at least 24 by 24 CSS pixels (with some allowable exceptions). (WCAG 2.5.8) [cite: 102] Labels MUST be programmatically associated with their corresponding form elements. (WCAG 1.3.1) [cite: 111] Placeholder text is allowed but MUST NOT be used as the only method of providing a label for a text input. (WCAG 1.3.1) [cite: 111] If an input error is automatically detected, the item that is in error is identified and the error is described to the user in text. (WCAG 3.3.1) [cite: 129] When a user inputs information or interacts with a control, it MUST 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. (WCAG 3.2.2) [cite: 135] Every interactive UI element MUST have a name, according to the accessible name computation. (WCAG 4.1.2) [cite: 138] If the CAPTCHA is not text-based (e.g. image or audio), a text alternative MUST communicate the purpose of the CAPTCHA. (WCAG 1.1.1) [cite: 151]

Consult the Full WCAG 2.2 Checklist:

This tool presents a subset of the comprehensive guidelines. For a thorough and complete accessibility audit against WCAG 2.2 AA standards, please refer to the original source document:

Official WCAG Standards & Guidelines (W3C)

The provided PDF document "web-accessibility-checklist-wcag-2.2.pdf" offers a detailed, actionable checklist based on these standards.

Contribute to this project!

Feel free to fork this project and implement new features or improvements.

GitHub Repository

-- Stars -- Forks