Estimate Project

ADA compliant website design: what it takes, how to check it, and what it costs

Summarize with ChatGPTSummarize with Perplexity
Two hands fit puzzle pieces with an eye, an ear, a keyboard and a document around a web page, with a magnifier over the letters Aa

ADA compliant website design means designing a site that people with disabilities can use with a keyboard, a screen reader, or zoom. The ADA sets no technical checklist for business websites, so teams design to the Web Content Accessibility Guidelines (WCAG), and we recommend version 2.2 at Level AA. At Ronas IT, a UX audit with a WCAG check starts from $500, and website design starts from $800 for a landing page and from $1,500 for a corporate site. The estimate states the target level and the pages to check, and development is priced separately.

Most popular websites do not meet WCAG yet. In the 2026 WebAIM Million report, automated tests found WCAG failures on 95.9% of the top one million home pages, with 56.1 errors per page on average. Five of the six most common error types come from choices a design can specify: text contrast, image descriptions, form field labels, link names, and button names.

What the ADA requires from a website

The Department of Justice has long held that the ADA's requirements cover the goods and services a business open to the public provides, including those on the web. For these businesses, the Department says it “does not have a regulation setting out detailed standards” and names WCAG and the federal Section 508 standards as helpful guidance. State and local governments have a detailed rule that names WCAG 2.1 at Level AA, summarized in a Justice Department fact sheet.

Who you areWhat appliesTechnical standardCompliance date
A business open to the public, such as a store, bank, clinic, or hotelTitle III of the ADANone set; WCAG and Section 508 as guidanceAlready applies
A state or local government of 50,000 people or moreTitle II web ruleWCAG 2.1 Level AAApril 26, 2027
A smaller state or local government, or a special districtTitle II web ruleWCAG 2.1 Level AAApril 26, 2028
A company that runs a website or app for a state or local governmentTitle II web rule, through the government it works forWCAG 2.1 Level AAThe date of that government

The Title II dates moved once already: an interim final rule of April 20, 2026 pushed them back by about a year. The last row matters for agencies and software vendors: the Department of Justice fact sheet on the Title II web rule gives the example of a city parking app run by a private company, and that app still has to meet WCAG 2.1 Level AA. The table is a screening aid, not legal advice: ask your lawyer which rules apply to your organization.

Which WCAG version and level to design for

Design for WCAG 2.2 at Level AA. Level A covers the most basic barriers, Level AA adds the criteria that the Title II rule refers to, and Level AAA is the strictest. The W3C itself does not recommend AAA as a general policy for whole sites, because some content cannot meet all of it.

Version 2.2 is the safe choice even when a rule names 2.1. The W3C advises using WCAG 2.2 and states that content that conforms to 2.2 also conforms to 2.1 and 2.0. Among the criteria 2.2 adds are a minimum size for click and tap targets, focus that is not completely hidden behind sticky headers, and sign-in that works with password managers instead of relying on memory.

What web accessibility compliance looks like in a design file

An ADA compliant design is a set of decisions written into the design file: colors that pass contrast checks, a focus state for each control, an error state for each field, layouts that still work at the text size and screen width that WCAG sets, and a text alternative for each meaningful image and icon button. Developers build what the file shows, so a decision missing from the design can go missing from the code.

Design decisionWCAG 2.2 criterionWhat the design file shows
Text contrast1.4.3 Contrast (Minimum), AAText colors with a ratio of at least 4.5:1, or 3:1 for large text
Contrast of controls and icons1.4.11 Non-text Contrast, AAField borders, icons, and control states at 3:1 or more against their background
Meaning without color1.4.1 Use of Color, AAn error or a required field marked with text or an icon as well as a color
Keyboard focus2.4.7 Focus Visible and 2.4.11 Focus Not Obscured (Minimum), AAA focus style for each control, not completely hidden by sticky headers or banners
Target size2.5.8 Target Size (Minimum), AAClick and tap targets of at least 24 by 24 CSS pixels, or enough space around smaller ones
Headings and structure1.3.1 Info and Relationships, AEach heading marked with its level, so the code can carry the structure that the text styles show
Forms3.3.1 Error Identification and 3.3.2 Labels or Instructions, AA visible label for each field, and an error message in words next to the field
Zoom and small screens1.4.4 Resize Text and 1.4.10 Reflow, AALayouts that work at 200% text size and at 320 CSS pixels wide without scrolling sideways, except for data tables, maps, and other content that needs a two-dimensional layout
Images and icons1.1.1 Non-text Content, AAlt text for each image that carries meaning, and a name for each icon button
Sign-in3.3.8 Accessible Authentication (Minimum), AASign-in that does not rely on memory alone: support for password managers and paste, or another sign-in method

