Website ADA compliance checklist.

Screen readers cannot see images. They read the alternative text you provide, or the file name if you provide nothing.

• Every informational image has alt text that describes its meaning, not its file name.
• Decorative images use an empty alt attribute so screen readers skip them.
• Charts, graphs, and infographics have a text equivalent nearby.
• Image-only buttons and icons have an accessible name (an aria-label or visually hidden text).

Low-contrast text is the single most cited finding on small business sites.

• Body text meets a contrast ratio of at least 4.5 to 1 against its background.
• Large text (about 24px, or 19px bold) meets at least 3 to 1.
• Color is never the only way information is conveyed (for example, a required field is marked with text, not just red).
• Buttons, form borders, and focus indicators meet 3 to 1 against adjacent colors.

Many users navigate with a keyboard only. If they cannot reach or operate something, it fails.

• Every interactive element (links, buttons, menus, form fields) is reachable and operable with the keyboard alone.
• The focus indicator is always visible as you tab through the page.
• There are no keyboard traps where focus gets stuck inside a widget.
• A skip link lets keyboard users jump past the navigation to the main content.

An inaccessible form, especially a checkout or contact form, is one of the strongest claims a plaintiff can make.

• Every input has a programmatic label, not just placeholder text.
• Error messages are announced to screen readers and tied to the field they describe.
• Required fields and input formats are explained in text.
• Related controls (such as a group of radio buttons) are grouped with a fieldset and legend.

Assistive technology relies on real structure to let users move around the page.

• Headings follow a logical order (one h1, then h2, then h3) and are not skipped for visual styling.
• Pages use semantic landmarks (header, nav, main, footer) so users can jump between regions.
• Lists are marked up as lists, and tables use real table markup with header cells.
• The page has a descriptive, unique title.

Users who navigate by links or buttons need each one to make sense on its own.

• Every link and button has discernible text; no empty links or icon-only controls without a name.
• Link text describes the destination (avoid repeated bare Read more links).
• There is more than one way to find a page (navigation, search, or a sitemap).
• The language of the page is set so screen readers use the right pronunciation.

Modern sites paint menus, modals, and carousels with JavaScript, which is where many failures hide.

• Modals and pop-ups move focus in on open and return it on close.
• Custom widgets (dropdowns, tabs, carousels) use correct ARIA roles and the attributes those roles require.
• Content that updates without a page reload announces itself to assistive technology.
• Motion respects the user's reduced-motion preference.

Compliance is not a one-time project. Sites change, and new content reintroduces old problems.

• PDFs that matter (menus, intake forms, case studies) are tagged and readable, or an accessible alternative is offered.
• Video has captions and audio has a transcript where needed.
• You publish an accessibility statement with a working contact channel.
• You re-check the site on a schedule, because theme updates and new apps introduce new barriers.