ADA TITLE II COMPLIANCE

Title II website &
mobile accessibility.

Prepare your public services for the DOJ’s digital accessibility rule.

Turn WCAG 2.1 AA requirements into clear priorities, practical fixes, and documented progress. EqualAccess. helps your team test and improve the digital experiences your community relies on.

  • Human-led testing
  • Code-level fixes
  • Clear documentation
Illustrative form improvement: a field label and visible focus help people navigate the appointment journey. This is a visual demo of work performed by human experts; scope and results depend on testing.

Plan around the right deadline.

Current DOJ web and mobile rule compliance dates.

Public entities with a total population of 50,000 or more, excluding special district governments.

Public entities with a total population below 50,000, and all special district governments.

The April 2026 interim final rule extended these dates. Population follows the rule’s definitions, rather than employee, student, or website-user counts. School districts are not special district governments. Read DOJ’s deadline guidance · 28 CFR § 35.200. Sources reviewed .

WHO THE RULE COVERS

Public services.
Open to your whole community.

ADA Title II applies to state and local public entities. The web and mobile rule covers digital content and applications they provide directly or through contractual, licensing, or other arrangements.

That can include benefit applications, permit forms, payments, booking journeys, program information, and relevant online documents.

Using a vendor does not remove the public entity’s responsibility. Include outsourced portals and apps in your accessibility planning. Independent third-party posts have a different, limited exception.

DOJ’s overview of covered public entities · Web and mobile requirements.

  • Government & public agencies

    State, county, city, and local government departments delivering information and services.

  • Public education

    Public schools, community colleges, universities, and their digital learning and service experiences.

  • Health & community services

    Public hospitals, clinics, benefits programs, and social services.

  • Transit & public spaces

    Transit authorities, libraries, parks, and recreation programs.

  • Courts & civic participation

    Courts, election offices, law enforcement, and public participation tools.

  • Special district governments

    Public entities such as water or fire districts, with the rule’s specific deadline treatment.

WHAT THE RULE REQUIRES

A technical standard.
A usable public experience.

The rule sets WCAG 2.1 Level A and AA success criteria and conformance requirements as its baseline. Testing needs to follow complete service journeys, including documents and relevant third-party components.

  • Keyboard & focus

    Operate controls without a mouse, follow a logical focus order, and see where focus is located.

  • Structure & labels

    Use meaningful headings, field labels, and programmatic relationships.

  • Text alternatives

    Provide useful alternatives for meaningful images and other non-text content.

  • Accessible media

    Provide captions, audio description, or text alternatives as the applicable media criteria require.

  • Contrast & perception

    Make text and essential interface details distinguishable; do not rely on color alone.

  • Reflow & zoom

    Support text resizing and reflow without losing information or required functionality.

  • Forms & feedback

    Make instructions and errors understandable, and expose relevant status updates.

  • Controls & interactions

    Provide accessible names, roles, and states, with appropriate gesture, timing, and motion behavior.

These are examples, not a complete checklist. W3C’s conformance requirements include full pages and complete processes. Broader WCAG 2.2 AA testing can be scoped while preserving the DOJ’s WCAG 2.1 mapping.

Exceptions need a closer look—not a blanket assumption.

The rule has five content exceptions, each with conditions. Password protection alone does not exempt a portal, website, or application.

  • Archived web contentQualifying older content kept unchanged, only for reference, research, or recordkeeping, in an area identified as an archive.
  • Pre-existing documentsCertain files available before the deadline, except documents currently used to access or participate in public services.
  • Independent third-party contentSome posts by third parties; not content posted through a contractual, licensing, or other arrangement with the public entity.
  • Individual secured documentsCertain conventional electronic documents about an individual, their property, or account, protected by a password or other security.
  • Pre-existing social media postsPosts published by the public entity before its compliance date.

Existing obligations for effective communication and equal participation continue. Your legal or compliance advisers should determine how an exception applies to particular content.

Read all five exceptions in 28 CFR § 35.201 · DOJ examples and explanations.

HOW EQUALACCESS. HELPS

Turn requirements into
work your team can deliver.

Choose the support your project needs, from a focused assessment to remediation and ongoing review. Scope, responsibilities, and deliverables are agreed before work begins.

Accessibility Audits & Testing

Combine automated analysis with manual keyboard and screen-reader testing across agreed content, components, and critical journeys. Findings include user impact, WCAG references, and actionable recommendations.

Explore Audits & Testing

Code-Level Remediation

Correct barriers in website code, templates, content, and interaction behavior. We can implement agreed changes directly or work alongside your developers and vendors.

