For enterprises and public bodies: cities, counties, state and federal agencies
Two colleagues review a large monitor in a bright office; the screen is out of focus.

ADA TITLE II · APRIL 26, 2027 / APRIL 26, 2028

Help your agency work toward ADA Title II compliance, with the evidence to show it.

Docketward runs automated WCAG 2.1 AA checks on the public pages and PDFs of cities, counties and other local governments. You get a dated report of what failed and what needs a person to review. Your team or web vendor fixes the issues. You keep the record.

When you send, your email app opens with this message addressed to support@docketward.com.

Built on axe-core 4.14.0 and veraPDF. Nothing is installed on your site.

Each scan produces a dated PDF, HTML and CSV report, a ranked fix list, an evidence record and Title II worksheets.

SAM.gov registered: ADELOS, LLC · UEI L2TRV8J4G1S1 · CAGE 24TU8. We quote by scope and respond to RFQs and RFPs.

See a sample report How to buy

Start here

Skip carousel

Showing 1 to 4 of 4

Check our work before you talk to us.

  • 01

    Sample report

    A real report from a saved scan.

  • 02

    Coverage and limits

    What automated checks cover, and what needs a person.

  • 03

    How we crawl

    Our user agent, our request rate and robots.txt.

  • 04

    Data inventory

    What we store, and for how long.

Facts you can check

  • WCAG 2.0, 2.1 and 2.2 Level AA page checks with axe-core 4.14.0
  • PDF/UA-1 checks with veraPDF, plus Word, Excel and PowerPoint review signals
  • A ranked fix list, scan-to-scan comparison, evidence record and Title II worksheets
  • Title II dates: April 26, 2027 (population 50,000 or more) · April 26, 2028 (under 50,000 and special districts), from the April 20, 2026 interim final rule (91 FR 20902)

Standards we check against

Title II legal floor. Automated page rules, axe-core 4.14.0
WCAG 2.1 AA
PDF checks, veraPDF
PDF/UA-1
Dated report, ranked fix list, evidence record
Proof
A city clerk and a colleague discuss a wall planning calendar in a municipal office; the calendar is out of focus.

ADA Title II

Two dates, one standard.

The Department of Justice set WCAG 2.1 Level AA as the standard for the web content and mobile apps of state and local governments. There are two compliance dates. Governments with a total population of 50,000 or more: April 26, 2027. Smaller governments and special district governments: April 26, 2028. The rule says how to count population. Check which date applies to you.

Public colleges and school districts are covered by the same rule. The rule has exceptions. Ask your counsel which compliance date and exceptions apply to your entity. What a scan can tell you is which automated checks your site fails. Each report names the 29 WCAG 2.1 criteria that have no axe-core rule and need a person, out of 50. See Coverage and limits.

Source: U.S. Department of Justice, interim final rule, 91 FR 20902 (published April 20, 2026; document 2026-07663). Compliance dates: April 26, 2027 (population 50,000 or more) and April 26, 2028 (under 50,000 and special districts). The 2024 final rule (89 FR 31320; document 2024-07758) set WCAG 2.1 AA as the standard. The April 20, 2026 interim final rule set the current dates. A lawsuit challenging the extension is ongoing; check ADA.gov.

Read the rule in plain words

What you get from each scan.

  1. 01

    Pages

    Automated WCAG Level A and AA results for each public page we reach, up to your plan’s limit.

  2. 02

    PDFs

    PDF/UA-1 results for the PDFs linked from those pages, up to 25 MB each.

  3. 03

    A ranked fix list

    Issues grouped and ranked so your team knows where to start.

  4. 04

    A report for your records

    A dated PDF report you can keep with your Title II plan records.

See what changed since your last scan.

Each new scan is compared with the one before it. The report lists issues that are new, fixed or still open. You can also export a local alert file. A hosted dashboard with emailed alerts is not live.

Example of scan-to-scan comparison. Illustrative numbers.

Pages checked
1,842
PDFs checked
312
Open issues (last scan: 232)
214
Pages we could not reach
9
Issues by WCAG criterion
Criterion This scan Last scan
1.1.1 Non-text Content 72 80
1.3.1 Info and Relationships 31 34
1.4.3 Contrast (Minimum) 54 57
2.4.4 Link Purpose (In Context) 49 52
3.1.1 Language of Page 8 9
Total open issues 214 232

What we are not.

Nothing is installed on your site or servers. We do not add a widget or overlay to your pages, and we do not inject an overlay and call that compliance. We read your public pages and PDFs and write a dated report you can keep.

A staff member uses a braille display, keyboard and laptop to review a municipal website; the screen is out of focus.

What automation can't tell you.

Automated tools find only part of the problems. Manual review is still required. A scan can tell you alt text is missing. It cannot tell you whether the alt text describes the image. That takes a person. The same goes for reading order, and for whether a form works by keyboard from start to finish.

