Accessibility Statement
Last updated: September 2026
NTRLY is committed to making our website and apps usable by everyone, including people who rely on assistive technology. This statement describes how far we've got, where we know we fall short, and how to tell us when we've got it wrong.
Conformance target
We are working towards conformance with the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA. Our self-assessed status is partially conformant. This assessment is internal — automated tooling plus our own review — and is not a third-party audit. We have not commissioned an independent VPAT and will not claim one until we have.
How we test
We run automated axe-core checks against twelve public pages using the WCAG 2.0 and 2.1 Level A and AA rule sets, at two widths — 1280 and 390 CSS pixels — in the light theme. Any finding rated critical or serious fails the check, and each run writes a dated report listing the routes scanned, the rule configuration and every finding. The most recent run found no critical or serious violations. Two points of precision, because they change what that sentence is worth: the check is a script we run before a release, not a continuous-integration gate, and automated checks cannot establish full WCAG conformance — they catch a well-defined subset of failures and are silent about much of what matters.
What's supported today
These are the things our checks cover on the public pages, at both widths we test. Text contrast of at least 4.5:1 for body copy and 3:1 for large text and interface components. Semantic headings in a logical order. Every form field programmatically associated with its label. Images that carry meaning have alternative text, and decorative artwork is marked so screen readers skip it. Links and buttons have accessible names. Regions that scroll horizontally can be reached and scrolled with a keyboard. A skip-to-content link is the first thing in the tab order on every page. We honour prefers-reduced-motion, and the app carries its own reduce-motion setting for people whose system preference does not reflect what they want here. Everything in this paragraph is checked automatically or is a property of the code rather than an intention.
What we have not tested yet
This section used to list specific defects — charts without accessible data tables, tables that did not announce their headers, modals returning focus to the wrong place. None of them had been reproduced. Listing suspected faults reads as candour while it is really guesswork, and it can describe problems that do not exist while hiding ones that do, so it is gone until each item has evidence behind it. What we can state plainly is the coverage. Our signed-in application has not yet had the same automated sweep, because those pages need an account. We have not completed a structured screen-reader audit with VoiceOver, NVDA, JAWS or TalkBack. We have not yet systematically tested the dark theme, keyboard operation of the meal planner's date controls, or the accessible alternatives to our charts. None of that means those features are inaccessible — it means we have not yet verified them, and we would rather tell you which is which. As testing produces findings, they will be listed here with the date they were confirmed.
Third-party content
Some parts of the experience are provided by third parties we don't control, including the sign-in windows presented by Google and Apple and the app store pages we link out to. We choose vendors with accessibility in mind and raise defects with them, but we cannot guarantee conformance of content served by another party. If a third-party component blocks you, tell us anyway — we will either escalate it or find you another route through.
Compatibility
The site is designed to work with current versions of Chrome, Edge, Firefox and Safari, paired with current versions of VoiceOver, NVDA, JAWS and TalkBack. It should also work with browser zoom, operating-system text scaling, high-contrast and forced-colours modes, speech recognition software, and switch access. Older browsers may work but are not tested. If you use an assistive technology we haven't listed, we would genuinely like to hear how you get on.
Reporting a problem
If any part of NTRLY is difficult or impossible for you to use, email support@ntrlyapp.com with the page or screen, what you were trying to do, and the browser and assistive technology you were using. We acknowledge every report within two business days and aim to resolve confirmed barriers within thirty days, or sooner where the barrier blocks core functionality. If a fix will take longer, we will tell you and offer an alternative way to complete the task in the meantime. Reports of accessibility barriers are treated as bugs, not feature requests, and are prioritised accordingly.
Formal complaints and alternative formats
If you are not satisfied with our response, ask for your report to be escalated to our accessibility lead by replying to the same thread — we will confirm receipt and give you a named point of contact. We can also provide information from this site in an alternative format, including large print, plain text or an accessible document, on request at no cost. There is no deadline for making a request and no need to explain why you need it.
Questions about this document?
Write to info@ntrlyapp.com and a person will answer — normally within one business day.
Digital Summit LLC, 2740 N. Mayfair Ave, Suite H112, Springfield, MO 65803