# ADA website compliance and accessibility, audited and built to WCAG 2.2 AA

> ADA website compliance and WCAG 2.2 AA audits, fixes and accessible builds, tested by keyboard and screen reader and documented for your legal team.

For ADA website compliance and accessibility laws worldwide, we audit existing websites against WCAG 2.2 Level AA, fix what's blocking people, and build new sites that work by keyboard, by screen reader and with motion turned down. Every finding is documented, so you can show what was tested, what passes and what's left to do.

## Common problems

- **Visitors who can't complete a task:** Menus that need a mouse, forms with unlabeled fields and buttons a screen reader announces only as button stop people from buying, booking or getting in touch.
- **Design choices that exclude people:** Low-contrast text, hidden focus outlines, tiny tap targets and animation that can't be paused make sites harder or impossible to use for many visitors.
- **Legal exposure without a clear picture:** Accessibility laws now apply to websites in many markets, but most businesses have no audit, no record of testing and no plan to show they are working on it.
- **Widgets sold as a quick fix:** Overlay toolbars promise instant compliance, but they don't change the underlying code and can interfere with the assistive technology people already use.

## What's included

- **WCAG 2.2 AA audit:** Automated scans plus manual testing of key templates and user journeys against every Level A and AA success criterion, with issues ranked by impact.
- **Keyboard and focus review:** Every interactive element reachable and usable by keyboard in a logical order, with visible focus states that aren't hidden behind sticky headers.
- **Screen reader testing:** Key journeys tested with common screen readers on desktop and mobile, checking headings, landmarks, labels, alt text and announcements.
- **Color and contrast fixes:** Text, icons, focus indicators and form borders checked against WCAG contrast ratios, with adjusted colors that stay true to your brand.
- **Accessible forms:** Visible labels, clear instructions, error messages linked to fields, logical grouping and authentication that doesn't rely on memory puzzles.
- **Motion and animation controls:** Pause controls for carousels, video and 3D scenes, plus reduced-motion versions that respect the visitor's operating system setting.
- **Remediation in code:** Fixes made in your templates and components, or detailed tickets for your developers, then retested to confirm each issue is resolved.
- **Conformance documentation:** A record of scope, methods, results and known exceptions, plus a draft accessibility statement you can publish and keep up to date.
- **Accessible new builds:** New websites designed and coded to WCAG 2.2 AA from the start, with accessibility checks built into every release.

## What we test on every audit and build

Automated tools catch only part of the picture. These are the areas where manual testing finds the issues that most affect real visitors.

- **Keyboard paths:** Menus, dialogs, carousels, filters and checkout all usable with Tab, Shift+Tab, Enter, Space, Escape and arrow keys, with no keyboard traps.
- **Focus states:** A clearly visible focus indicator on every control, with enough contrast, and never fully covered by cookie banners or sticky bars.
- **Contrast and color:** At least 4.5:1 for normal text, 3:1 for large text and key interface elements, and information never conveyed by color alone.
- **Reduced motion and pause controls:** Moving content that lasts more than five seconds can be paused, and parallax, scroll effects and 3D scenes calm down when reduced motion is requested.
- **Screen reader output:** Meaningful headings, landmarks, link text, image alternatives and status messages, so the page makes sense when it is heard rather than seen.
- **Forms and errors:** Labels, required-field cues, input purpose for autofill, error identification and suggestions, and no repeated entry of the same information.
- **Target size and touch:** Tap targets that meet the WCAG 2.2 minimum size or spacing, and alternatives for any action that depends on dragging.
- **Accessible RTL:** Arabic pages with correct lang and dir attributes, a reading and focus order that follows the right-to-left layout, and properly announced mixed-language text.

## The first 90 days

### Weeks 1–2: Audit and prioritize

- Scope agreed: templates, journeys and devices
- Automated scans and manual WCAG 2.2 AA testing
- Issues ranked by user impact and effort

### Build or remediate: Fix and retest

- Components and templates fixed in code
- Contrast, focus, forms and motion issues resolved
- Keyboard and screen reader retesting of each fix
- Content editors briefed on alt text and headings

### Launch and after: Document and maintain

- Conformance report and accessibility statement
- Accessibility checks added to the release process
- Periodic re-audits as content and features change

## What we report

- WCAG 2.2 A and AA success criteria passing
- Automated audit issues by severity
- Manual audit issues open and resolved
- Key journeys completed by keyboard only
- Key journeys completed with a screen reader
- Color contrast failures
- Core Web Vitals after remediation

