Accessibility Statement

FormLevel considers accessibility during design, development, testing, and ongoing maintenance. Our goal is to reduce barriers so people with disabilities can understand the content, navigate the service, use its controls, and receive meaningful feedback.

Accessibility is an ongoing responsibility, especially while FormLevel is in beta. We welcome reports from people using assistive technology and use that feedback to prioritize improvements.

This statement covers the first-party FormLevel web application at formlevel.app, including the exercise-analysis, workout-planning, diet-planning, account, progress, and legal-information interfaces that FormLevel operates.

Third-party services, browser-native controls, and content provided by other organizations may have their own accessibility behavior. Those dependencies are addressed in the current limitations below.

FormLevel uses the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA as an ongoing design and testing target. The U.S. Department of Justice also identifies WCAG as helpful technical guidance in its Guidance on Web Accessibility and the ADA.

Current conformance status: not formally determined. FormLevel has not completed a comprehensive WCAG 2.2 Level AA conformance evaluation or received independent accessibility certification. This statement therefore does not claim full WCAG conformance, blanket ADA compliance, or that every page, workflow, and third-party component meets every accessibility requirement that may apply.

• Use semantic page landmarks, heading structure, form labels, accessible names, and text status messages.
• Build interactive controls for keyboard use with visible focus treatment and labeled menus and dialogs.
• Design and test toward responsive layouts, browser zoom, light and dark appearance choices, and readable contrast.
• Pair important status colors with text, icons, or programmatic state instead of relying on color alone.
• Respect the operating system's reduced-motion preference so nonessential interface movement is limited automatically when requested by the user's device.
• Run automated accessibility checks with Playwright and axe and maintain component tests for important keyboard and accessibility behavior.

Automated testing can identify many issues, but it cannot prove that a service is fully accessible. We supplement automated checks with developer review and continue expanding manual and assistive-technology testing.

FormLevel currently assesses accessibility through developer self-evaluation. This includes automated axe checks in Playwright, component and interaction tests, and manual developer review of keyboard use, responsive layouts, browser zoom, focus behavior, and status messaging.

Current automated browser coverage primarily uses Chromium on desktop and Pixel 7-style mobile emulation. FormLevel has not yet completed a comprehensive evaluation across screen readers, Safari or WebKit, physical iOS devices, forced-colors or high-contrast modes, or every combination of browser and assistive technology. Automated test results are useful signals, not proof of complete accessibility or conformance.

FormLevel relies on HTML, CSS, JavaScript, and WAI-ARIA where native HTML alone does not express an interactive control's state. Interactive analysis, planner, account, and progress features require JavaScript.

The service is designed for current versions of major desktop and mobile browsers, but a formal browser and assistive-technology compatibility matrix has not yet been established. Browser, operating-system, assistive-technology, and extension combinations vary and may behave differently.

Despite ongoing work, some content may not yet provide an equivalent experience in every format:

• Most exercise demonstrations and generated overlays are silent and include written instructions or analysis summaries where the feature provides them, but motion and measurement details may not have a complete text equivalent or audio description. User-uploaded videos are presented as provided; FormLevel does not currently generate captions or transcripts for audio in those uploads.
• Pose overlays, progress charts, and other visualizations may contain more visual detail than is conveyed through their current accessible names or text summaries.
• FormLevel does not yet provide a site-wide skip-to-main-content link, so keyboard users may need to move through repeated navigation before reaching a page's primary content.
• Some menu and tab-like controls support Tab, Enter, Space, and Escape but do not yet implement every recommended arrow-key interaction.
• Accessibility of third-party media, browser-native video controls, authentication services, and other provider interfaces can vary outside FormLevel's direct control.
• New or changing beta features may introduce temporary accessibility regressions that automated checks do not detect.

If one of these limitations prevents access, please request help or an available alternative using the contact options below.

Report an accessibility barrier through Contact & support or by email at hello@formlevel.app. If possible, include the page or feature, what you were trying to do, what happened, and the browser or assistive technology involved. Do not send passwords, authentication codes, tokens, or other secrets.

You may also use those contact options to request assistance accessing information or completing a FormLevel workflow. If the support form itself creates a barrier, email us directly. Accessibility reports are reviewed as part of ongoing product work.

This statement will be revised as FormLevel's features, testing practices, known limitations, or accessibility targets change. The date at the top identifies the current version.