Loading
People who need a legal document the most are often the least able to fight an interface to get one. Disability, injury, and illness are what put many of our users in front of a court in the first place. An inaccessible legal tool is a tool that fails exactly the people it was built for.
Last reviewed: July 30, 2026
Our target is the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA. That is the benchmark U.S. courts and settlements generally apply to websites, and it is the standard we hold new work to.
We are deliberately describing that as a target, not a claim. We have not had a full third-party audit of every page, and we are not going to tell you the site is “fully compliant” or “ADA certified” when no one has measured it end to end. There is no such certification, and a company that claims one is telling you something it cannot support.
These are measures in place today, not aspirations:
What that does not mean. Automated tools catch only a minority of accessibility problems — they can tell you a button has no name, but not whether a label makes sense or whether a flow is actually usable with a screen reader. Passing them is a floor, not proof of conformance. We have not yet completed a manual screen-reader and keyboard-only pass across the product, and we have not had a third-party audit. Until we have, treat this page as a description of effort, not a guarantee of results.
We would rather tell you what is broken than let you discover it in the middle of a filing. As of July 30, 2026, we know about the following and are actively working on them:
This list will change as we fix things and as we find more. We keep a dated remediation log alongside the code.
You will not find an accessibility widget, toolbar, or “one line of code” compliance plugin on this site, and we will not add one.
Those products promise to make a site accessible automatically. They do not. They frequently interfere with the screen readers and browser settings people have already configured, and sites running them are sued over accessibility at least as often as sites without them. In January 2025 the Federal Trade Commission took action against one of the largest overlay vendors over its compliance claims.
We would rather fix the underlying markup. It is slower and it is the only thing that actually works.
Court filing systems, clerk portals, and the courts’ own forms are outside our control and vary enormously in quality. If you hit an accessibility barrier at the filing stage rather than inside SynthCounsel, tell us anyway — we may be able to give you the document in a different format, and it helps us know where the process breaks down.
Many courts will grant accommodations to litigants with disabilities, including deadline extensions and alternative filing methods. We are a document preparation service and cannot advise you on whether to request one or what to ask for. Your court’s ADA coordinator or clerk of court is the right place to start, and our ADA accommodation request tool can help you put your own request in writing.
If any part of SynthCounsel blocked you, please tell us. You do not need to know the technical name for the problem or cite a standard — “I could not get past the second step of the answer wizard with my screen reader” is a perfect bug report.
Use the support form. Choose “Something else” as the category and start your message with “Accessibility”. Tell us the page, what you were trying to do, and — if you know it — what assistive technology and browser you were using. You do not need an account to send one.
We read every accessibility report and prioritize barriers that block someone from completing a document. If a barrier is standing between you and a filing deadline, say so in your message so we can see it. We are a small team and cannot commit to a fixed response or resolution time, so we would rather tell you that than promise a deadline we might miss.