Accessibility Statement

Effective date: August 3, 2026

Corrido ("we," "us," or "our") is committed to making our website and mobile app usable by as many people as possible, including people who use assistive technologies. This statement describes the accessibility of trycorrido.com and the Corrido iOS and Android apps, what we have built so far, known limitations, and how to reach us if something does not work for you.

1. Scope

This statement covers:

• Website — the public pages on trycorrido.com, including the home page, contact form, Privacy Policy, Terms of Use, and account deletion instructions. Thin utility pages that open the app (billing return, password reset, invite links) are noted separately below.
• Mobile app — the Corrido app for iPhone, iPad, and Android (Expo / React Native), including recording, library, family, account, and related in-app flows.

Third-party store listings, payment sheets provided by Apple or Google, and embedded third-party widgets (such as Cloudflare Turnstile on the contact form) are outside our direct control. Their accessibility depends on those providers.

2. Conformance status

We aim to align the website with WCAG 2.2 Level AA and to support common platform accessibility features on iOS and Android (including VoiceOver and TalkBack). We do not claim full conformance with WCAG or with any particular App Store accessibility checklist at this time.

This statement is based on an internal review of our website markup and mobile app code (including shared accessibility components and automated tests for labels, roles, and form errors). It has not been validated by a third-party audit or a full assistive-technology test pass across every screen.

3. Website accessibility

On trycorrido.com we currently provide:

• Pages marked with lang="en", unique page titles, and a consistent header, primary navigation, main content, and footer structure on marketing and legal pages.
• Landmark and section labeling on the home page (including aria-labelledby on major sections).
• Descriptive alternative text for product screenshots and App Store / Google Play badges; logos exposed with an accessible name.
• A contact form with visible labels, a polite live status region for feedback, and a honeypot field hidden from assistive technology.
• Native FAQ disclosures (details / summary), a viewport that allows zoom, and light/dark color tokens that follow the system color scheme preference.
• Visible focus styles on the mobile menu control and on contact form fields and the submit button.

Known website limitations include:

• No skip-to-main-content link yet.
• Focus styles are incomplete on many text links and primary buttons outside the contact form.
• The mobile navigation control does not yet expose an open/closed state (for example, aria-expanded).
• Smooth scrolling is enabled without a prefers-reduced-motion override.
• Some primary button and link color combinations (especially in dark mode) may not meet WCAG contrast ratios for normal text. We are tracking this for improvement.
• Billing return, password-reset, and similar bridge pages may auto-redirect into the app, which can be a sudden change of context.

4. Mobile app accessibility

The Corrido app is built with React Native accessibility APIs. Shared controls and many primary flows include accessibility labels, roles, and state. In particular:

• Primary and secondary buttons expose button roles, labels, and disabled state.
• Labeled text fields surface validation errors through invalid state, hints, polite live regions, and spoken announcements.
• Screen and section titles use header roles for screen-reader navigation.
• Bottom tabs and top-bar actions (including Back and Open account) have accessible names and selection state where applicable.
• Story tiles and library cards combine title and metadata into a single accessibility label.
• Recording controls (start, stop, pause, resume, flip camera, cancel countdown, retry) have explicit labels. The capture countdown respects Reduce Motion when enabled and announces countdown and recording-start events.
• Custom audio playback controls include Play/Pause and a scrubber with an accessibility value. Video playback uses the platform’s native media controls.
• Toasts use a polite live region; the offline banner uses an assertive live region. Decorative brand art and skeleton loaders are hidden from the accessibility tree.
• Automated unit tests cover shared UI accessibility behavior (button labels and disabled state, field errors, search labels, header roles, composite story labels, and invite step progress).

Known mobile limitations include:

• Some screens still rely on visible text alone (without an explicit accessibility label), including parts of invite-code entry, onboarding links, and a few secondary prompts.
• Reduce Motion is handled for the capture countdown; other animations (for example, progress indicators and some transitions) are not yet gated the same way.
• We have not shipped an explicit Dynamic Type / large-text layout strategy beyond React Native’s default font scaling.
• Camera preview and audio level meters are visual; they are not described as live regions for screen-reader users.
• Accessibility coverage has not been exhaustively verified with VoiceOver and TalkBack on every screen.

5. Compatibility

The website is intended to work with current major browsers and with common assistive technologies such as screen readers, keyboard navigation, and browser zoom. The mobile app is intended to work with VoiceOver on iOS and TalkBack on Android, and with system settings such as Reduce Motion where we have wired support.

Compatibility can vary by device, OS version, and assistive-technology version. If a combination does not work for you, please tell us what you use so we can reproduce the issue.

6. Feedback

We welcome accessibility feedback. If you find a barrier, cannot access content or a feature, or need information in a different format, contact us at hello@wkndbuilds.com or through our contact form.

Please include:

• The page URL or app screen where you had trouble.
• What you were trying to do.
• Your device, operating system, browser or app version, and any assistive technology (for example, VoiceOver or TalkBack).

We aim to acknowledge accessibility reports within five business days and to prioritize fixes that block core tasks such as signing in, recording a story, playing back media, or managing your account.

7. Assessment approach

As of the effective date above, accessibility has been evaluated through:

• Manual review of website HTML structure, labels, images, forms, and CSS focus / motion / contrast tokens.
• Manual review of mobile accessibility props and shared UI components in the Corrido codebase.
• Automated unit tests for selected accessibility behaviors in the mobile app.

We have not completed a formal third-party WCAG audit of the website or a full VoiceOver / TalkBack regression suite for every app screen.

8. Changes to this statement

We may update this Accessibility Statement as we improve the website and app. When we do, we will update the "Effective date" at the top of this page.

9. Contact us

Accessibility questions and barrier reports: hello@wkndbuilds.com. You can also use the contact form.