Accessibility Statement

1. Our standard

Stupid Simple Fitness aims to conform with the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. WCAG defines requirements for designers and developers to improve accessibility for people with disabilities, and is the de facto standard most modern accessibility law references.

2. What we've built toward

• Keyboard. All interactive controls are reachable and operable with a keyboard. Visible focus styles are not removed.
• Screen readers. Semantic HTML is the default. Form fields have labels. Buttons say what they do. Decorative graphics are hidden from assistive tech.
• Color and contrast. Body text meets the 4.5:1 contrast ratio against its background; large display text meets 3:1.
• Type and zoom. Layouts reflow to at least 200% zoom without losing content or function.
• Motion. We do not autoplay video or run distracting motion. We respect prefers-reduced-motion.
• Plain language. Microcopy and error messages aim to be specific and actionable.
• Forms and errors. Errors are described in text, not by color alone, and are associated with the offending field.

3. Where we know we're not there yet

Honesty over polish. As of the date at the top of this page, areas we are still working on:

• Some early flows have not yet been independently audited by someone who uses a screen reader as a primary input.
• Mobile-specific gesture alternatives for a couple of dashboard interactions are in progress.
• The under-the-hood reasoning views are dense; we are working on a more linear, screen-reader-friendly presentation.

If you hit something we haven't listed, that's on us, not on you. Please tell us.

4. Tell us when we miss

If something on the Service blocks you, frustrates you, or just plain doesn't work with the assistive tech you use, email help@stupidsimplefitness.com. Useful detail to include if you can:

• The page or screen.
• What you were trying to do.
• What happened (or didn't).
• Your browser, OS, and assistive technology (e.g., "Safari 17 on macOS, VoiceOver" or "Chrome on Android, TalkBack").

We aim to acknowledge accessibility reports within 5 business days and to come back with a fix or a plan within 15 business days. Where a fix needs more time, we will say so and tell you what we're doing in the meantime.

5. Third parties

Some parts of the Service are powered by third-party tools (for example, the payment processor's checkout). We do our best to choose vendors with strong accessibility commitments, but we do not control their interfaces. If you hit a barrier in a third-party flow, tell us anyway; we may be able to provide an alternative path or escalate to the vendor.

6. This statement

This statement covers the web application at stupidsimplefitness.com and any sub-applications operated by Linchpin Industries under that name. We update this page when our accessibility posture changes meaningfully.