The simplest way to keep these right across a site is a shared set of colors and components. When the palette is checked for contrast once and every control has its focus state and every field its error state, each new page inherits them. Our guide to design system services explains how that shared set reaches the code.

Our designers make these decisions in Figma together with an AI agent connected to the file, which can open any layer and change it. The agent takes part in the design itself: it builds components, sets up the type styles, and, at the designer's request, checks every text and icon color in the file against its background. The designer directs that work and decides what a focus ring or an error message looks like. Every design delivery also includes a DESIGN.md file that describes the palette and the components, so the AI coding tools your developers use build new pages from the same checked colors.

What we found when we fixed our own website

In 2026 our team ran a round of accessibility fixes on ronasit.com. This round covered how the pages behaved:

  • Focus: a global style removed the browser's focus outline, so a keyboard user could not see where they were. We added a focus ring that appears for keyboard focus only.
  • Mobile menu: the menu button was built from a hidden checkbox, so the menu could not be opened with a keyboard. It is now a real button that tells a screen reader whether the menu is open, and links inside closed sections no longer take focus.
  • Form errors: error messages appeared on screen but were not linked to their fields, so a screen reader did not announce them when the field got focus. Each field now points to its error, and the name and email fields tell the browser what they collect, so autofill works.
  • Link names: every “View case” link on the case listing sounded the same in a screen reader's list of links. Each one now has a name that starts with its visible text and adds the case title, so voice control still finds it by what is on the screen.
  • Motion and targets: animations follow the reduced-motion setting of the operating system, and the small links and the cookie settings button in the footer got targets of at least 24 by 24 pixels.

“Nearly every fix went into a shared component or the global styles rather than a single page. A mistake in shared code reaches every page, and so does the fix.”

Alexander Storozhevsky, Lead developer at Ronas IT

Problems like these are why accessibility cannot be signed off at the design stage alone. Designers set the colors, states, and texts, and frontend developers decide whether a control is a real button, whether an error is linked to its field, and where focus goes.

Single-page apps built with React or Next.js add problems that no design file shows. When the app changes the route, the browser does not reset focus the way a full page load does, so a keyboard user can stay on a control that is no longer on the screen. A dialog must take focus when it opens and give it back to its trigger when it closes. An error or a toast must appear inside a live region that stays in the page, because many screen readers do not announce a region that appears together with its text. Aurora Scharff's audit list for React apps puts these focus and announcement checks next to the usual clickable divs and unlabeled inputs.

How to check a website for ADA compliance

Check a website in two passes: an automated scan for the errors a tool can detect, and a manual test of your main tasks with a keyboard, zoom, and a screen reader. The Department of Justice warns that a “clean” report from an automated checker does not necessarily mean everything is accessible, and suggests pairing the checker with a manual check.

  1. Run an automated checker on your main templates. It finds low contrast, missing alt text, empty links, and fields without labels in minutes.
  2. Put the mouse away. Press Tab through the home page, the menu, and one form. You should see where the focus is at every step and reach every control.
  3. Zoom and narrow the page. At 200% zoom and at a width of 320 pixels, no text should be cut off and no line of text should need sideways scrolling. Data tables, maps, and diagrams are the exception: WCAG allows them to scroll in both directions.
  4. Use a screen reader such as VoiceOver on a Mac or NVDA on Windows to complete your main task: a purchase, a booking, or a contact form.
  5. Submit forms with mistakes and check that each error is described in words and linked to its field.
  6. Check again after releases. New content and features can bring new errors, so the scan belongs in your release routine.

