ADA Accessibility Checklist

Date: January 8, 2026

Purpose:
This checklist is designed to help ensure the online platform is accessible to people with disabilities, in alignment with U.S. federal ADA requirements and WCAG 2.1 AA standards (the primary benchmark used by courts and regulators).

This applies to all users, including those who use screen readers, keyboards instead of a mouse, voice controls, screen magnifiers, captions, or other assistive technologies.

1. Website Structure & Navigation

Goal: Users should be able to easily understand and move through the site.

• Pages should follow a clear, logical structure (header → main content → footer).
• Navigation menus should stay consistent across pages.
• Headings should be used correctly (H1 for page title, H2 for sections, H3 for subsections).
• Every page must have a clear, descriptive title.
• Add a “Skip to main content” link for keyboard users.
• Links should describe where they go (avoid “click here”).
• Navigation, buttons, and menus should behave the same way everywhere.
• Include search and sitemap features that are accessible.

2. Text & Written Content

Goal: Content must be readable and understandable by everyone.

• Every image, icon, or graphic must have alternative text unless decorative.
• Text must be readable when zoomed up to 200% without breaking the layout.
• Content should reflow on smaller screens without horizontal scrolling.
• Use clear, plain language where possible.
• Maintain comfortable spacing between lines and paragraphs.
• Identify the language of the page in code (and any language changes).
• Avoid flashing content that could cause seizures (more than 3 flashes per second).

3. Forms & Input Fields

Goal: Forms must be usable by screen readers and keyboard users.

• Every form field must have a visible label tied to it.
• Instructions should appear before users fill out the form.
• Error messages must explain what went wrong and how to fix it.
• Errors should not rely on color alone (e.g., red text only).
• Group related fields (like address fields) together.
• Do not clear user input when errors occur.
• Ensure a logical tab order through form fields.
• Use proper input types (email, phone, password, etc.).

4. Multimedia (Video & Audio)

Goal: Audio and video must be accessible to people who cannot see or hear them.

• Videos must include captions.
• Audio-only content must have transcripts.
• Important visual-only information must be described in audio.
• Media players must work with keyboards and screen readers.
• Users must be able to pause, stop, and control volume.
• Avoid autoplay; if used, provide an easy way to stop it.

5. Keyboard Accessibility

Goal: The entire platform must work without a mouse.

• All features must be usable using only a keyboard.
• Users must always see where their keyboard focus is.
• The focus order should follow a logical reading flow.
• No keyboard traps (users must be able to exit components).
• Provide keyboard alternatives for drag-and-drop features.

6. Color & Visual Contrast

Goal: Users with low vision or color blindness must still understand content.

• Text must have strong contrast against backgrounds.
• Buttons, links, and focus indicators must be clearly visible.
• Information cannot rely on color alone (e.g., “red means error”).
• Links should be visually distinct from regular text.
• Support high-contrast or dark mode where possible.

7. Assistive Technology Compatibility

Goal: Screen readers and other tools must correctly interpret the site.

• Use proper HTML elements before adding ARIA attributes.
• Use ARIA only when necessary and correctly.
• All buttons, inputs, and controls must have clear names and roles.
• Screen readers must be alerted to dynamic content changes.
• Modals must trap focus and announce themselves.
• Decorative images must be hidden from screen readers.
• Tables must include headers and clear relationships.

8. Motion, Timing & Safety

Goal: Avoid disorientation, seizures, or forced interactions.

• Allow users to extend or turn off time limits.
• Provide a way to reduce animations or motion effects.
• Respect system “reduce motion” preferences.
• Do not auto-refresh content without warning.

9. Responsive Design & Touch Accessibility

Goal: The platform must work across devices and screen sizes.

• Content must reflow properly on mobile and tablets.
• Do not rely on hover-only interactions.
• Touch targets should be large enough and spaced apart.
• Orientation changes should not break functionality.

10. Authentication & Security

Goal: Login and security features must be accessible.

• Support password managers.
• Allow copy/paste in login fields where possible.
• Avoid inaccessible CAPTCHAs; provide alternatives.
• Ensure multi-factor authentication is accessible.

11. Documents, Downloads & Third-Party Content

Goal: Everything users interact with must be accessible.

• PDFs and downloads must be properly tagged and readable.
• Provide accessible alternatives for older documents.
• Review third-party plugins and embeds for accessibility.
• Provide workarounds if third-party tools are not accessible.

12. Error Prevention & Confirmation

Goal: Prevent costly or irreversible mistakes.

• Allow users to review information before final submission.
• Provide confirmation screens and receipts.
• Make confirmations accessible to screen readers.

13. Consistency & Predictability

Goal: Reduce confusion and cognitive load.

• Avoid unexpected page changes.
• Keep labels and actions consistent across the platform.
• Do not auto-submit forms or redirect without warning.

14. Testing & User Feedback

Goal: Accessibility is ongoing, not one-time.

• Perform automated accessibility scans regularly.
• Conduct manual testing with keyboards and screen readers.
• Test across browsers, devices, and operating systems.
• Include users with disabilities in usability testing.
• Provide an easy way for users to report accessibility issues.
• Track and fix issues promptly.

15. Policies, Training & Maintenance

Goal: Build accessibility into operations.

• Publish an accessibility statement.
• Assign responsibility for accessibility compliance.
• Train developers, designers, and content creators.
• Build accessibility into design and QA workflows.
• Maintain records of audits and fixes.

16. Data, Charts & Complex Components

Goal: Ensure non-text data is understandable.

• Provide text summaries for charts and graphs.
• Ensure filters, tabs, carousels, and accordions are keyboard and screen-reader accessible.
• Do not hide critical information behind interactions that assistive tech cannot access.

17. Performance & Loading States

Goal: Users should understand what’s happening on screen.

• Announce loading states to screen readers.
• Avoid layout shifts that move content unexpectedly.
• Maintain focus after content updates.

18. Legal & Compliance Notes

• This checklist aligns with ADA Title III obligations.
• WCAG 2.1 AA is the current accepted standard in U.S. enforcement.
• Accessibility applies to websites, SaaS platforms, dashboards, portals, and apps.
• Compliance reduces legal risk and improves usability for all users.