Current reports include a “What automated checks cover” section. In the older sample on this site it is titled “Current scanner coverage, for reference”. Of the 50 WCAG 2.1 A and AA success criteria, 21 have at least one rule enabled in our scan configuration (axe-core 4.14.0) and 29 have none and need manual review. A criterion with a rule is not fully covered by it.

Read coverage and limits

How to buy Docketward.

How buying works
  • Tell us your site

    Quoted by scope

    1of 3

    What we do
    You send the public URL and any scope notes.
    What you get
    We confirm what we will crawl before we start.
  • We scan and document

    Quoted by scope

    2of 3

    What we do
    Automated WCAG 2.1 AA page checks and PDF/UA-1 checks, within the agreed scope.
    What you get
    A dated report, ranked fix list, evidence record and worksheets.
  • You buy by quote

    Quoted by scope

    3of 3

    What we do
    We quote by scope and respond to RFQs and RFPs.
    What you get
    No public prices. Ask us for a sample scan or a proposal.

Buying with a purchase order.

We quote by scope. Ask us for a quote packet (scope letter, sample report and, when available, a W-9). Tell us your purchasing route. We will say up front which forms we can complete and which we cannot. We do not ask for a bond or a multi-year term.

A new product.

Docketward is a new product. We have no customer logos to show you, so we show you a sample report instead. We do not inject an overlay and call that compliance.

About and Trust

Frequently asked questions

See what a scan finds on your site.

We confirm the scope with you before we run a sample scan. You receive a dated report package. It is not a certification.

Two colleagues review a large monitor in a bright office; the screen is out of focus.

ADA TITLE II · APRIL 26, 2027 / APRIL 26, 2028

Help your agency work toward ADA Title II compliance, with the evidence to show it.

Docketward runs automated WCAG 2.1 AA checks on the public pages and PDFs of cities, counties and other local governments. You get a dated report of what failed and what needs a person to review. Your team or web vendor fixes the issues. You keep the record.

When you send, your email app opens with this message addressed to support@docketward.com.

Built on axe-core 4.14.0 and veraPDF. Nothing is installed on your site.

Each scan produces a dated PDF, HTML and CSV report, a ranked fix list, an evidence record and Title II worksheets.

SAM.gov registered: ADELOS, LLC · UEI L2TRV8J4G1S1 · CAGE 24TU8. We quote by scope and respond to RFQs and RFPs.

See a sample report How to buy

Start here

Skip carousel

Showing 1 of 4

Check our work before you talk to us.

  • 01

    Sample report

    A real report from a saved scan.

  • 02

    Coverage and limits

    What automated checks cover, and what needs a person.

  • 03

    How we crawl

    Our user agent, our request rate and robots.txt.

  • 04

    Data inventory

    What we store, and for how long.

Facts you can check

  • WCAG 2.0, 2.1 and 2.2 Level AA page checks with axe-core 4.14.0
  • PDF/UA-1 checks with veraPDF, plus Word, Excel and PowerPoint review signals
  • A ranked fix list, scan-to-scan comparison, evidence record and Title II worksheets
  • Title II dates: April 26, 2027 (population 50,000 or more) · April 26, 2028 (under 50,000 and special districts), from the April 20, 2026 interim final rule (91 FR 20902)

Standards we check against

Title II legal floor. Automated page rules, axe-core 4.14.0
WCAG 2.1 AA
PDF checks, veraPDF
PDF/UA-1
Dated report, ranked fix list, evidence record
Proof
A city clerk and a colleague discuss a wall planning calendar in a municipal office; the calendar is out of focus.

ADA Title II

Two dates, one standard.

The Department of Justice set WCAG 2.1 Level AA as the standard for the web content and mobile apps of state and local governments. There are two compliance dates. Governments with a total population of 50,000 or more: April 26, 2027. Smaller governments and special district governments: April 26, 2028. The rule says how to count population. Check which date applies to you.

Public colleges and school districts are covered by the same rule. The rule has exceptions. Ask your counsel which compliance date and exceptions apply to your entity. What a scan can tell you is which automated checks your site fails. Each report names the 29 WCAG 2.1 criteria that have no axe-core rule and need a person, out of 50. See Coverage and limits.

Source: U.S. Department of Justice, interim final rule, 91 FR 20902 (published April 20, 2026; document 2026-07663). Compliance dates: April 26, 2027 (population 50,000 or more) and April 26, 2028 (under 50,000 and special districts). The 2024 final rule (89 FR 31320; document 2024-07758) set WCAG 2.1 AA as the standard. The April 20, 2026 interim final rule set the current dates. A lawsuit challenging the extension is ongoing; check ADA.gov.

Read the rule in plain words

What you get from each scan.

  1. 01

    Pages

    Automated WCAG Level A and AA results for each public page we reach, up to your plan’s limit.

  2. 02

    PDFs

    PDF/UA-1 results for the PDFs linked from those pages, up to 25 MB each.

  3. 03

    A ranked fix list

    Issues grouped and ranked so your team knows where to start.

  4. 04

    A report for your records

    A dated PDF report you can keep with your Title II plan records.

