Skip to main content

Accessibility Statement

Last Updated: August 7, 2026

Trust Swiftly is committed to making our website and our identity verification platform usable by everyone, including people with disabilities. Accessibility is not a checkbox for us: our customers include federal, state, and local government programs whose users must be able to complete an identity proofing workflow regardless of how they see, hear, move, or process information.

Table of Contents

  1. Standards We Measure Against
  2. Conformance Status
  3. What We Have Done
  4. Known Limitations
  5. Accessibility Conformance Report (VPAT)
  6. How We Test
  7. Report a Barrier
  8. Formal Complaints and Enforcement

1. Standards We Measure Against

We measure this website and the Trust Swiftly platform against:

  • WCAG 2.1 Level A and Level AA — the Web Content Accessibility Guidelines published by the W3C.
  • The Revised Section 508 Standards (36 CFR Part 1194, Appendix A and Appendix C), which incorporate WCAG 2.0 Level A and AA by reference for web content, software, and electronic documents. We target WCAG 2.1 AA because it is a superset of WCAG 2.0 AA and is what most agencies now ask for.
  • EN 301 549 for customers in the European Union, which harmonizes with the same WCAG success criteria.

Section 508 applies directly to federal agencies rather than to private companies. We hold ourselves to it because agencies must procure conformant information and communication technology (ICT), and because our platform is used by members of the public who have no choice about whether to complete an identity verification.

2. Conformance Status

This website is partially conformant with WCAG 2.1 Level AA. “Partially conformant” means that most of the content meets the standard, but some content does not yet fully conform. The known exceptions are listed under Known Limitations below, along with what we are doing about each one.

We publish this status honestly rather than claiming full conformance. If you find a barrier that is not listed here, we want to hear about it — see Report a Barrier.

3. What We Have Done

Measures taken across this site include:

  • A “Skip to main content” link as the first focusable element on every page, and a single <main> landmark on every page.
  • Visible keyboard focus indicators on interactive controls, restored over legacy stylesheet rules that had removed them.
  • Body text and interface colors revised to meet the 4.5:1 contrast ratio, including the site link color, muted text, section labels, and button fills.
  • Heading levels corrected across the site templates and the article archive so the document outline can be navigated by heading.
  • Programmatic labels, autocomplete attributes, and text-based error messages on the contact form.
  • Accessible names on embedded frames, images, and icon-only controls.
  • Keyboard access to horizontally scrolling content such as wide comparison tables and code samples.
  • Support for prefers-reduced-motion, which disables animation for users who have asked their operating system to reduce motion.

4. Known Limitations

We are aware of the following limitations. Each is tracked and scheduled.

  • Video captions. Several demonstration videos embedded in blog articles are screen recordings published before our current captioning policy. They have accessible names but do not yet have synchronized captions or audio description. Where a video conveys information that is not in the surrounding article text, we are adding captions and a text summary. If you need the content of a specific video now, email us and we will send you a transcript.
  • Third-party embedded services. Our scheduling widget (Cal.com), live chat (Landbot), comment thread (Cusdis), and anti-spam challenge (hCaptcha) are supplied by third parties and rendered inside their own frames. We do not control their internal markup. hCaptcha provides an audio challenge and an accessibility cookie for users who cannot complete a visual challenge. If any of these blocks you, the contact routes below reach a human directly and do not require the widget.
  • Legacy blog content. Articles published before 2025 were authored in a rich-text editor and may contain heading levels or table structures that are not ideal. We are correcting these as articles are revised.
  • Downloadable spreadsheets. The ROI calculator offered as an .xlsx download has not yet been assessed for accessible table structure or alternative text on charts. An accessible alternative is available on request. The PDFs on this site — our federal capability statement and our customer case study — are tagged, carry a document title and language, and contain selectable text.

5. Accessibility Conformance Report (VPAT)

Federal agencies evaluate accessibility through an Accessibility Conformance Report (ACR) — a completed ITI Voluntary Product Accessibility Template (VPAT) scoped to a specific product and its support documentation, not to a vendor’s marketing website.

Contracting officers, Section 508 program offices, and prospective customers can request an ACR for the Trust Swiftly identity verification platform by emailing [email protected]. Tell us which edition you need — 508 (WCAG 2.0 A/AA), EU (EN 301 549), WCAG, or INT — and we will confirm scope and timing within five business days.

6. How We Test

Our assessment approach combines:

  • Automated testing with axe-core against the built static output of every published page on this site. Automated tools reliably detect only a portion of WCAG failures, so they are a floor and not a ceiling.
  • Source-level review of templates and stylesheets for the criteria automated tools cannot evaluate: keyboard operability, focus management, alternative text quality, link purpose in context, and error identification.
  • Document checks on published PDFs for tag structure, document title, language, and text extractability.

We are expanding this to include structured manual testing against the DHS Trusted Tester Conformance Test Process and the U.S. Access Board’s ICT Testing Baseline for Web, together with screen reader verification. Those results will be reflected here and in our ACR as they complete.

This statement was last reviewed on August 7, 2026.

7. Report a Barrier

If you encounter an accessibility barrier on this site or in the Trust Swiftly platform, please tell us. Include the page address, what you were trying to do, and the assistive technology and browser you were using, if you know them.

We aim to acknowledge accessibility reports within two business days and to give you a remediation plan or a workaround within ten business days. If a fix will take longer, we will tell you why and give you an alternative way to get the same information or complete the same task.

8. Formal Complaints and Enforcement

If you are a federal employee or a member of the public who cannot access Trust Swiftly content delivered through a federal agency, you may also raise the issue with that agency’s Section 508 program office. Federal agencies are required to have a complaint process under Section 508 of the Rehabilitation Act.

We would prefer to resolve the issue with you directly and quickly first. Contacting us does not limit any right you have to file a complaint.