Developer Accessibility Checklist

Semantics and Structure

• Add a title element that describes the page
• Add landmarks/regions to a page
• Identify the language of the page or content
• Iframes need meaningful titles
• Provide text-based clues to help users perceive content
• Use list elements for grouping content
• Use meaningful heading structure
• Use valid markup in web pages

Tables

• Add header cells to tables
• Provide a caption on tables

Forms

• Add labels to inputs and other controls
• Ensure an element's accessible name matches the visible name
• Group form inputs that relate to each other
• Indicate if a form has a required field
• Provide autofill on form inputs
• Provide clear error messages on forms

Navigation

• Add landmarks/regions to a page
• Avoid positive tabindex values
• Ensure there are no keyboard traps
• Include a skip to main content mechanism
• Interactive content must be usable by keyboard

Animation

• Avoid flashing web content
• Let users pause/stop/hide animation

Images

• Avoid images of text when possible
• Graphics used as links and buttons need accessible names
• Include alt text on images
• Name SVGs with proper semantics

Visual Design

• Avoid images of text when possible
• Don't use color alone to convey information
• Ensure text and controls have enough color contrast
• Ensure typography is readable and customizable
• Give links distinguishable visual cues
• Support forced colors modes
• Use style sheets (CSS) for spacing and styles
• Visually hide redundant text as needed

Input Methods

• Avoid positive tabindex values
• Ensure there are no keyboard traps
• Interactive content must be usable by keyboard

Links

• Ensure an element's accessible name matches the visible name
• Give links distinguishable visual cues
• Graphics used as links and buttons need accessible names
• Links should open in the same tab/window
• Provide descriptive link text
• Visually hide redundant text as needed

Responsive Design

• Ensure typography is readable and customizable
• Ensure users can zoom when viewing content
• Use responsive units over fixed units when possible

Dynamic Content

• Give users enough time to access content
• Make status messages detectable semantically

Video and Multimedia

Readability

Headings