ADA Accessible Website Guidelines: A Practical 2026 Checklist For Compliance And Better UX

You run a business site and wonder whether the ADA reaches it. Yes: the Department of Justice applies the ADA to web offerings, so ADA accessible website guidelines matter, though no regulation sets one detailed technical standard.

For the wider picture of accessible design, see our digital accessibility guide. This page stays on the legal context and a checklist where every item has a test.

Common misconceptions about the ADA and websites

The ADA does not stop at the front door. ADA.gov’s web guidance explains that Title III prohibits discrimination against people with disabilities by businesses open to the public. It also says the Department of Justice has consistently taken the position that the ADA’s requirements apply to the goods and services a business offers on the web. If customers use your site to browse, book, buy or get support, treat it as part of the service you must make accessible.

The confusion usually comes from three places: the ADA’s building standards, the lack of a named web rule, and the overlap with Section 508. The table sorts them out.

Figures and scope statements above come from ADA.gov web guidance and the U.S. Access Board’s ADA page.

Choosing a WCAG level

Aim for WCAG 2.2 Level AA. That is a practical recommendation, not a legal safe harbor, because DOJ leaves the choice of method to each organization. Two pieces of evidence support the target.

• A public-sector signal. The University of Wisconsin–Madison explains that, for its 2024 ADA rule, WCAG 2.1 Level AA is the endorsed technical standard and that a higher standard such as WCAG 2.2 or 3.0 can be used. Its digital tools must be accessible by April 26, 2027. That deadline applies to the university, not to your business, but it shows where public institutions are heading.
• A complete testing aid. Cornell’s WCAG 2.2 checklist lists all Level A and AA success criteria, so building to 2.2 AA gives you a full list to test against.

If your organization is a federal agency, the Section 508 guide to accessible web design recaps the WCAG requirements that federal websites need to meet the Revised 508 Standards. Everyone else can use it as a plain-language cross-check of the thresholds below.

WCAG 2.2 and the POUR principles

WCAG 2.2 is not tied to one technology. Cornell notes that its guidelines cover a broad range of web content, so the same criteria apply to a plain HTML page, a single-page app or a form builder. Cornell also lists a related guide titled Constructing a P.O.U.R. Website. POUR stands for Perceivable, Operable, Understandable and Robust, and it is a useful way to sort your fixes.

• Perceivable. Alt text, captions and text contrast sit here: people must be able to take in the content.
• Operable. Keyboard navigation and control of moving or flashing content sit here: people must be able to use the interface without a mouse.
• Understandable. Clear form labels and error indicators sit here: people must know what a control asks of them.
• Robust. Controls must expose a name and role that assistive technology can read, which depends on clean markup.

Sorting findings this way helps assign owners: designers usually own contrast, developers own markup and keyboard behavior, and editors own alt text and captions.

Highest-impact fixes first

Start with the barriers the Department of Justice itself lists. ADA.gov’s examples of website accessibility barriers include poor color contrast, missing alt text, no captions on videos, inaccessible online forms and mouse-only navigation. These fixes suit almost every site and are easy to verify.

• Text alternatives on images. Images without alt text leave blind users without the content or purpose of the image. Our guide, What Is Image Alt Text? A Practical Guide to Writing Alt Text for Accessibility and SEO (2026) – Internetbuttons, covers how to write useful descriptions.
• Captions on video. Videos without captions block people with hearing disabilities, so caption anything with speech before you publish it.
• Keyboard navigation. People who cannot use a mouse cannot reach content if the site cannot be navigated by keyboard. Fix this on menus, dialogs and checkout steps first.
• Form labels and errors. Forms need labels that screen readers can convey, along with error indicators. A form people cannot complete is a lost sale or a missed service request.
• Color contrast. Poor contrast is a one-line CSS change in many cases and the easiest barrier to check with a tool.

If time is short, handle forms and keyboard access first, because they block people from completing a task rather than just making it harder.

WCAG 2.2 AA checklist with a test method for each item

The table turns the barriers and several numeric thresholds into pass conditions you can test. Use it as acceptance criteria in tickets.

Thresholds are taken from the Section 508 accessible web design guide, and the barrier categories from ADA.gov web guidance.

Each number is a minimum or ceiling for passing, not a design target. Aim for contrast comfortably above the ratio and for no flashing at all where you can.

How to test your site

Work through the checklist page by page, starting with templates that many pages share: header, navigation, forms and checkout. Cornell describes its WCAG checklist as a testing guide and a method for recording issues, and it publishes a separate methodology covering how to test websites and web applications thoroughly.

1. Run the contrast check. Test color contrast with the WebAIM color contrast checker, as the federal accessible web design guide recommends.
2. Navigate by keyboard. Tab through each template and confirm you can reach and operate every link, button and field.
3. Listen with a screen reader. Step through a key task, such as submitting a contact form, and confirm that labels, errors, image descriptions and control names are announced.
4. Check media. Play videos with sound off for captions, and load pages to confirm autoplay audio and moving content can be controlled.
5. Log each failure. Record the page, the checklist item, the steps to reproduce and an owner. A screenshot makes the report clearer, and our guide How To Screenshot Using Your Keyboard: Fast Tricks For Windows, Mac, And Chromebooks (2026) – Internetbuttons shows the shortcuts.

If you also run an automated scanner, treat its output as a starting list and confirm each item by hand against the checklist. Repeat the checks whenever a template or component changes, so fixes do not regress.

Frequently asked questions