Skip to main content

Accessibility Statement

Last Updated: March 27, 2026

Our Commitment​

SquadUp is committed to improving accessibility over time and making the product more usable for a wider range of users, devices, and assistive needs.

We aim to:

  • improve readability and clarity
  • reduce avoidable motion where practical
  • make interactive, disabled, and preview states easier to understand
  • support more accessible navigation patterns over time
  • iteratively improve alignment with WCAG standards
  • respond to reported accessibility issues in good faith

This statement describes the current state of accessibility support in the SquadUp product. It does not mean every feature is fully accessible today.

Current Accessibility Controls in the App​

Some current builds of SquadUp include an Accessibility section in app settings.

The current accessibility controls include:

Accessibility Enhancements​

This setting improves readability and clarity across selected shared surfaces, including disabled and preview-only actions.

Current effect may include:

  • stronger contrast for shared action rows and framework cards
  • clearer visual hierarchy on selected helper surfaces
  • clearer disabled badges and labels
  • better readability for action hub rows that are intentionally unavailable
  • stronger border emphasis on selected hints, toasts, and framework modals
  • roomier controls on selected buttons and header actions
  • stronger card separation on selected home surfaces
  • stronger content-card and day-row separation on selected Library and Calendar surfaces
  • explicit disabled accessibility semantics where implemented

Larger Text​

This setting increases text size on selected shared surfaces and key app headers used across the product.

Current effect may include improved readability in:

  • main screen headers
  • framework subtitles on major surfaces
  • settings rows in the accessibility/settings flow
  • shared quick action hubs
  • Quick Stash
  • Quick Win
  • Quick Framework guide surfaces
  • selected hints, toasts, and accessibility-oriented surfaces

This is broader than the initial shared-surface rollout, but it is not yet a full app-wide text scaling system.

Reduce Motion​

This setting reduces motion on selected shared transitions.

Current effect may include reduced or removed animation on:

  • floating action button ripple and snap behavior
  • selected hint and toast transitions
  • shared quick action sheets
  • selected framework modals
  • selected motion utilities already connected to the reduced-motion setting

This is not yet a full app-wide motion reduction system.

Current Accessibility Scope​

Accessibility support in SquadUp currently varies by:

  • feature surface
  • app version
  • device and operating system
  • release phase
  • whether a screen uses the newer shared component system

At this time, accessibility improvements are strongest in:

  • newer shared UI surfaces
  • major home surface headers
  • settings and support/accessibility controls
  • selected hints, toasts, and floating action controls
  • selected legal/support/settings paths

Examples of current focus areas include:

  • readable action states, disabled states, and preview states
  • larger text support on shared modal/sheet components and key headers
  • reduced motion support on selected shared transitions and floating action behavior
  • legal and support documentation access
  • clearer explanations for preview-only MVP states

Known Limitations​

Accessibility support is still in progress.

Known limitations may include:

  • not all text on all screens responds to the larger-text setting yet
  • not all animations and gesture-driven transitions respond to reduce-motion yet
  • some older screens may still rely on fixed sizing
  • some visual patterns may still depend too heavily on color or layout density
  • some feature flows may require additional screen reader review
  • support may differ between iOS, Android, web docs, and future builds

We do not currently claim that SquadUp is fully compliant with every accessibility standard across every surface.

How We Approach Accessibility Work​

Our current approach is practical and iterative.

We prioritize:

  • high-friction areas first
  • reusable components before one-off screens
  • settings that improve real usability immediately
  • clearer legal and support documentation about what is and is not supported

This means some accessibility improvements may appear first in shared surfaces before they reach every legacy or lower-priority screen.

What To Do If You Need Help​

If you encounter an accessibility issue, need help using a feature, or want to request an accommodation, contact us.

Please include as much detail as you can:

  • device type
  • operating system version
  • app version
  • screen or feature name
  • what you expected to happen
  • what actually happened

Contact:

This Accessibility Statement is provided to explain our current accessibility efforts and known limitations in plain language.

It does not create a guarantee that:

  • every feature is accessible in every release
  • accessibility support is identical across all devices and platforms
  • all assistive technologies are fully supported today
  • all future features will launch with the same accessibility coverage on day one

For the legal terms governing use of the service, please review:

Ongoing Improvements​

We expect this statement to evolve as the product evolves.

Areas we expect to continue improving include:

  • broader text scaling coverage beyond headers and shared surfaces
  • broader reduced-motion coverage beyond shared surfaces and selected controls
  • improved screen reader support
  • better accessible patterns for interactive and disabled states
  • more explicit QA and release review for accessibility-sensitive surfaces

SquadUp
Mavaro Systems LLC