Accessibility Statement

Happy Songs USA Corp. ("Happy Songs," "we," "us," or "our") is committed to making its products usable by everyone, including people with disabilities. This Accessibility Statement describes that commitment, the standard we build to, the accessibility features of our products, the current conformance status, and how to reach us if you encounter a barrier.

This Statement is issued for the United States and Mexico, the markets in which Happy Songs currently operates. Where our products are offered in other regions, additional region-specific accessibility information may be published separately.

Throughout this Statement, "the Customer" means the adult account holder (18 or older, or the age of majority where they live) who registers for, operates, and pays for the Service. The Service is operated by the adult Customer; a child does not register for, hold an account with, operate, or provide information to the Service. Because a song is typically created for a child, and may be played to a child who is present as its listener, we design the App's content to be understandable to a broad range of people — including children present when a song is played, and people with disabilities. Consistent with that, we keep our content age-appropriate and do not market to, advertise to, track, or profile children: a child is a beneficiary of the Service, not a user of it.

Incidental, parent-supervised listening by a child does not make the Service directed to children. As with any general-audience app, an adult Customer may let a child hear a song on the adult's own device; that incidental, supervised listening is not a child "using" or "accessing" the Service as a user, and it does not convert an adult-operated Service into one directed to children within the meaning of the U.S. Children's Online Privacy Protection Act (COPPA) or comparable Mexican protections. Three facts about how the product is built hold this line: (1) we build no profile of the child — we hold only the first name the adult provides; (2) we direct no feature, screen, content, character, or message at a child — there is no child login, no child-facing mode, and nothing that invites a child to act, earn, or transact; and (3) we collect no data from the child — every input is provided by, and the account is operated by, the adult Customer. To be accurate and not overstate: a child's first name is processed, with the adult's parental consent, and we still do not market to, advertise to, track, or profile a child. If a future feature were to speak to a child or be operated by a child, that would change this analysis and we would re-assess it before that feature ships.

1.Our accessibility commitment

We are working to conform to WCAG 2.2 Level AA across the Service. WCAG is the internationally recognized technical standard for digital accessibility (also adopted as ISO/IEC 40500 for earlier versions) and is the benchmark we treat as our build target in every market in which we operate.

Accessibility is an ongoing effort. We build accessibility into our design system, our components, and our development process rather than treating it as a one-time exercise, and we review our conformance on a recurring basis (see Sections 3 and 11).

2.Scope

This Statement applies to the following surfaces of the Service:

Third-party platforms and tools that we do not control — for example, the operating-system app stores, a device's own assistive technologies, or third-party payment interfaces presented by Apple or Google — are outside the scope of this Statement. Their accessibility is governed by the respective provider.

3.Conformance standard and current status

WCAG 2.2 defines three levels of conformance: A, AA, and AAA. Our target is Level AA.

• Current status: partially conformant. "Partially conformant" means that some parts of the Service do not yet fully meet the standard. We are actively identifying and remediating gaps.
• Assessment method: self-evaluation. Our current conformance posture is based on our own internal review against WCAG 2.2 Level AA. We have not yet completed a third-party accessibility audit. We will update this Statement, including the assessment method and dates, when a further or independent evaluation is completed.
• We do not claim full conformance. We state our status honestly so that people who rely on assistive technology can set accurate expectations and so that we maintain a good-faith record of continuous improvement.

We build every new surface to WCAG 2.2 Level AA, including the criteria introduced in version 2.2 (for example, accessible authentication that does not depend on a cognitive-function test, minimum target sizes for controls, a single-pointer alternative to any dragging movement, visible and unobscured keyboard focus, consistent help, and no redundant re-entry of information already provided in a flow).

4.Accessibility features

The Service currently includes the following accessibility features. Because the Service is under continuous development, specific features may be added or changed over time (see Section 11).

