Our target
We build gluciq.com and the GlucIQ mobile app toward Web Content Accessibility Guidelines (WCAG) 2.2, Level AA. Accessibility is a stated product requirement.
What we have verified on the website
Our most recent verification pass on gluciq.com covered:
- Keyboard. Every interactive element we tested is reachable and operable with a keyboard alone, with a visible focus indicator.
- No JavaScript. The core marketing pages stay readable and usable with JavaScript disabled.
- Zoom and reflow. Text stays readable and unclipped at 200% browser zoom, and content reflows to a single column without horizontal scrolling at a narrow viewport.
- Reduced motion. Animated elements stop when the operating system asks for reduced motion.
- Contrast. The shipped color tokens meet the WCAG 2.2 AA thresholds for the text and interface elements we tested.
- Widths. 320 pixels to 1920 pixels.
What we have not yet verified, and what is hard
- Interactive calculators. The calculators use static forms with native controls and stay operable without JavaScript. We have not audited how their outputs read in a screen reader; that audit is open.
- Long-form content. Data tables inside long blog posts, and document-style content that began as a PDF, have not been audited. Some are likely to be difficult with a screen reader or at high zoom.
- The mobile app. The app has not completed an independent accessibility audit. It relies on the platform screen readers, VoiceOver on iOS and TalkBack on Android. Our own checks cover the main flows, not every screen.
If one of these gaps blocks you, tell us which screen or page, and we will prioritize it.
Meal scanning without a camera
Scanning a meal with the camera is one input method among several. If a camera is unavailable to you, or a camera-only interaction is a barrier, these alternatives work:
| Alternative | How it is used |
|---|---|
| Manual entry | Type the meal and its components yourself |
| Barcode scan | Scan a packaged product barcode where a camera is available, or search for the product |
| Text search | Search the nutrition library by name |
| Nutrition library | Reuse a food or meal you have logged before |
You do not need the camera to use GlucIQ.
Assistive routes
If you need a person to describe or navigate something on this site or in the app:
- Contact us at [email protected], and we will describe the screen or document you need.
- Be My Eyes connects blind and low-vision users with sighted volunteers and company support through its app. We are reachable through the standard Be My Eyes service and will answer a GlucIQ question sent that way.
- Platform assistive tools, including VoiceOver, TalkBack, Voice Control, Switch Control, and the operating system’s magnification settings, apply to the app as they do to other apps.
Feedback and response
Send accessibility feedback to [email protected] with the subject Accessibility feedback. Describe the page or screen and the assistive technology you used, then tell us what happened. We acknowledge within two business days. Accessibility defects enter the normal product process, with the same triage and fix path as any other bug. If a fix will take a while, we tell you what we plan to do and when.
European Accessibility Act context
The European Accessibility Act applies to many digital products and services in the European Union. Along with the harmonized standard EN 301 549, it sets the accessibility requirements. We use WCAG 2.2 AA, the standard EN 301 549 references for web content, as the working target for this site and the app.
Contact
Accessibility feedback and requests for a specific format go to [email protected]. Company details are in the Imprint.