Accessibility Statement
marshal should work for everyone who uses it, including people who rely on screen readers and other assistive technology. This statement records where the app stands today and what still needs work.
Conformance status
marshal targets Web Content Accessibility Guidelines (WCAG) 2.2 Level AA. WCAG 2.2 is the current W3C standard (published October 2023) and is backward-compatible with WCAG 2.1 AA — the level referenced by the U.S. Department of Justice’s 2024 ADA Title II rule — so targeting 2.2 AA also covers 2.1 AA.
As of July 2026, marshal partially conforms to WCAG 2.2 Level AA. “Partially conforms” is the status defined by the W3C for content that meets many but not all applicable success criteria — we do not claim full conformance. Conformance is strongest on iOS and Android, which are built on the platform accessibility frameworks; web accessibility is in active development. The specific gaps are listed under Known limitations below.
What works today
- Screen readers — primary user flows (sign in, join group, browse announcements, send messages, RSVP to events) are built with screen-reader roles and labels for iOS VoiceOver and Android TalkBack; device screen-reader verification is ongoing.
- Form fields — nearly all text inputs have a programmatic label.
- Interactive controls — buttons, tabs, and toggles announce their purpose and state.
- Bottom navigation — each tab announces its name and dynamic state (e.g. “Chat, 3 unread messages, tab”).
- Color contrast — body text meets WCAG AA contrast ratios on dark backgrounds.
- Web language — our web version declares its content language for screen readers.
- Visible focus indicators (web) — buttons, links, and interactive controls show a visible focus ring when navigated by keyboard.
- Reduced motion — core animations (loading skeletons, spinners, toasts, and banners) and screen-to-screen navigation transitions honor the operating-system “reduce motion” setting.
- Dialog focus management (web) — opening a dialog moves keyboard focus into it, keeps focus within it while open, and returns focus to the control that opened it when it closes.
- Descriptive image labels — images in chat, member profiles, and events carry contextual labels (e.g. “Jordan Lee, profile photo” or “Photo attachment”) rather than a generic “Photo.”
- Error announcements — inline form validation errors across the app’s forms (sign in, password reset, payments, two-factor sign-in, identity re-verification, announcements, and live-event forms), along with all toast notifications and load-error messages, are announced by screen readers as they appear.
Known limitations
We disclose what does not yet conform so users can decide whether marshal meets their needs:
- Keyboard navigation on web — dialogs now trap and cycle focus, but Tab/Enter navigation still has gaps in a few custom controls. Target fix: Q3 2026.
- Image content descriptions — images now carry contextual labels, but user-uploaded photos are described by their context (who posted them, or where they appear) rather than their visual content. Target fix: ongoing.
- 200% text scaling — has not been fully tested across all screens. Some layouts may break at the largest accessibility text sizes. Target fix: Q4 2026.
Testing approach
Our accessibility work is informed by:
- Direct code review against WCAG 2.2 success criteria.
- Manual VoiceOver/TalkBack verification is in progress.
- Contrast calculation against our design tokens.
We have not yet conducted formal testing sessions with assistive-technology users; this is planned for Q3 2026 before our public launch.
Standards and frameworks
- WCAG 2.2 Level AA (target conformance level)
- Americans with Disabilities Act (ADA) Title III — marshal aims to be accessible to users with disabilities in line with the spirit of the ADA, recognizing the evolving regulatory landscape for mobile applications.
- Section 508 of the Rehabilitation Act — relevant when marshal is used by U.S. federal agencies or recipients of federal funds.
- Apple Human Interface Guidelines and Android Material Design Accessibility for platform-specific patterns.
Feedback and assistance
Report an accessibility issue
If you encounter an accessibility barrier in marshal, or if you need assistance accessing any content or feature, please contact us. We aim to respond within 5 business days.
When reporting, please include: the page or screen where the issue occurred, what you were trying to do, the assistive technology you were using (if any), and your device and browser/app version.
Formal complaints
If you are dissatisfied with our response, you have the right to file a formal complaint:
- U.S. Department of Justice ADA Information Line: 1-800-514-0301 (voice) or 1-833-610-1264 (TTY) — ada.gov/file-a-complaint
- Federal Communications Commission (FCC) Disability Rights Office for issues related to accessibility of communications services.
Statement preparation
This statement was prepared on and last updated on , following a code-grounded accessibility review and remediation — adding visible keyboard focus indicators on web, dialog focus management (focus-in, focus-trap, and focus-return) across the app’s dialogs, reduced-motion support in core animations and screen transitions, screen-reader announcement of validation errors across the app’s forms (completing the form-error work previously listed as a known limitation), and descriptive labels for images in chat, member profiles, and events. We review and update this statement at least quarterly. The methods used to evaluate accessibility include self-evaluation against WCAG 2.2 criteria, in-progress manual VoiceOver/TalkBack verification, and color contrast analysis against published thresholds.