• Lyrics as a complete text alternative for every song. Each Happy Songs song is audio-only media. Because our songs' lyrics are produced as text before the audio is generated, we are able to present a complete and accurate written version of the song. We display those lyrics as on-screen text in the player so that people who are Deaf or hard of hearing, people who prefer to read, and people using screen readers can access the full content of a song. Lyrics can be read in the App without playing the audio, with in-app text sizing and screen-reader support. (See Section 5 for how this works within our in-app, closed-ecosystem model.)
• Assistive-technology support in the player. The lyric text is exposed to assistive technology as real text (not as an image), so that screen readers such as VoiceOver (iOS) and TalkBack (Android) can read it aloud.
• Operable, labeled media controls. Play, pause, seek, and volume controls are reachable, labeled, and operable; audio does not auto-play in a way that cannot be stopped.
• Keyboard operability and visible focus on interactive controls where a keyboard or switch interface is used, with a visible focus indicator.
• Text resizing and reflow without loss of content or function, respecting the device's larger-text and Dynamic Type settings.
• Color contrast meeting Level AA thresholds, driven by our design system, and no reliance on color alone to convey meaning.
• Clear labels and error messages on the sign-up, account, subscription/checkout, and song-creation forms.
• Reduced-motion support, honoring the device's reduce-motion setting for animations and transitions.
• Consistent help and navigation across screens.

5.Lyrics, assistive technology, and our in-app model

Happy Songs delivers songs, lyrics, and cover art through in-app access only. A Customer receives a personal, non-exclusive, revocable license to access and play a song inside the App; a song is not a downloadable or exportable file, and the Service does not offer a lyric file export or download (for example, .txt or .lrc). This is explained in full in our Terms of Service and Acceptable Use Policy. This Section explains how accessibility works within that model, because the two are fully compatible.

• The text alternative is satisfied by in-app rendering. The accessibility standard requires that a text alternative to audio be available to the user through the product — it does not require that the text be exportable as a separate file. Presenting the lyrics as accessible on-screen text, readable in the App and exposed to assistive technology, fully meets that obligation with no download path.
• Using assistive technology to read a song's lyrics is a supported accommodation — not "extraction." Having your screen reader or other assistive technology read the on-screen lyrics aloud, and having the App expose that text programmatically to assistive technology, are permitted and encouraged accessibility uses. They are expressly not the "extraction," copying, re-hosting, or circumvention that our Acceptable Use Policy prohibits. The prohibited conduct is removing a song, its lyric text, or its cover art from the App — for example ripping or re-encoding the audio, defeating access controls, or copying, re-hosting, or sharing content outside the App. Reading content through assistive technology, for accessibility, is not that conduct.
• Programmatic and on-screen exposure of lyric text always works, regardless of product choices. Whether the App offers a general-purpose "copy lyrics" control is a separate product decision (currently off, to remain consistent with our in-app model). Independent of that decision, assistive-technology access to the lyric text is an accessibility obligation and will function.
• A song is not unique to one Customer. Because the personalized element of a song is limited to a first name that is filled in, another Customer creating a song for a person with the same first name may receive the same song. This does not affect your ability to access and play, or to read the lyrics of, the songs available in your account.

If any accessibility need cannot be met within the App — for example, if you require content in an alternative accessible format — please contact us using the details in Section 9, and we will work with you to provide a reasonable accommodation.

6.Technologies and compatibility

Accessibility of the Service depends on the following technologies being supported by your device and assistive technology. We aim to support recent versions of:

• Screen readers: VoiceOver (iOS) and TalkBack (Android).
• Operating-system accessibility settings: larger text and Dynamic Type, increased contrast, and reduced motion.
• Web browsers: current versions of the major mobile and desktop browsers, for our web surfaces.

Our accessibility testing to date is based on internal evaluation using the assistive technologies above. We do not overstate our testing coverage: where a particular assistive technology or configuration has not yet been formally tested, we do not claim conformance for it, and we welcome reports (Section 9) that help us prioritize.

7.Known limitations

Despite our efforts, some content may not yet be fully accessible:

• Because our conformance status rests on a self-evaluation and a full accessibility audit has not yet been completed, some barriers may exist that we have not yet identified. We treat identified barriers as remediation items and prioritize them.
• The song audio itself is AI-generated and is not separately narrated or captioned in a video sense; the on-screen lyrics are the text alternative for the audio (see Sections 4 and 5).
• Certain non-essential animations or illustrations may not yet have complete text alternatives on every surface.

