Last updated · 2026-09-01
Accessibility statement
United States · Maryland. WCAG 2.2 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
57Million LLC designs the Splntr Service at splntrapp.com to meet the Web Content Accessibility Guidelines (WCAG) 2.2, 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 conformance with 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. Every item is verified by an engineering-perspective sweep (see “Verification trail” below) and is 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 Control signal paths: analytics and survey prompts are silenced when either is detected, so assistive-tech users aren’t re-identified.
- Locale-aware placeholder text in 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.
Verification trail — 2026-09-01 sweep
On 2026-09-01 we ran an engineering-perspective static audit against WCAG 2.2 Level AA covering the app routes under app/ and every shared component. Confirmed working:
- Skip-to-content link renders on every page via the root layout.
<main>landmark present on the unauthenticated homepage,/settings,/groups, all authenticated app pages, and every legal page (via the sharedLegalPagewrapper).<html lang="en">in the root layout; locale switch also updates the attribute so screen readers can pick the right voice.prefers-reduced-motionguards confirmed for the branded animations (marquee, tour-pulse, fluent-emoji, ken-burns, hub rotations, coach-bounce and the rest). The 2026-09-01 sweep found one custom keyframe (coach-bounce) missing its guard and closed it in the same commit.- Group-avatar images are marked with
alt=""plusaria-hidden="true"so screen readers skip them rather than announcing “graphic” with no useful label. - Colour contrast: the subgroup report and group report were using
text-white/35on secondary numeric cells (~4.1:1 on pure black, marginally failing AA). Bumped totext-white/50in the same commit for a comfortable ~6.4:1. - First-party analytics beacon (see Privacy §5c) skips capture entirely when the browser signals DNT or Global Privacy Control, so assistive-tech users aren’t re-identified through session metadata.
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:
[email protected]
We aim to respond within 5 business days.
Date of this statement
Prepared on 2026-04-23. Last reviewed 2026-09-01 (engineering-perspective sweep; four items closed the same day). Next review scheduled within 12 months or following any material change to the Service, whichever is sooner.