WCAG 2.1 AA · DOJ Title II Final Rule · 28 CFR §35.200

WCAG evidence your counsel can rely on.

April 26, 2027 is the federal deadline for state and local government websites to meet WCAG 2.1 AA. Automated scanners catch a fraction of real violations. Overlay widgets are being sued and fined. Parallax is the audit and continuous monitor your accessibility coordinator, web team, and outside counsel can stand behind — built for public-sector procurement realities.

Run a free preliminary audit → See pricing

Apr 26, 2027 Large-entity deadline (≥50K pop)

Apr 26, 2028 Small-entity & special-district deadline

2,014 ADA web lawsuits filed Jan–Jun 2025

$9,500 P-card-purchasable audit, fixed fee

Free resource · no email required

The 12-item ADA Title II compliance checklist for 2027 — print, mark up, share with your team.

Download PDF →

The rule

The deadline is real. The shortcuts aren't.

The Department of Justice published its Title II web accessibility Final Rule on April 24, 2024 (89 Fed. Reg. 31320), and extended the compliance dates by one year on April 20, 2026. Public entities — state and local governments, public universities, public school districts, transit authorities, special districts, and public hospitals — must conform their web content and mobile applications to WCAG 2.1 Level AA.

Enforcement is direct: DOJ investigation, OCR complaints, and private lawsuits under Title II. There is no "good faith" exemption. There is no compliance grace period after the deadline.

The two timelines that matter:

Apr 26, 2027 Public entities serving ≥50,000 people. State agencies, large counties and cities, large university systems.
Apr 26, 2028 Public entities serving <50,000 people, plus all special-purpose districts (water, transit, library, school, etc.) regardless of size.

Source: 28 CFR Part 35, Subpart H. Extension: 89 FR Doc 2026-07663 (April 20, 2026).

The shortcuts

Two paths most agencies tried first. Both fail under DOJ scrutiny.

An honest read of what's been tried so far, and why neither produces a defensible compliance posture before the deadline.

Shortcut 1

Run an automated scanner. Call it done.

Free or low-cost scanners (axe-core, Lighthouse, WAVE) flag computed-CSS contrast, missing alt text, and ARIA syntax. They cannot evaluate keyboard interaction order, ARIA state changes during user flow, focus traps inside dialogs, dynamic-content announcements, or contrast on rendered pixels behind images and gradients. WebAIM's annual audit of one million homepages consistently finds critical WCAG failures on the majority of sites scanners pass clean.

Why it fails legally: A scanner report does not satisfy DOJ's WCAG 2.1 AA standard. Plaintiffs' counsel routinely demonstrate clean-scan sites with failing user flows.

Shortcut 2

Install an overlay widget.

Overlay tools (accessiBe, UserWay, AudioEye, EqualWeb) inject JavaScript that claims to "fix" accessibility automatically. The Federal Trade Commission fined accessiBe approximately $1 million in April 2025 for deceptive WCAG conformance claims. More than 800 sites running overlay widgets were sued in 2024 alone. The overlay does not change the underlying site; it adds a UI on top that disability advocates and screen-reader users have repeatedly demonstrated does not work.

Why it fails legally: Overlays are now treated as a red flag by plaintiffs' attorneys, not a defense. Public-sector counsel will not certify a remediation plan that relies on one.

The work

Three things scanners can't do — and Parallax does on every audit.

