Last updated · 2026-04-23
Accessibility statement
United States · Maryland. WCAG 2.1 AA as our conformance target. This statement is maintained to match what is actually in the code — not what we hope to ship. See Limitations.
Conformance target
Squarekin LLC designs the Squarekin Service at edvd.vpttips.com to meet the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA as published by the W3C Web Accessibility Initiative. We align our interfaces, keyboard handling, and semantic markup against those criteria as the baseline for every new feature.
We are not presently claiming conformancewith Section 508 of the Rehabilitation Act or Title III of the Americans with Disabilities Act. A formal, independent audit has not yet been completed, and no Voluntary Product Accessibility Template (VPAT) has been published. Federal procurement offices should treat the Service as “Partially Supports” pending that audit.
What is in place today
The following measures are implemented in the code as of the date above. They are necessary but not sufficient for full conformance.
- Skip-to-content link on every page and semantic landmarks (
<nav>,<main>,role="banner",role="contentinfo"). - Focus-visible outlines on interactive elements using the
:focus-visiblepseudo-class (keyboard users see an outline; mouse users do not get spurious rings). aria-label/titleon icon-only buttons across the bar, nav, and forms.- Dynamic
<html lang>anddir— the document language and text-direction update when a user changes locale, supporting right-to-left scripts (Arabic, Hebrew, Persian, Urdu). prefers-reduced-motionhonored globally — animations and transitions collapse to near-zero duration when the OS-level preference is set. Users can also opt in from/settings.- Do Not Track and Global Privacy Controlsignal paths: analytics and survey prompts are silenced when either is detected, so assistive-tech users aren’t re-identified.
- Locale-aware placeholder textin form inputs — examples (city names, payment apps, currencies) adapt to the visitor’s region so screen readers announce examples that make sense in context.
- Toast popups (form-validation feedback, success confirmations) carry
role="status"and live in anaria-live="polite"region so assistive tech announces them without interrupting the current task.
Limitations — what is not yet verified
We are being explicit so you can make an informed decision. The following items are in progress or outstanding:
- No independent third-party audit has been performed. Our conformance claims are self-assessed.
- pa11y-ci runs in CI on every push but only against the marketing pages — the authenticated app surfaces (groups, expenses, trip planner) are not yet covered by an automated audit.
- No VPAT has been published. Federal-procurement requests for a completed VPAT 2.5 document will not be met until a formal audit is scheduled.
- Screen-reader verification against JAWS and NVDA (Windows) has not been completed. VoiceOver on macOS/iOS has received spot checks only — it has not been a line-by-line pass.
- Color-contrast ratios for the full palette have not been measured and documented. Typographic pairings are designed to meet 4.5:1 for body text and 3:1 for large text, but there is no audit trail for this yet.
- Keyboard navigation in custom controls(the contact picker chip list, the trip planner’s travel-mode radios, the live-trip waypoint editor) has not been formally tested for focus containment and Escape-key handling.
- Leaflet map (trip planner) renders an interactive canvas of OpenStreetMap tiles with marker pins. Keyboard navigation is partial; screen readers announce only a static label per pin. Distance / duration / mode are also surfaced as plain text in the summary card above the map so the route information stays available without the visual.
- Third-party embeds— receipt-OCR uses Anthropic’s Claude API server-side (no embed). Map tiles come from openstreetmap.org. We cannot warrant the accessibility of those external services.
Our commitment to close the gap
We publish a monthly internal review of accessibility findings from the Padires static scan and keep this page synchronized with what the code actually does. If federal procurement requires a completed VPAT 2.5 and independent audit, contact us at the address below and we will scope a schedule with an accessibility consultancy (Deque, Level Access, TPGi are our shortlist).
Feedback & assistance
If you have difficulty using any part of the Service, need an alternative format, or want to report an accessibility issue, contact us at:
accessibility@squarekin.com
We aim to respond within 5 business days.
Date of this statement
Prepared on 2026-04-23. Last reviewed 2026-04-23. Next review scheduled within 12 months or following any material change to the Service, whichever is sooner.