Skip to main content
OptimusPep

Accessibility Statement

Last reviewed: July 31, 2026

Reviewed: OptimusPep mobile app version 0.1.0 (iOS build 10), and the optimuspep.com website.

Our commitment

OptimusPep, LLC is committed to making OptimusPep usable by as many people as possible, including people who use screen readers, keyboard-only navigation, magnification, or larger text sizes. People manage real health routines in this app, and losing access to your own record is not an acceptable outcome.

OptimusPep is working toward conformance with the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA. We have not completed the comprehensive testing that would be needed to claim conformance, and this page is not a claim that the app or the website is fully accessible. It is a description of where we actually are, including what is still broken.

What we have measured

We completed an accessibility review on July 31, 2026 covering both the website and the mobile app source. The review included:

Accessibility measures currently in place

Known accessibility limitations

These are real problems we found and have not fixed yet. We would rather list them than imply they do not exist.

Colour contrast on the website

Small uppercase labels on the website, including compound category tags and some eyebrow labels and inline links, do not meet the 4.5:1 contrast minimum for normal-sized text. Measured ratios range from 2.14:1 to 3.52:1 against white. Our primary brand colour on white measures 3.16:1, which also affects the white text on primary buttons. Some footer text measures between 3.77:1 and 4.48:1. These labels are readable for many people but not for everyone, and this is the largest open issue on the site.

The mobile navigation menu

On narrow screens, the website menu button correctly reports whether it is open or closed, but the panel it opens is not announced as a dialog, does not receive focus when it opens, and does not trap focus or close on Escape. The links inside it can still be reached with the keyboard.

Screen reader testing is incomplete

We audited control names in the source code, which confirms a name exists, but we have not yet completed hands-on testing sessions with VoiceOver, TalkBack, NVDA, or JAWS. Until we do, we cannot describe the screen reader experience with confidence, and there may be barriers this review did not find.

Coverage of this review

Automated scanning covered major website routes rather than every page, and automated tools only detect a portion of possible accessibility issues in the first place. The mobile app was reviewed in source rather than on a device. A clean automated result is not the same as an accessible product, and we do not present it as one.

Report an accessibility barrier, or ask for help

If any part of OptimusPep is difficult or impossible for you to use, please tell us. We treat accessibility reports as bugs, not as suggestions, and a barrier that stops you completing something important gets priority.

Email support@optimuspep.com with the subject “Accessibility”. It helps if you can tell us the page or screen, what you were trying to do, and the assistive technology, browser, or device you were using. You can also send a report from inside the app under Settings, then Report a problem.

We aim to reply within a couple of business days. If you need information from the app in a different format so you can use it, ask us and we will find a way to get it to you.

How we keep this current

We review this statement when we complete an accessibility pass or ship a change that affects it, and we update the date at the top when we do. Publishing this page does not by itself make the product accessible. The work behind it is what counts, and the limitations listed above are the honest state of that work.

Back home