Accessibility

Accessibility Statement

Last updated: May 25, 2026

Mycro is built by one person who wants this site and the app to work for as many people as possible. Accessibility is a baseline, not a feature.

1. Standard we aim for

Our target is conformance with the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA. We use this as a yardstick, not a final destination — accessibility is ongoing work.

2. What we've done

• Semantic HTML across the site (real headings, lists, links, and landmarks)
• Visible focus states on interactive elements
• Color contrast meeting WCAG AA on body text and UI
• Forms with labels, error messaging, and keyboard support
• Reduced reliance on JavaScript — most pages work fully with JS disabled
• Responsive layout that works at 320px and up, and at 200% zoom

3. The mobile app

The Mycro iOS app uses native UIKit / SwiftUI components, which inherit Apple's accessibility infrastructure: VoiceOver labels, Dynamic Type for font sizing, and full keyboard / switch-control support. We test the most-used flows (logging weight, logging your food, viewing the trend) with VoiceOver before each release.

4. Known limitations

We're aware of work still to do. As of the date above:

• Some long-form pages do not yet have a "skip to content" link
• The phone-screenshot section on the homepage is decorative; alt text describes what's shown but the image is not interactive
• Custom form styling has not been tested in every assistive-tech / browser combination

If you find an issue we haven't listed, please tell us — see Section 6.

5. Third-party content

Some content embedded on or served by the Site comes from third parties (fonts from Google Fonts, hosting from Netlify). We do our best to choose providers that meet accessibility standards, but we don't control their underlying infrastructure.

6. How to report a problem

If something on the Site or in the app is hard to use because of an accessibility issue, please email hello@trymycro.com. Include:

• The page or screen where the problem happened
• What you were trying to do
• The browser or assistive technology you were using, if you know

We try to acknowledge accessibility reports within five business days and treat them as priority bug reports.

7. Changes to this statement

We'll update the "Last updated" date when we materially change this statement.