Skip to content
Tallyfy

Accessibility statement

We want everyone to use these docs

Section titled “We want everyone to use these docs”

Tallyfy’s product documentation should work for everyone, including people who browse with a keyboard alone, a screen reader, screen magnification, voice control, or another assistive technology. This page explains how accessible the docs are today, what we’ve built in, and how to reach us if something gets in your way.

How accessible these docs are

Section titled “How accessible these docs are”

These docs aim to meet WCAG 2.2 Level AA. That’s the accessibility standard most governments and large buyers ask for, and it’s the same level Tallyfy targets across the rest of the product.

Today the documentation site meets that level, and we don’t know of any outstanding issues. We recheck this as we add and change pages, so it stays true over time.

What’s built in

Section titled “What’s built in”

You don’t have to switch any of this on. It’s part of every page:

  • You can reach and operate every link, button, and menu with the keyboard alone.
  • Headings, lists, and tables are marked up so a screen reader announces them correctly.
  • Text and controls meet AA contrast targets in both light and dark mode.
  • Links say where they go, so they still make sense when read on their own.
  • Diagrams carry a text description, and none of them flash or loop.
  • Footnote markers and the copy buttons are large enough to tap on a phone.
  • Dark mode and your browser’s text zoom both work without breaking the layout.

Known issues

Section titled “Known issues”

We don’t currently know of any accessibility problems on these docs. We recheck as we add and change pages, and if you run into something that’s hard to use, please tell us (the next section shows how). We treat it as a bug.

Tell us about a problem

Section titled “Tell us about a problem”

Found a page that’s hard to read or use? Email us at support@tallyfy.com. Tell us the address of the page and what went wrong, and add the browser or assistive technology you were using if you can. We read every message, and we’ll fix the page or get you the same information another way.

More about Tallyfy and accessibility

Section titled “More about Tallyfy and accessibility”

This page covers the documentation site. For accessibility across the rest of Tallyfy, and to request a full accessibility conformance report (a VPAT), see Tallyfy’s main accessibility page at https://tallyfy.com/legal/accessibility/ ↗.

Technical details

Section titled “Technical details”

For anyone who wants the specifics: the docs are built with standard HTML, CSS, and JavaScript, and we use ARIA only where a plain HTML element won’t do the job. We test against WCAG 2.2 Level A and AA with a mix of automated and manual checks. The automated checks run the axe testing engine in both light and dark mode. The manual checks cover keyboard-only navigation and a review of the accessibility tree that screen readers read from. We test in current versions of Chrome, Firefox, Safari, and Edge. This statement was last reviewed in June 2026.

Section titled “Related articles”

Pro > Miscellaneous

Find resources beyond Tallyfy’s core workflow tools. Topics include company background, support…

Pro > Compliance

Tallyfy maintains a current SOC 2 Type 2 attestation. Bank-level encryption (TLS 1.2+ and…
Get in touch
About Tallyfy