Accessible Online Ballot Checklist for Election Teams

An accessible online ballot is not just a screen that passes a technical scan. It is a voting experience that lets every eligible voter review the ballot, make selections, confirm intent, and get help without giving up privacy or independence.

If preparing a member, board, union, association, or public-sector election, use this accessible online ballot checklist before you send notices or open voting. It will help you catch the practical failures that usually appear too late, such as unclear instructions, keyboard traps, unsupported assistive technology, and help desk scripts that do not match the ballot.

Start With the Voter’s Actual Path

A ballot can look clean in a planning meeting and still fail voters in the real world. The safest review starts with the full voter path, not the ballot screen alone. That path includes the notice, login, authentication, ballot review, selection, confirmation, receipt, and any support request in between.

The Department of Justice explains that voting accessibility covers the full voting process, including registration, early and absentee voting, and communication with voters with disabilities. In online elections, the same principle applies even when the election is not a government election. Accessibility is an operating requirement, not a footer on a website.

For teams using online voting software, the review should include both the platform and the election configuration. A strong platform can still be weakened by a confusing ballot title, a poorly written instruction, or a support plan that requires a voter to disclose a disability to get basic help.

The Accessible Online Ballot Checklist

Use this checklist after the ballot is configured but before voter notices are finalized. At this stage, changes are still inexpensive. After launch, every correction is harder because voters may already have seen instructions, saved links, or contacted support.

1. Confirm the voter list and ballot styles. Make sure each voter receives the correct ballot style, language option, and contest set. Accessibility starts with eligibility accuracy because a voter cannot independently correct an invisible data error.


2. Test keyboard-only navigation. A reviewer should be able to log in, move through the ballot, make selections, review choices, and cast the ballot without a mouse.


3. Run screen reader testing on the configured ballot. Do not stop at a generic platform test. Listen to the actual contest names, candidate names, ballot questions, instructions, error messages, and confirmation screen.


4. Check plain-language instructions. Tell voters what to do in direct language. Avoid legal shorthand, internal committee terms, unexplained acronyms, and instructions that appear only after an error.


5. Verify contrast, focus, and selection states. Voters should be able to see where they are, what they selected, what remains incomplete, and how to change a selection.


6. Review the mobile experience. Many voters will use a phone, including voters who rely on built-in accessibility settings. Test text resizing, orientation, scrolling, and confirmation screens.


7. Confirm privacy and independence. Support should help voters use the system without asking them to reveal ballot choices or rely on another person to complete the vote.


8. Document the test record. Keep dated notes showing what was tested, who tested it, what issues were found, and how they were resolved before launch.

This is where an experienced election operations team earns its keep. Accessibility problems are often configuration problems: an ambiguous contest label, a missing language instruction, a deadline notice that does not match the voting window, or a help desk answer that conflicts with the rules.

What to Review Beyond WCAG

WCAG conformance is essential, but it is not the whole job. WCAG helps define whether digital content is perceivable, operable, understandable, and robust. Election administrators also have to ask whether the voting process preserves voter intent, secrecy, eligibility, and a defensible record.

Practical ballot reviewers ask whether a ballot is visually clear, consistent, easy to navigate, and written in plain language. Online ballots add another layer because voters also interact with code, devices, browsers, and assistive tools.

Build Accessibility Into Support and Records

Many election teams focus on the ballot and forget the help desk. That is a mistake. When a voter encounters a barrier, the support process becomes part of the voting experience. If support is slow, confusing, or intrusive, the election may still feel inaccessible even if the ballot screen is technically sound.

Prepare scripts for common accessibility questions before voting opens. Staff should know how to guide a voter who cannot find the next button, uses a screen reader, or receives an authentication error. The answer should never require the voter to reveal a choice.

Records matter because accessibility is easier to defend when documented in election files. Keep a pre-launch signoff, issue-resolution log, support categories, and final incident summary. The record should be specific, dated, and tied to the actual election.

Frequently Asked Questions

What is an accessible online ballot?

An accessible online ballot allows voters with disabilities to read, navigate, mark, review, and cast their ballot with the same privacy and independence offered to other voters. It should work with assistive technology, clear instructions, keyboard navigation, and practical support.

Is WCAG compliance enough for an online election?

WCAG compliance is a necessary foundation, but it is not enough by itself. Election teams must also review eligibility setup, authentication, ballot secrecy, voter support, audit records, and the exact ballot configuration used in the election.

When should accessibility testing happen?

Testing should happen after the real ballot is configured and before voter notices are sent. A final check should also occur shortly before launch to confirm that links, deadlines, language options, and support instructions still match the approved election plan.

Who should review accessibility before launch?

The review should involve the election administrator, platform or operations lead, support lead, and at least one person testing with assistive technology. For higher-risk elections, consider outside accessibility review or documented user testing before launch.

The Bottom Line

Accessible online voting is not a one-time technical certification. It is a disciplined election practice: clear ballot design, tested assistive access, private support, and records that show what the team did before voters were affected.

If you are preparing an online election and want a second set of eyes on accessibility, ballot setup, and support procedures, Votem can help you review the risks before launch. Start with Votem’s accessibility approach, or contact our team before you set final voting deadlines.