Explore Code-Level Remediation

Documentation & VPAT/ACR

Keep a clear record of findings, changes, retests, and remaining limitations. Where product or procurement reporting calls for it, scope an ACR using the appropriate VPAT® template.

Explore VPAT & ACR

Consulting & Training

Give developers, designers, content teams, and accessibility coordinators practical guidance they can use. Build accessibility into design reviews, publishing, procurement, and release checks.

Explore Consulting & Training

Ongoing Monitoring & Support

Review new content and changes through an agreed mix of automated monitoring, periodic manual testing, and technical support. Frequency and coverage are defined for your organization.

Explore Monitoring & Support

Include the whole service journey.

Web pages, online forms, documents, media, and vendor handoffs can each introduce barriers. For native mobile apps, confirm platforms, access, assistive technologies, and specialist testing coverage during scoping.

Explore PDF & Document Remediation

OUR FIVE-STEP PROCESS

From an accessibility backlog
to documented progress.

A practical sequence with clear handoffs. Your timeline depends on the content, technology, access, vendor dependencies, and people available to implement changes.

01 · Assess

Start with scope and priorities.

Identify the websites, documents, public-service journeys, and vendor dependencies involved. Agree the technical target, access requirements, testing coverage, responsibilities, and delivery milestones. Your legal advisers confirm legal applicability and the relevant deadline.

WHAT THIS STAGE PRODUCES
  • Digital asset and journey inventory
  • Agreed assessment scope
  • Responsibilities and project milestones

02 · Manual Testing

Understand the barriers in real use.

Use automated findings as one input, then investigate keyboard operation, screen-reader behavior, forms, navigation, and critical transactions through expert manual testing. Prioritize reproducible issues by user impact and service importance.

WHAT THIS STAGE PRODUCES
  • Reproduction steps and evidence
  • Relevant WCAG criteria
  • Prioritized technical findings

03 · Code-Level Remediation

Fix the underlying implementation.

Address agreed issues in code, content, and components. We can implement changes, guide your developers, and coordinate vendor-owned work. Track dependencies and unresolved findings rather than treating them as complete.

WHAT THIS STAGE PRODUCES
  • Scoped fixes and developer guidance
  • Issue ownership and status
  • Implementation notes

04 · Retest & Verify

Repeat the affected journeys.

Retest agreed fixes in the relevant environment using appropriate manual, keyboard, assistive-technology, and automated checks. Record whether each finding is resolved, still open, or requires further investigation.

WHAT THIS STAGE PRODUCES
  • Issue-level retest results
  • Regression and journey checks
  • Remaining limitations

05 · Documentation

Make the progress reviewable.

Bring scope, findings, remediation, and verification evidence into a usable technical record. Include an ACR, role-specific training, or an ongoing support plan where those deliverables are part of the engagement.

WHAT THIS STAGE PRODUCES
  • Findings and remediation record
  • Verification evidence and summary
  • Optional ACR and handoff materials

The full sequence applies when the engagement includes remediation and retesting. Audit-only, training, and advisory projects cover the agreed stages. Ongoing support can continue after the initial handoff.

ENGAGEMENT OPTIONS

The right support
for your team’s capacity.

Choose a defined project, targeted expertise, or continuing support. We can also combine them around your priorities.

Defined-scope project

A focused audit or a coordinated assessment and remediation engagement.

Best suited to
Teams with a clear set of sites, journeys, or deliverables.
Typical scope
Agreed assessment, findings, and—when included—fixes, retesting, and documentation.
How it is priced
A project fee and milestones agreed in the statement of work.

Consulting support

Specialist help alongside your existing developers and content teams.

Best suited to
Teams that can implement changes but need testing, advice, or training.
Typical scope
Technical reviews, issue investigation, guidance sessions, and scoped training.
How it is priced
An agreed hourly, daily, or scoped advisory arrangement.

Ongoing partnership

Accessibility support as your digital services continue to change.

Best suited to
Organizations with frequent content updates, releases, or vendor changes.
Typical scope
Agreed monitoring, periodic manual testing, change reviews, and support.
How it is priced
A monthly or quarterly scope with defined coverage and capacity.

Pricing depends on the number of properties and templates, journey complexity, documents, integrations, testing access, and remediation responsibilities. We scope the work before quoting; no fixed delivery period is assumed.

Discuss Your Title II Accessibility Needs

WHAT YOU RECEIVE

A clear record.
A practical next step.

Your deliverables connect the work completed to the experience tested. They also make remaining work visible.