## Website accessibility laws by region

|  | Main legislation | Who it mainly affects | Technical reference |
| --- | --- | --- | --- |
| United States | ADA Title III | Businesses open to the public, through private lawsuits | No set standard for private sites; WCAG widely used |
| Canada | AODA (Ontario) and Accessible Canada Act | Ontario organizations with 50+ employees; federally regulated sectors | WCAG 2.0 AA under AODA |
| European Union | European Accessibility Act, applied from 28 June 2025 | Many consumer products and services sold in the EU, with a microenterprise exemption for services | EN 301 549, which references WCAG |
| United Kingdom | Equality Act 2010 | Service providers, through the duty to make reasonable adjustments | WCAG commonly used as the benchmark |
| Australia | Disability Discrimination Act 1992 | Providers of goods and services, through complaints | WCAG referenced in official guidance |

## Why web accessibility matters now

Around the world, a large share of people live with a disability that affects how they use the web, whether that's low vision, color blindness, limited hand movement, hearing loss or a cognitive condition. Add older visitors, people on a cracked phone screen in bright sunlight and anyone using a keyboard because a trackpad broke, and accessibility stops looking like a niche concern. It's a question of whether people can use your website at all.

The legal picture has also changed. Accessibility laws in the United States, Canada, the European Union, the UK and Australia now reach websites in different ways, and enforcement is no longer theoretical. We can't certify legal compliance, but we can build and test your site to WCAG 2.2 AA and document what we found and fixed. That's the practical foundation any legal adviser will ask about first.

## How our WCAG 2.2 AA audits work

Every audit starts by agreeing scope: the templates, components and user journeys that matter most, such as navigation, search, product pages, booking, checkout and contact forms. We run automated scans across the site to catch issues at scale, then test the key journeys manually, because automated tools can only detect part of what WCAG covers.

Manual testing means using the site the way people with disabilities do. We work through each journey by keyboard alone, checking order, visible focus and traps. We listen to pages with screen readers on desktop and mobile. We check contrast, zoom and reflow at small widths, target sizes, form labels and error handling, and how the site behaves with reduced motion turned on. Each issue is mapped to the WCAG success criterion it fails, ranked by impact on users, and paired with a recommended fix.

## Remediation and accessible builds

Audits are only useful if the issues get fixed. We can fix them in your templates and components ourselves, or write detailed tickets for your developers and retest their work. Most of the value sits in shared components such as menus, dialogs, carousels, form fields and buttons, so fixing them once improves every page that uses them.

For new sites, accessibility is part of the design system from the first wireframe: color palettes that meet contrast ratios, focus styles designed rather than removed, semantic HTML, and motion that can be paused or reduced. That applies to animated and 3D sections too, which get pause controls, reduced-motion versions and text alternatives. Arabic and other right-to-left pages get the same keyboard and screen reader testing as English ones. If your current site needs deeper work, a [website revamp](/services/web-development/website-revamp/) can address it, either as a Refresh on your current platform or a Rebuild on a modern stack.

## The legal context, in plain terms

In the United States, website accessibility claims are usually brought under Title III of the ADA, and many businesses that sell or take bookings online face that risk. Our [United States](/regions/united-states/) page covers the market in more detail. In Canada, Ontario's AODA sets WCAG 2.0 AA requirements for public websites of larger organizations, and the Accessible Canada Act applies to federally regulated sectors.

Across the European Union, the European Accessibility Act has applied since 28 June 2025 to many consumer products and services, including e-commerce, and it can reach businesses outside the EU that sell to EU consumers. See our [Europe](/regions/europe/) market notes for context. In the UK, the Equality Act 2010 requires service providers to make reasonable adjustments, and in Australia the Disability Discrimination Act 1992 covers the provision of goods and services. This is general information, not legal advice, so please confirm your obligations with a qualified lawyer.

## Why overlays don't solve the problem

Accessibility overlays and widgets are sold as a one-line fix, but they sit on top of the page rather than changing it. Missing labels, broken keyboard paths and poor heading structure remain in the code, and many assistive technology users find overlays get in the way. Real conformance comes from fixing the site itself.

## Accessibility and SEO work together

Semantic headings, descriptive links, image alternatives, readable content and fast, stable pages help search engines and AI systems understand a site as well as people. IMPOSEO is an SEO and web development agency, so every accessibility project is checked for its effect on search, and our [technical SEO](/services/technical-seo/) team makes sure fixes improve crawlability and Core Web Vitals rather than harming them. We scope and quote every project in USD after a free website review.
## FAQ

