← FuelLog

Accessibility Statement

FuelLog is a free workout and nutrition tracking app, built and maintained by one person. We want it to be usable by as many people as possible, including people who use screen readers, keyboard navigation, high-contrast displays, or reduced-motion settings. This page explains what we've done, where we honestly still fall short, and how to reach us if something isn't working for you.

The standard we aim for

We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA — the standard most commonly referenced for web accessibility, including under U.S. laws like the Americans with Disabilities Act (ADA). It's the target we design and test against.

What we've done

We recently ran an accessibility audit and fixed the issues it found. That work included automated scanning (axe-core across the app's main screens, in both light and dark themes) plus manual keyboard, contrast, and screen-reader review. From that pass we:

After those fixes, our automated scans report zero violations across the screens and themes we tested.

Current status

FuelLog is partially conformant with WCAG 2.1 Level AA. "Partially conformant" means the app meets most of the standard, but not yet every part of it. We're being upfront about that on purpose: automated testing can't catch everything, and a clean scan is not a guarantee that every interaction works well with every assistive technology. We consider accessibility an ongoing effort, not a one-time checkbox — this is a good-faith statement of where we are, not a certification or a promise of full compliance.

Known limitations

To be honest about the gaps, here's what we know still needs work:

We're working through these as we're able. If one of them is blocking you, please tell us (see below) and we'll prioritize it.

Tell us if something isn't working

If you hit an accessibility barrier in FuelLog, or you need help doing something the app makes hard, email us at jacksonveljkovic@gmail.com. It helps if you can tell us what you were trying to do, which screen you were on, and what device, browser, or assistive technology you were using — but even a quick "this button doesn't work with my screen reader" is genuinely useful.

We read every message and aim to respond, and to fix confirmed issues, within a reasonable timeframe. If a fix will take a while, we'll try to suggest a workaround in the meantime.

Changes to this statement

As we improve the app and re-test, we'll update this page and the "Last updated" date above to reflect where things actually stand.