Parallax uses the open-source axe-core engine for the machine-decidable layer (so we don't fight industry standards), then layers three deeper analyses that produce the evidence a defensible compliance program requires.

Rendered-pixel contrast analysis

We render every page in a real browser and sample the actual pixels under text — not the computed CSS color. This catches text on hero images, gradients, semi-transparent overlays, and dynamic backgrounds where contrast fails in production but passes a static scan.

Interaction traces

Parallax drives every page like a keyboard user — Tab through every interactive element, open every menu and dialog, fill every form. Focus order, focus traps, ARIA state changes, dynamic announcements, and error-recovery flows are recorded and compared against semantic markup. WCAG violations that only appear during interaction are flagged with a full session replay.

Human-reviewed issue queue

Every machine-decidable finding is triaged by a human accessibility reviewer before it lands in your remediation queue. False positives are dropped. Severity is calibrated against actual user impact. Each issue ships with a recommended fix and the WCAG success criterion it maps to. Your developers get a queue they can ship against, not a 400-row CSV they have to interpret.

The engagement

From URL to defensible compliance posture in four weeks.

Day 0

Free preliminary audit (24 hours)

Submit your top-level URL. Within 24 hours you receive a PDF preliminary report covering up to 25 pages: total WCAG violations by severity, the top five issues, the deadline you fall under, and a fixed-fee proposal for the full engagement. No credit card required.
Week 1

Full audit kicks off

P-card payment or invoice + PO. We crawl the site (up to 500 pages by default; more in Enterprise tier), run the three-layer analysis, and triage every finding through human review. You get a project channel and a named reviewer.
Week 3

Audit report + remediation roadmap

A signed PDF audit report (the artifact your counsel needs), a CSV/JSON remediation queue your developers can ship against, and a 90-day roadmap prioritized by severity × user-impact. Your accessibility statement and VPAT are drafted from the findings.
Ongoing

Continuous monitoring (optional)

Parallax Monitor runs the same three-layer analysis weekly, sends a monthly diff report, and updates your accessibility statement annually. Regressions on remediated issues fire a real-time alert to your web team. Your VPAT stays current automatically.

Pricing

Pricing without RFPs.

Audit and Monitor are priced under typical state and local government P-card single-purchase ceilings, so they can be procured directly without formal solicitation. Enterprise engagements above $25,000 go through standard cooperative purchasing or RFP — Parallax is registered with NASPO ValuePoint and Florida MyFloridaMarketPlace.

Parallax Audit

$9,500

One-time. Single domain, up to 500 pages.

● Three-layer analysis (axe-core + rendered-pixel + interaction traces)
● Human-reviewed issue queue
● Signed PDF audit report + 90-day remediation roadmap
● Drafted accessibility statement + VPAT
● P-card purchase, invoice, or PO

Buy with P-card →

Most chosen

Audit + Monitor

$13,990

First year. Renews at $4,990/yr Monitor only.

● Everything in Audit
● Weekly continuous monitoring
● Monthly diff reports + regression alerts
● Annual VPAT + accessibility-statement refresh
● Single bundled invoice — under most state P-card ceilings

Buy with P-card →

Enterprise

$25K+

Multi-domain, dedicated reviewer, full audit artifacts.

● Multi-domain crawl (no page cap)
● Named accessibility reviewer + monthly office hours
● Continuous monitoring across the portfolio
● Audit artifacts on your letterhead, ready for litigation defense
● NASPO ValuePoint, GSA MAS, or state cooperative

Request a proposal →

All prices in USD. Audit + Monitor renewal at $4,990/year is also under typical P-card ceilings. State P-card single-purchase ceilings vary; verify yours before purchase.

Free preliminary audit

See where your site stands. In 24 hours. No card.

Submit your top-level URL and the email address of your accessibility coordinator or web team lead. You'll receive a PDF preliminary report covering up to 25 pages: total WCAG 2.1 AA violations by severity, the top five issues with screenshots, the deadline tier you fall under, and a fixed-fee proposal if you want the full engagement.

Public-sector domains only (.gov, .edu, .us, .mil, .k12.<state>.us, plus public university and special-district equivalents). One audit per domain per 90 days.

Email hello@morton-digital.com with:

●Subject: "Parallax preliminary audit request"
●The URL you'd like audited
●Your name + role (ADA Coordinator, IT Director, etc.)
●Your public-sector email (.gov, .edu, .us, .mil)
●Any context on size, priorities, or your deadline tier

You'll get a PDF preliminary report within one business day. No commitment, no card.

Open email with template →

If your mail client doesn't open, write to hello@morton-digital.com directly. We don't sell or share your information.

Frequently asked

The questions our buyers actually ask.

If you have a question that isn't here, email hello@morton-digital.com and a Parallax reviewer will respond within one business day.

Can I really purchase this on a P-card? +

Yes. Audit ($9,500), Monitor ($499/mo or $4,990/yr), and the Audit + Monitor bundle ($13,990) are all under typical state and local government P-card single-purchase ceilings (commonly $10,000, sometimes $5,000 — varies by entity). We provide a vendor invoice formatted for your finance team's records.

If your entity's ceiling is below $9,500 we can split the audit across two billing cycles (audit phase + report-delivery phase) at no additional cost. Email us with your ceiling.

How is Parallax different from Level Access, Deque, or SiteImprove? +

Level Access (which now owns UserWay) targets enterprise procurement at $50K+ ACV with multi-month onboarding. Deque builds developer tooling around the open-source axe-core engine. SiteImprove sells a broader content-governance suite where accessibility is one of several modules.

Parallax is purpose-built for the mid-tier public-sector buyer who needs an audit and monitor that can be purchased on a P-card, deployed in days, and produce a defensible compliance posture before April 2027 — without an enterprise sales cycle, without an overlay, and without forcing the web team to wire up a developer-tool stack.

For enterprise-scale agencies (large state-wide systems, top-50 universities, multi-domain transit authorities), our Enterprise tier matches the incumbents on scope and adds the rendered-pixel + interaction-trace layers most don't run automatically.

What about overlay widgets — wouldn't those be cheaper? +

Overlay widgets do not modify your underlying HTML, ARIA, or content. They inject a JavaScript layer that disability advocates and screen-reader users have repeatedly demonstrated does not work. The Federal Trade Commission fined accessiBe approximately $1 million in April 2025 for deceptive WCAG conformance claims, and over 800 sites running overlay widgets were sued under the ADA in 2024.

Public-sector counsel will not certify a remediation plan that relies on an overlay. Procurement officers reading current case law are removing overlay vendors from approved-vendor lists. Cheaper is the wrong metric — defensible is the right metric.

What's actually in the audit report? +

A signed PDF report (typically 40–80 pages depending on site size) containing: an executive summary for non-technical stakeholders; a per-page conformance map; every WCAG 2.1 AA violation found with severity, the affected element, the success criterion (e.g., 1.4.3 Contrast Minimum), a recommended fix, and a screenshot or session replay; a 90-day remediation roadmap prioritized by user impact; a drafted accessibility statement matching DOJ's expectations; and a drafted VPAT (Voluntary Product Accessibility Template) for any procured systems.

The report is the artifact your counsel uses to defend an investigation, your developers ship against, and your accessibility coordinator presents to the governing body.

How does the human-reviewed queue actually work? +

Every machine-decidable finding goes into a triage queue staffed by accessibility reviewers (humans, not models). Each finding is verified against the live site, false positives are dropped, severity is recalibrated when the automated tool over- or under-states impact, and the recommended fix is checked against current ARIA Authoring Practices and WCAG techniques. Only verified findings appear in the report your team works from.

Most automated scanners ship the raw output. Most enterprise audits ship 3–5 weeks after the scan completes. Parallax ships a verified report 2–3 weeks after the audit kicks off because the queue runs continuously, not in batches.

What happens if my agency misses the deadline? +

Enforcement is direct. The Department of Justice can investigate on its own initiative, the Office for Civil Rights at HHS or Education can act on a complaint, and individuals can sue under Title II for injunctive relief and attorneys' fees. There is no statutory damages cap that limits exposure, and a single failing user flow can support a complaint.

The pattern from past Section 508 enforcement and current ADA Title III cases: agencies that have an audit, a roadmap, and a documented remediation cadence in flight are given a chance to cure. Agencies that have nothing pay outside counsel to defend the lack of evidence.

Who is behind Parallax? +

Parallax is built and operated by Morton Technology Consulting LLC, a Florida-registered software firm. The firm has been working in IT and software since 2024 and currently delivers solutions for public-sector and enterprise clients. Parallax is the firm's flagship accessibility product, designed against the DOJ Title II Final Rule from the day it was published.