LegalAccessibility Statement
Accessibility Statement
1. Commitment
Being Optimal is a pregnancy-nutrition planning product. We believe people should be able to plan meals, learn, and manage their accounts regardless of disability, assistive technology, or temporary impairment.
We are committed to improving the accessibility of:
- Public marketing and Learning Center pages;
- Help Center content;
- Account and authentication flows;
- The signed-in nutrition dashboard (planner);
- Legal and policy pages.
2. Conformance target
| Standard | Target |
|---|---|
| WCAG | 2.1 Level AA (Web Content Accessibility Guidelines) |
| Additional | We consider WCAG 2.2 guidance where practical as we iterate |
Status: Partial conformance / ongoing improvement. We have not published a third-party WCAG audit certificate for the full product as of 2026-07-13. Individual screens may meet AA while others lag.
This statement will be updated when a formal audit is completed or major accessibility remediations ship.
3. Measures we take
| Measure | Practice |
|---|---|
| Design system | Shared tokens, focus-visible styles, and UI kit patterns where the product uses them |
| Semantic structure | Headings, landmarks, and labels on newer surfaces |
| Keyboard | Interactive controls intended to be reachable by keyboard on primary flows |
| Color & contrast | Theme tokens aiming for readable contrast; dark theme default on some surfaces |
| Text alternatives | Decorative vs informative image treatment on editorial content; ongoing for charts |
| Reduced motion | Respect for user motion preferences where implemented |
| Auth & forms | Provider-hosted and first-party forms with labels; errors intended to be text-visible |
| Legal documents | Structured Markdown rendered to accessible page layouts on /legal/* |
4. Known limitations
We are transparent about areas that may create barriers today:
| Area | Limitation | Mitigation / plan |
|---|---|---|
| Nutrition dashboard density | Complex grids, meal editors, and multi-panel layouts may be difficult with screen readers or small viewports | Incremental labeling, focus order, and responsive work |
| Charts & score visualizations | Visual Day Score / nutrient charts may lack full text equivalents or live-region updates | Prefer numeric summaries already shown in UI; expand text alternatives over time |
| Drag-and-drop / advanced editors | Some interactions may be pointer-first | Keyboard alternatives where present; report gaps |
| AI assistant chat | Dynamic streaming content may challenge some AT users | Message history remains in DOM; improve announcements over time |
| Community forum | Hosted by Community Platform Provider — accessibility follows that platform’s capabilities | Report forum-specific issues to us; we escalate where we can |
| PDF / downloadable exports | Export formats may not be fully tagged accessible documents | Request alternative formats via [email protected] or [email protected] for data exports |
| Third-party auth UI | Authentication Provider-hosted screens are outside our full design control | We configure branding where allowed; provider a11y policies apply |
| Mobile PWA | Installable web app; some mobile AT combinations less tested | Feedback-driven fixes |
| Language | English-primary product; limited localization | Affects cognitive load for non-English users |
This list is not exhaustive. Absence of an item does not mean full conformance.
5. Compatibility
| Technology | Notes |
|---|---|
| Browsers | Modern evergreen browsers (latest two major versions of Chrome, Firefox, Safari, Edge) |
| Assistive tech | We test on a best-effort basis with common screen readers and OS accessibility settings; not every combination is certified |
| Zoom | Core flows should remain usable at increased zoom / text size; dense tables may require horizontal scroll |
6. Feedback and assistance
If you encounter an accessibility barrier:
- Email [email protected] (or [email protected] if that address is easier for you).
- Include:
- The page URL or screen name; - What you were trying to do; - Assistive technology / browser / OS if known; - Screenshots or a short description of the barrier.
We aim to respond within 10 business days acknowledging your report, and to provide a timeline or workaround where feasible.
Alternative formats
On request, we will make reasonable efforts to provide information in an alternative format (e.g., clearer HTML, structured export assistance) via [email protected] or [email protected].
7. Enforcement and formal complaints
| Path | Contact |
|---|---|
| Product accessibility feedback | [email protected] |
| Legal / regulatory accessibility inquiry | [email protected] |
| Privacy-related access needs | [email protected] |
Depending on your location, you may also have rights under disability and equality laws (e.g., ADA in the United States, European Accessibility Act / national implementations in the EU, Equality Act 2010 in the UK). This statement does not limit those rights.
8. Preparation of this statement
| Field | Value |
|---|---|
| Prepared for | [PENDING: LEGAL_ENTITY_NAME] (Being Optimal, Site Nutrition) |
| Method | Operator self-assessment against WCAG 2.1 AA intent; product architecture knowledge |
| Last review | 2026-07-13 |
| Next planned review | On major UI release or at least annually |