Accessibility Statement
Last updated: June 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, and we design against Level AAA for text contrast where it doesn't compromise legibility. Our current self-assessed status is partially conformant: most of the site meets Level AA, with the documented exceptions listed below. This assessment is based on internal review using automated tooling and manual keyboard and screen-reader testing, not a third-party audit. We have not yet commissioned an independent VPAT.
How we test
Every release is checked with axe-core in continuous integration, then manually with VoiceOver on macOS and iOS, NVDA on Windows with Firefox, and TalkBack on Android. We test keyboard-only navigation on every interactive screen, and we verify the site at 400% browser zoom and with a 320 CSS pixel viewport to confirm reflow behaviour.
What's supported today
Full keyboard operation of every control, with a visible focus indicator that meets the 3:1 non-text contrast requirement. Semantic headings in a logical order on every page, with skip-to-content available at the top of the tab order. Text contrast of at least 4.5:1 for body copy and 3:1 for large text and interface components. Every form field has a programmatically associated label, errors are announced through live regions and marked with aria-invalid rather than colour alone, and no error message relies on colour to be understood. Images that carry meaning have alternative text; decorative artwork is marked so screen readers skip it. Layout reflows to a single column without horizontal scrolling down to 320 CSS pixels, and all text can be resized to 200% without loss of content. Motion is limited, and we honour prefers-reduced-motion.
Known gaps
We'd rather list these than let you discover them. The analytics charts convey trends visually and their underlying figures are not yet exposed as an accessible data table, so screen-reader users get the summary statistics but not the full series. Some dense inventory and receipt tables do not yet announce row and column headers correctly when navigated cell by cell in certain screen-reader and browser combinations. A small number of modal dialogs return focus to the top of the page on close rather than to the control that opened them. Date pickers on the meal planner rely on a custom widget whose keyboard model is not yet fully documented for assistive-technology users, though a plain text-entry fallback is available. Video content in our help articles has captions but does not yet have audio description. We are actively working on all of these; the charts and the tables are the current priority.
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 hello@ntrly.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 hello@ntrly.com and a person will answer — normally within one business day.