We will update this Section as our self-evaluation and any subsequent audit identify specific items, and as we remediate them.

8.Privacy of accessibility requests and data minimization

Accessibility and privacy work together in the Service.

• You do not need to disclose a diagnosis. To report an accessibility barrier or request an accommodation, you do not need to tell us your medical condition, disability, or diagnosis. We do not ask for, and do not want, health, biometric, or other special-category information. Please describe the barrier, not your medical situation.
• Data minimization in the product. About the person a song is for, the Service stores only a first name — no surname, no age or date of birth, no profile, and no precise location. When we handle an accessibility request, we collect only the information needed to respond to you and to reproduce and fix the issue (such as the screen involved and the device or assistive technology you were using).

Our handling of any personal information you provide is governed by our Privacy Notice.

9.Feedback and contact

We welcome your feedback on the accessibility of the Service. If you encounter a barrier, or if you need content in an alternative accessible format, please contact us:

• Email: support@happysongs.ai
• In the App: Settings → Help → "Report an accessibility problem" (where available).
• Postal (Mexico, operating office): Happy Songs USA Corp., Calle Tijuana 22-1, Col. Del Valle, C.P. 03100, Benito Juárez, Ciudad de México, México.
• Postal (United States, registered office): Happy Songs USA Corp., 8350 Ashlane Way, Suite 103, The Woodlands, TX 77382, United States.

To help us respond, please tell us the page or screen where the problem occurred, what happened, and the device and assistive technology you were using. We aim to acknowledge accessibility reports within [5] business days and to provide a substantive response or a workaround as promptly as we reasonably can. We keep a record of accessibility reports and their resolution as part of our continuous-improvement process.

10.Enforcement and escalation

If you are not satisfied with our response, you may pursue the remedies available where you live.

United States. You may contact the U.S. Department of Justice, which enforces the Americans with Disabilities Act (ADA), through its ADA information line and website (ada.gov). If you are in California, you may also have remedies under the Unruh Civil Rights Act and may contact the California Civil Rights Department. You may also contact the Attorney General of your state.

Mexico. Mexico is a party to the United Nations Convention on the Rights of Persons with Disabilities, and Mexican law protects against discrimination, including the denial of reasonable accommodations, under the Constitution (Article 1), the Ley Federal para Prevenir y Eliminar la Discriminación, and the Ley General para la Inclusión de las Personas con Discapacidad. If you believe you have experienced discrimination on the basis of disability, you may file a complaint with the Consejo Nacional para Prevenir la Discriminación (CONAPRED). Consumer-service concerns may be raised with the Procuraduría Federal del Consumidor (PROFECO).

Other regions. Where the Service is offered outside the United States and Mexico, additional region-specific accessibility rights and enforcement authorities may apply and are addressed in the accessibility information published for those regions.

11.Changes to this Statement and to accessibility features

We may update this Statement, and we may add, change, or discontinue features of the Service, including accessibility features, as the Service evolves. Any such change is prospective: it applies going forward and does not retroactively affect access you have already paid for. Where the law requires notice of a change (for example, of a change to subscription pricing), we will provide it, and you may cancel in accordance with our Terms of Service. We review this Statement on a recurring basis and after significant releases of the Service, and we update it to reflect the Service as it actually operates.

12.Governing language

This Statement is issued in English as the authoritative master text. A Spanish-language (Mexico) version is provided for users in Mexico. For consumers in Mexico, the Spanish-language version governs to the extent required by Mexican consumer-protection law; in all other cases the English master text governs in the event of any conflict. The Spanish-language version is available at [URL].

13.Related documents

This Statement should be read together with our Terms of Service, Privacy Notice, Acceptable Use Policy, and AI Disclosure, which describe our in-app, closed-ecosystem song model, our data practices, our acceptable-use and anti-circumvention rules, and how our songs, lyrics, and cover art are generated.

14.Statement details

• Provider: Happy Songs USA Corp., a Texas C-Corporation, operating from Mexico.
• This Statement was prepared on: [preparation date].
• Preparation method: self-evaluation against WCAG 2.2 Level AA.
• This Statement was last reviewed on: [review date].
• Next scheduled review: [next review date, or upon a major release of the Service].
• Version: 1.0.