Public services
Accessibility work record
Assessment scope
Defined
Findings & ownership
Recorded
Fixes & retest evidence
Linked
Open issues
Documented
Illustrative record structure. Actual deliverables depend on the agreed engagement.
  • Accessibility audit & findings

    Tested locations, methods, reproducible barriers, relevant criteria, evidence, and priority.

  • Remediation roadmap & code changes

    A practical plan with ownership, dependencies, and agreed implementation work.

  • Verification record

    Results of retesting, issue status, and any unresolved barriers or testing limitations.

  • Technical conformance summary

    A documented scope, testing methods, results, and limitations. Any conformance statement must reflect the evidence and its defined scope.

  • Optional VPAT / ACR

    A product-specific conformance report when separately included for procurement or other reporting needs.

  • Training & handoff materials

    Role-specific guidance, publishing checklists, or technical notes where training is included.

  • Ongoing support plan

    An agreed review frequency, responsibilities, and process for handling future changes.

AFTER THE INITIAL PROJECT

Keep accessibility in
the way you work.

A deadline is a milestone. New content, forms, procurement decisions, and code releases can introduce new barriers. Build review into the changes your team already makes.

Explore Ongoing Monitoring & Support
  • Publish with care

    Use content guidance and document checks before information reaches your community.

  • Review meaningful changes

    Include accessibility in design, development, procurement, and release decisions.

  • Revisit critical journeys

    Combine monitoring with periodic manual testing and review of user-reported barriers.

THE RIGHT REQUIREMENT, IN CONTEXT

Title II is one part of the accessibility landscape. Your organization may need to account for more than one requirement.

Official references: DOJ Title II fact sheet · Current web and mobile regulation · W3C WCAG 2.1.

QUESTIONS, ANSWERED

Frequently
asked questions.

Practical answers for teams planning Title II accessibility work.

Talk to EqualAccess.

The current web and mobile rule deadlines are April 26, 2027 for public entities with populations of 50,000 or more, excluding special district governments, and April 26, 2028 for smaller entities and special district governments.

Existing Title II obligations continue before those dates. Prioritize critical journeys now, and review the rule’s specific exceptions before deciding that older content can be left unchanged. Read DOJ’s guidance.

The Web Content Accessibility Guidelines are technical criteria developed by W3C. Level AA conformance includes the Level A and AA success criteria and the conformance requirements, including full pages and complete processes.

Our testing is scoped against that baseline, with evidence and limitations documented. Explore WCAG Compliance & Conformance.

Yes. The DOJ rule covers web content and mobile apps provided by public entities, including through relevant third-party arrangements. Web content includes conventional electronic documents such as PDFs, Word documents, presentations, and spreadsheets.

Specific exceptions may apply to some content. We scope document and web work around your services; native mobile-app platforms, access, and specialist testing coverage are confirmed before an engagement.

The public entity remains responsible for the covered web content and mobile apps it provides through contractual, licensing, or other arrangements. An outsourced payment portal or booking service should be part of your accessibility planning.

We can test agreed vendor journeys, document technical issues, and help coordinate remediation. Your legal and procurement teams review contracts and legal responsibilities.

A high scanner score or a mostly fixed issue list is not a WCAG conformance determination. Remaining barriers must be understood and documented.

The rule’s minimal-impact provision is narrow: the public entity must demonstrate that the noncompliance does not affect access in the specific ways the rule describes. It is not a general allowance for a few minor failures. Your legal advisers should assess its application. Read 28 CFR § 35.205.

EqualAccess. provides technical documentation, not an official ADA certificate. Deliverables may include findings, remediation records, retest evidence, and a scoped conformance summary.

An ACR using a VPAT® template can be included when appropriate. It records product conformance information; it does not certify legal compliance or remove the need for ongoing accessibility work.

An audit-only engagement can work well when your developers have capacity to implement findings. We provide the agreed testing, priorities, and guidance.

If your team needs implementation help, we can scope code-level remediation and retesting. The right approach depends on your technology, backlog, vendor access, internal capacity, and deadlines.

Yes. We can investigate the reported technical barriers, identify the affected journeys, and help prioritize remediation, verification, and documentation.

Your attorney handles the legal matter. Explore ADA Website Lawsuit Support for the technical work around an active complaint or demand.

START WITH YOUR PUBLIC SERVICES

Get started with
ADA Title II accessibility.

Tell us about your websites, key service journeys, and upcoming deadlines. We’ll help define the technical work and a practical path forward.

Human expertise. Practical implementation. Documented progress.

Opens in a new tab.