Our QA checklist includes keyboard navigation. The scheduled page audits that run automatically in our CI pipelines check accessibility along with speed, so if a release brings in an error that a tool can detect, it shows up in a later report. If you already know your site has problems and want a list of them ranked by severity, a UX audit that includes a WCAG check is the place to start.

Why an overlay widget is not enough on its own

An overlay is a script that adds an accessibility toolbar or tries to repair a page as it loads. It runs on top of the site's own code and does not change it, so a problem the script misses is still there. Automated tools are useful for finding problems, but the fix itself belongs in the design and in the code, where it stays in place for every visitor without a script in between.

In April 2025, the FTC approved a final order requiring accessiBe to pay $1 million. The FTC complaint said the company's claim that its widget could make any website WCAG compliant was false, misleading, or not backed by evidence. The order bars the company from making that claim without evidence to support it.

How much ADA compliant website design costs

The cost depends on whether you fix a live site or build a new one. A new corporate website, with design and development together, starts at $3,000. Each price below is for the work in its row, such as the design or the build. The accessibility scope, meaning the target level and the pages or screens to check, is part of the estimate, and so is project management.

Your situationWorkStarting priceTimeline
A live site that needs a ranked list of its problemsUX audit of the key pages, with a WCAG check of the screens in scopeFrom $500From 3 days
A live website that needs colors, states, and labels fixed, or a new layoutWebsite design of the pages that need new colors, states, labels, or layout, without developmentFrom $800 for a landing page, from $1,500 for a corporate siteLanding page: from 3 days. Corporate site: from 5 days
A live web product, such as a SaaS app or a client portalDesign fixes estimated by the screens and states they touch; a rework of the key screens is a product redesign, with a review of the current designBy scope; a product redesign from $2,500At least 1 week
A new website that your own developers will buildWebsite design without development: structure and responsive design of the key pagesFrom $800 for a landing page, from $1,500 for a corporate siteLanding page: from 3 days. Corporate site: from 5 days
A new corporate website that we design and buildCorporate website development, design includedFrom $3,000At least 2 weeks

Code fixes on a live site or product are estimated once the list of fixes is known. Fixing a live site costs less when the fixes are mostly colors, states, and labels, and more when the layout itself has to change. Our website redesign cost guide explains what else affects the cost of a redesign.

How to choose a WCAG compliant web designer or agency

Choose a company that names the standard it designs to and can show how it tests. Five questions on the first call tell you whether it can:

  • “Which WCAG version and level will you design and test our site to?” Expect a clear answer, such as WCAG 2.2 Level AA, and a reason if it is lower.
  • “How do you test it?” The answer should go beyond an automated score and include manual checks, such as a pass with the keyboard only.
  • “What will the design file show?” Look for focus and error states drawn next to the default ones.
  • “Do you use an overlay?” A company that offers a widget as the whole fix is making the kind of claim the FTC acted against.
  • “What happens after launch?” Ask whether the site is checked again on a schedule and how soon the team replies when you report an error.

“When accessibility comes up after the screens are approved, we go back through each of them for contrast and focus. When it comes up on the first call, it goes into the brief, and the first screen is already drawn that way.”

Alexander Kontsevoy, Art Director at Ronas IT

If you are comparing agencies for the wider design work as well, our overview of UI/UX design companies lists what else to check.

What to do next

  1. Find out which row of the ADA table above fits your organization, and confirm it with your lawyer.
  2. Pick your target: WCAG 2.2 Level AA covers the 2.1 level that the Title II rule names.
  3. Run an automated checker on your main templates and note the error types it finds.
  4. Test your main task with the keyboard only and with a screen reader.
  5. Decide between fixing the live site and a new design, and ask each agency the five questions.

Tell us which pages must meet WCAG 2.2 Level AA, and we will reply with an estimate for the design work. Send a list of fixes too, and the estimate will cover the code.

Frequently Asked Questions (FAQs)

What is an ADA compliant website?

It is a website that people with disabilities can use with a screen reader, with zoom, or with a keyboard instead of a mouse. The ADA does not list technical rules for business websites, so in practice a site is designed and tested against WCAG, the accessibility guidelines of the W3C.

Does my website need to be ADA compliant?

