Title II Rules for Third-Party Online Election Vendors

When a public entity hires a vendor to host an election portal, the vendor may run the technology, but the public entity still owns the voter’s access to its program. Under the Department of Justice’s Title II web and mobile accessibility rule, covered state and local entities must address content and apps they make available directly or through contractual, licensing, or other arrangements.

That distinction matters well before a ballot goes live. This guide explains how to assign responsibility for an accessible online election, build meaningful vendor requirements, and test the complete voter journey rather than a single ballot screen.

The Voter Sees One Election Experience

From a voter’s perspective, there is no dividing line between the election office’s website and a vendor-hosted voting portal. A notice on the public entity’s site links to eligibility information. An email directs the voter to authenticate. The voter reviews candidates, makes selections, receives confirmation, and may contact support. If a keyboard trap, inaccessible PDF, unreadable error message, or support barrier appears anywhere along that path, the election experience has broken down.

For covered state and local government entities, the current Title II rule uses WCAG 2.1 Level AA as its technical standard. The Department of Justice extended the implementation date to April 26, 2027 for entities serving populations of 50,000 or more, and to April 26, 2028 for smaller entities and special district governments.

The practical lesson applies even outside that rule’s direct scope. An accessible election is an operating discipline. Assigning every screen to a different owner invites gaps at the handoffs. Treat the voter journey as one service, then decide who is accountable for each component.

Start With a Responsibility Map, Not a Vendor Promise

A vendor’s accessibility statement, audit report, or VPAT can inform procurement. It cannot tell you whether your notices, candidate statements, uploaded documents, eligibility workflow, help desk, and custom configuration work together for voters. That is why a short responsibility map should exist before configuration starts.

Put a named person beside each line. This prevents gaps when communications staff publish content, an election administrator configures the portal, and a contractor controls the hosted application.

Put Accessibility Controls in the Election Agreement

Broad language promising an “accessible platform” leaves too much to interpretation during a compressed election calendar. The contract or statement of work should name the standard, the relevant election functions, the evidence to be delivered, and the cure process for defects. It should also cover updates made after the original review. An accessible login page does little good if a last-minute candidate document or confirmation screen creates a barrier.

Use this pre-launch checklist with your vendor and internal team:

1. Name the standard. For covered Title II entities, specify WCAG 2.1 Level AA and identify the portal, communications, downloadable materials, and support touchpoints in scope.


2. Request function-level evidence. Ask what was tested for authentication, ballot navigation, error handling, review, submission, and confirmation. A generic product claim is not a test result for your election.


3. Set a change-control rule. Require accessibility review when ballot templates, branding, integrations, content, or authentication steps change.


4. Define remediation timing. Decide who triages an issue, who communicates with affected voters, and what accessible alternative is available if a defect cannot be corrected immediately.


5. Keep the record. Retain test results, issue logs, approvals, and voter-support outcomes with the election file.

A managed workflow should make this evidence easy to find. The right election operations process gives administrators checkpoints before the voting window, not an argument after it.

Test the Whole Journey With Real Election Content

Automated scans find obvious problems, but they do not answer the questions that matter during an election. Can a keyboard user move through each contest predictably? Does a screen reader announce the candidate, office, selection state, and error? Can a voter recover from an expired credential and verify confirmation?

Run scenario-based testing before notices go out. Start at the page where the public entity announces the election. Follow the link to eligibility information, open the actual candidate materials, sign in using the real authentication path, complete a test ballot, and request help. Include a keyboard-only pass, a screen-reader pass, zoom and reflow checks, and a mobile pass. If your election permits multiple voting channels, verify that the transition to phone or assisted support is clear and preserves ballot secrecy.

Testing should include the documents your team supplies, not only the platform. The U.S. Election Assistance Commission treats accessible electronic communications as part of election administration, and its resources span registration, voting, and voter information. That wider lens is useful for organizations building a credible accessibility program around online elections.

Frequently Asked Questions

Does a hosted vendor make the public entity exempt from Title II accessibility duties?

No. The DOJ rule addresses web content and mobile apps that covered state and local government entities make available directly or through contractual, licensing, or other arrangements. A vendor can perform technical work, but the public entity should govern the service it offers to voters.

Is a VPAT enough to approve an online election platform?

No. A VPAT can be useful procurement evidence, but it does not test your candidate documents, voter notices, configured authentication flow, support process, or last-minute changes. Treat it as one input to an election-specific acceptance review.

Should we require WCAG 2.2 if Title II names WCAG 2.1 Level AA?

The DOJ Title II rule identifies WCAG 2.1 Level AA as the technical standard for covered public entities. WCAG 2.2 adds success criteria and is backward compatible in most practical planning; a vendor may build to it, but your contractual requirement should state clearly which standard governs acceptance.

When should accessibility testing happen?

Begin during procurement or configuration, then repeat it after real election content is loaded and before voter communications are sent. Test again when material changes affect the path to registration, authentication, ballot completion, or support.

The Bottom Line

Outsourcing an election portal does not outsource the voter’s experience. The strongest programs define responsibilities early, require evidence that matches the configured election, and test every step a voter must take to participate independently.

If your team is preparing a hosted election and needs a defensible accessibility handoff plan, talk with Votem’s election team before you set the voter-notice date. A clear division of work now is far less costly than repairing access during an active vote.