---
title: "Website Accessibility Remediation & WCAG Audits | dirango"
description: "Website accessibility remediation with WCAG 2.1 and 2.2 AA audits, implementation, and verification on a weekly or monthly cadence."
canonical: "https://dirango.com/services/website-accessibility/"
---

# Website accessibility remediation.

Find the barriers that stop people from using your website, fix them, and test again. dirango provides WCAG 2.1 AA and 2.2 AA audits and remediation, with weekly or monthly reviews for new content and releases.

## Which pages and tasks need testing?

We start by listing the templates, pages, forms, and documents to test, along with the tasks people need to complete. That might include applying for a program, making a payment, or finding a public meeting document. We also identify any third-party systems that need a separate review.

We use automated tools and manual testing. A scanner can find some issues, but it cannot tell us whether a person can complete an application or understand a form error. [W3C's evaluation guidance](https://www.w3.org/WAI/test-evaluate/) explains why human evaluation is part of the process.

We agree on the standard before testing: WCAG 2.1 AA or WCAG 2.2 AA. The DOJ Title II web rule specifies WCAG 2.1 AA for covered state and local government entities; 2.2 AA adds further requirements.

## From an audit to a tested fix

### Prioritize barriers

Each finding identifies the affected task, the relevant WCAG criterion, reproduction steps, and the person responsible for the fix. A blocked application form usually deserves attention before a minor issue on an archive page.

### Implement remediation

Fix the issues in the site itself: headings and page structure, keyboard controls, forms, contrast, labels, links, and templates used across multiple pages.

### Verify the changes

Repeat the original failing task after the change, then check related pages and states. Record what passed, what still fails, and anything a third-party vendor must address.

### Keep the review current

New pages and software updates can introduce new problems. Weekly or monthly reviews let us check those changes, make repairs, and retest them.

## The 2027 and 2028 public-sector deadlines

For covered state and local government entities, the DOJ Title II web rule specifies WCAG 2.1 Level AA. WCAG 2.2 AA is available as a broader project target, but is not the standard named in the rule. See the [DOJ rule overview](https://www.ada.gov/resources/2024-03-08-web-rule/).

**Does the April 26, 2027 date apply to every public agency?** No. Under the DOJ’s 2026 interim final rule, the date is April 26, 2027 for covered state and local government entities with a total population of 50,000 or more, except special district governments. The date is April 26, 2028 for entities with a population below 50,000 and for every special district government. See the [2026 interim final rule](https://www.ada.gov/assets/pdfs/2026-ifr.pdf) for the amended dates.

Read our [2027 and 2028 deadline guide with working accessibility fixes](/insights/ada-website-accessibility-deadlines/) for population examples, document exceptions and practical retest steps.

These dates concern covered Title II entities, and entity classification affects applicability. Counsel should confirm your obligations. dirango provides technical services within the agreed scope; this work does not determine legal duties or guarantee compliance.

## Public-sector website experience

[Selected public-sector work](/work/#public-sector-work) includes [Build LACCD](https://www.build-laccd.org/) and the [Housing Authority of the City of Santa Barbara](https://hacsb.org/). These projects show our website work. They do not establish that we audited those sites or that the sites conform to WCAG.

For related ongoing site ownership, see [website governance](/services/website-governance/) and [WordPress support](/services/wordpress-support/). For practical review planning during a site rebuild, read the [accessibility audit checklist](/insights/accessibility-audit-checklist/).

## What should an audit deliver?

Read our [accessibility audit checklist with manual checks, remediation and retesting](/insights/accessibility-audit-checklist/) to see what a scan catches, what needs manual testing, and how to record a retest.

## Tell us what needs reviewing.

Send us the site, any issues you already know about, and the deadline you're working toward. We can help identify the pages and tasks to test first.

[Discuss accessibility work ](/contact/)