See what changed since your last scan.

Each new scan is compared with the one before it. The report lists issues that are new, fixed or still open. You can also export a local alert file. A hosted dashboard with emailed alerts is not live.

Example of scan-to-scan comparison. Illustrative numbers.

Pages checked
1,842
PDFs checked
312
Open issues (last scan: 232)
214
Pages we could not reach
9

Issues by WCAG criterion

  • 1.1.1 Non-text Content

    This scan
    72
    Last scan
    80
  • 1.3.1 Info and Relationships

    This scan
    31
    Last scan
    34
  • 1.4.3 Contrast (Minimum)

    This scan
    54
    Last scan
    57
  • 2.4.4 Link Purpose (In Context)

    This scan
    49
    Last scan
    52
  • 3.1.1 Language of Page

    This scan
    8
    Last scan
    9
  • Total open issues

    This scan
    214
    Last scan
    232

What we are not.

Nothing is installed on your site or servers. We do not add a widget or overlay to your pages, and we do not inject an overlay and call that compliance. We read your public pages and PDFs and write a dated report you can keep.

A staff member uses a braille display, keyboard and laptop to review a municipal website; the screen is out of focus.

What automation can't tell you.

Automated tools find only part of the problems. Manual review is still required. A scan can tell you alt text is missing. It cannot tell you whether the alt text describes the image. That takes a person. The same goes for reading order, and for whether a form works by keyboard from start to finish.

Current reports include a “What automated checks cover” section. In the older sample on this site it is titled “Current scanner coverage, for reference”. Of the 50 WCAG 2.1 A and AA success criteria, 21 have at least one rule enabled in our scan configuration (axe-core 4.14.0) and 29 have none and need manual review. A criterion with a rule is not fully covered by it.

Read coverage and limits

How to buy Docketward.

How buying works
  • Tell us your site

    Quoted by scope

    1of 3

    What we do
    You send the public URL and any scope notes.
    What you get
    We confirm what we will crawl before we start.
  • We scan and document

    Quoted by scope

    2of 3

    What we do
    Automated WCAG 2.1 AA page checks and PDF/UA-1 checks, within the agreed scope.
    What you get
    A dated report, ranked fix list, evidence record and worksheets.
  • You buy by quote

    Quoted by scope

    3of 3

    What we do
    We quote by scope and respond to RFQs and RFPs.
    What you get
    No public prices. Ask us for a sample scan or a proposal.

Buying with a purchase order.

We quote by scope. Ask us for a quote packet (scope letter, sample report and, when available, a W-9). Tell us your purchasing route. We will say up front which forms we can complete and which we cannot. We do not ask for a bond or a multi-year term.

A new product.

Docketward is a new product. We have no customer logos to show you, so we show you a sample report instead. We do not inject an overlay and call that compliance.

About and Trust

Frequently asked questions

See what a scan finds on your site.

We confirm the scope with you before we run a sample scan. You receive a dated report package. It is not a certification.

ADA Title II Compliance Enablement for Cities and Counties | Docketward

{{ sg.t }}{{ sg.t }}

See a sample report How to buy

Start here

Skip carousel

{{ railCount }}

Check our work before you talk to us.

Facts you can check

  • {{ sg.t }}{{ sg.t }}

Standards we check against

{{ sg.t }}{{ sg.t }}
{{ s.value }}

What you get from each scan.

  1. {{ t.n }}

    {{ t.title }}

    {{ sg.t }}{{ sg.t }}

See what changed since your last scan.

Each new scan is compared with the one before it. The report lists issues that are new, fixed or still open. You can also export a local alert file. A hosted dashboard with emailed alerts is not live.

Example of scan-to-scan comparison. Illustrative numbers.

{{ d.k }}
{{ d.v }}
Issues by WCAG criterion
Criterion This scan Last scan
{{ r.id }} {{ r.name }} {{ r.now }} {{ r.last }}

Issues by WCAG criterion

  • {{ r.id }} {{ r.name }}

    This scan
    {{ r.now }}
    Last scan
    {{ r.last }}

What we are not.

Nothing is installed on your site or servers. We do not add a widget or overlay to your pages, and we do not inject an overlay and call that compliance. We read your public pages and PDFs and write a dated report you can keep.

How to buy Docketward.

How buying works
  • {{ p.name }}

    Quoted by scope

    {{ p.price }}of 3

    {{ r.k }}
    {{ sg.t }}{{ sg.t }}

Buying with a purchase order.

We quote by scope. Ask us for a quote packet (scope letter, sample report and, when available, a W-9). Tell us your purchasing route. We will say up front which forms we can complete and which we cannot. We do not ask for a bond or a multi-year term.

A new product.

Docketward is a new product. We have no customer logos to show you, so we show you a sample report instead. We do not inject an overlay and call that compliance.

About and Trust