### What is WCAG 2.2 AA?

WCAG, the Web Content Accessibility Guidelines, is the W3C standard for making web content accessible. Version 2.2 was published in 2023 and adds criteria on focus visibility, target size, dragging, accessible authentication and consistent help. Level AA is the conformance level most laws and policies point to, and it's the level we audit and build to.

### Will this make our website legally compliant?

We can't certify legal compliance, and no honest agency can. What we do is build and test to WCAG 2.2 AA, fix the issues we find and document conformance, so you have clear evidence of the work. Laws differ by country and situation, so we recommend getting advice from a lawyer familiar with accessibility law in your markets.

### Does the ADA apply to websites?

In the United States, many courts have applied Title III of the ADA to business websites, and website accessibility lawsuits are filed in large numbers every year. The Department of Justice has not set a specific technical standard for private businesses' websites, but WCAG is the benchmark most often used in settlements and guidance. A lawyer can tell you how this applies to your business.

### What does the European Accessibility Act mean for our website?

The European Accessibility Act has applied across EU member states since 28 June 2025. It covers many consumer-facing products and services, including e-commerce, banking services, e-books and passenger transport services, and it can apply to businesses outside the EU that sell to EU consumers. Microenterprises providing services are exempt. National authorities enforce it, so please confirm your position with legal advice.

### What are the requirements in Canada?

In Ontario, the AODA requires public sector organizations and private and non-profit organizations with 50 or more employees to make public websites conform to WCAG 2.0 Level AA, with some exceptions. At the federal level, the Accessible Canada Act applies to the federal government and federally regulated sectors such as banking, telecommunications and transportation. Other provinces have their own accessibility laws at different stages.

### What about the UK and Australia?

In the UK, the Equality Act 2010 requires service providers to make reasonable adjustments for disabled people, which is generally understood to include websites, and public sector bodies have separate accessibility regulations. In Australia, the Disability Discrimination Act 1992 makes disability discrimination in providing goods and services unlawful, and official guidance points to WCAG for websites.

### Do accessibility overlays or widgets make a site compliant?

No. Overlays add a toolbar or script on top of the page, but they don't fix missing labels, broken keyboard paths or poor heading structure in the underlying code. Many disabled users report that overlays get in the way of the screen readers and settings they already rely on, and having one installed has not stopped businesses from being sued.

### Can't automated tools find every issue?

No. Automated scanners are useful for catching issues such as missing alt attributes or low contrast at scale, but they can only detect part of what WCAG covers. They can't judge whether alt text is meaningful, whether focus order makes sense or whether a checkout works with a screen reader. Our audits combine automated scans with manual keyboard and screen reader testing.

### Can a site with animation or 3D content be accessible?

Yes, with planning. Animated and 3D sections need a way to pause anything that moves for more than five seconds, a reduced-motion version that respects the visitor's system setting, keyboard-operable controls and a text alternative for information conveyed visually. We apply the same rules to our own interactive builds.

### How do you handle accessibility on Arabic and RTL sites?

Arabic pages need the correct lang and dir attributes so screen readers use the right voice and reading direction. Focus order has to follow the right-to-left layout, mixed Arabic and Latin text must be marked up so it's announced properly, and icons and arrows need to mirror in the right places. We test RTL pages with the same keyboard and screen reader checks as English ones.

### Should we fix our current site or rebuild?

It depends on how deep the issues go. If most problems sit in content and a handful of components, remediation or a Refresh on your current platform is usually enough. If the theme or framework generates inaccessible markup everywhere, a Rebuild on a modern stack can cost less than patching it. The audit gives you the evidence to decide.

### Does accessibility help SEO?

Often, yes. Clear headings, descriptive link text, image alternatives, semantic HTML and fast, stable pages help search engines and AI systems understand content as well as people. IMPOSEO is an SEO and web development agency, so SEO is part of every remediation and build, though we never promise specific rankings.

### How much does a web accessibility audit or remediation cost?

It depends on the number of unique templates and user journeys, the platform, how many issues the audit finds, whether we fix the code or brief your developers, and whether you need ongoing monitoring. A small brochure site is a much smaller job than a large store with a custom checkout. We quote in USD after a free website review.

---
Source: https://imposeo.com/services/web-development/web-accessibility/
IMPOSEO: SEO for Google and AI search. Contact: rank@imposeo.com. Proposals are quoted in USD after a free audit: https://imposeo.com/contact/