If your business is open to the public in the US, such as a store, a bank, a clinic, or a hotel, the Department of Justice takes the position that the ADA also covers what you offer on the web. State and local governments have a separate rule that names WCAG 2.1 Level AA, with compliance dates in April 2027 and April 2028. For a decision about your own case, ask a lawyer.

How do I make my website ADA compliant?

Since the ADA has no technical checklist for business websites, design and build the site to WCAG 2.2 Level AA, the level we recommend. In the design, choose text colors that pass contrast checks, draw a focus state for each control, give each field a visible label and an error state, and write alt text for each image that carries meaning. In the code, use real buttons and link each error to its field. Then test the site with an automated checker and by hand, and check it again after releases.

Is WCAG the same as ADA compliance?

No. The ADA is a US civil rights law, and WCAG is a technical standard from the W3C. The Department of Justice uses WCAG 2.1 Level AA in its rule for state and local governments and names WCAG as helpful guidance for businesses.

How do I check if my website is ADA compliant?

Start with an automated checker to find contrast errors, missing alt text, and fields without labels. Then test by hand: move through the main pages with the keyboard only, zoom the page to 200%, and complete your main task with a screen reader. The Department of Justice notes that a clean automated report does not necessarily mean everything is accessible, so the manual part matters.

What happens if my website is not ADA compliant?

People who cannot use the site can file complaints or lawsuits. In its web guidance, the Department of Justice lists agreements it has reached with companies over inaccessible websites, including H&R Block.

Can an accessibility plugin make my website ADA compliant?

Not on its own. The Department of Justice says automated checkers and overlays can be helpful tools but need to be used carefully. In 2025, the FTC ordered accessiBe to pay $1 million. In its complaint, the FTC called accessiBe's claim that its widget could make any website WCAG compliant false, misleading, or not backed by evidence. Use automated tools to find problems, and make the fixes in the design and the code.

How much does it cost to make a website ADA compliant?

It depends on the size of the site and on how much of it has to change. At Ronas IT, a UX audit of the key pages with a WCAG check starts from $500. New design for a website, without development, costs from $800 for a landing page or from $1,500 for a corporate site. Accessibility fixes to the design of a live web product, such as a SaaS app, are estimated by the screens and states they touch; when the key screens need rework, that is a product redesign, from $2,500, with a review of the current design. A corporate website that we design and build, new or redesigned, starts from $3,000. Code fixes on an existing site are estimated once the list of fixes is known. Project management is part of every one of these prices.

How long does it take to make a website ADA compliant?

A redesign of the key screens of a live web product takes at least 1 week before development, and the design of a new website from 3 days (a landing page) or 5 days (a corporate site). The rest depends on how many templates the site has and how deep the code fixes go. A site with a few templates can reach Level AA sooner than a large site where each page type needs its own fixes.

Do mobile apps have to be accessible too?

For state and local governments, yes: the Department of Justice rule covers their mobile apps as well as their websites, at WCAG 2.1 Level AA, even when a private company runs the app for them. For businesses, the Department of Justice guidance covers what they offer on the web, and the same WCAG criteria are a practical guide for apps.

Related posts

The Ronas IT cat mascot holds a magnifying glass over a laptop screen with a crooked button and a warning sign, next to a checklist
How to
UX audit services: what you get, how it works, and what it costs
2026-11-05 • 14 min read
The Ronas IT cat mascot on a ladder paints a browser window, turning its cluttered old layout into clean new blocks, with a blank price tag
How to
How much does it cost to redesign a website?
2026-10-30 • 13 min read
A designer surrounded by connected icons for a user, budget, documents, a pen, a typography tool and a magic wand
How to
Design system services: what you get, the process, and the cost
2026-11-17 • 16 min read
Choosing a design company: the Ronas IT cat mascot pins a check badge to the middle of three easels, each with a different phone screen design.
How to
UI/UX design companies: 9 to compare and how to choose one
2026-11-05 • 17 min read
The Ronas IT cat mascot at a design desk hands a phone screen made of interface blocks to a client's open hand beside a laptop
How to
UI/UX design outsourcing: models, where to find a partner, and handoff
2026-11-17 • 12 min read