Documents everyone can read, written that way from the start.

Why it exists

Agendas, minutes, notices and reports are how cities, towns, schools and nonprofits tell people what is happening. Posted as documents, they often can’t be read with a screen reader, navigated by keyboard or followed by someone who needs plain structure.

The ADA’s Title II rule now holds state and local governments’ web content, documents included, to WCAG 2.1 AA: from April 26, 2027 for those serving 50,000 people or more, and from April 26, 2028 for smaller ones and special districts. The Department of Justice set those dates in April 2026, and a lawsuit asks a court to set that extension aside.

Most accessibility problems are made while a document is written, and most checkers find them only afterwards. Ada Editor checks as you write, cites the WCAG success criterion behind every finding, and exports tagged PDF (PDF/UA-1) and HTML built from the same structure.

What we promise

• No compliance claims. Automated checks cover only part of WCAG, so Ada Editor never calls a document compliant. What needs a person is marked “Needs your call”. Our guide explains what “ADA compliant PDF” can and can’t mean.
• Your Word files stay with you. They are read in your browser; the file itself is never uploaded, only the document made from it.
• The editor is held to the standard it checks. Where it falls short, the accessibility statement says so.
• Your documents are yours. No ads, nothing sold, and the privacy notice lists everything we keep and count.

Reach a person

Signed in, send us a message from the privacy page’s form. It reaches the people who build Ada Editor.

Without an account, open an issue on Ada Editor’s GitHub repository, where the code and research are public.