Accessibility by construction.
Agined should be usable by everyone. We are committed to making our website and applications accessible to everyone, including people who use assistive technologies such as screen readers, screen magnifiers, voice control, and keyboard-only navigation.
Effective 2026-11-08 · Last reviewed 2026-11-08 · Avonao, Inc.
Our commitment
Agined is designed and built to conform with the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA — the technical standard referenced by the major accessibility laws worldwide. Accessibility is a first-class requirement in the engineering process, not an afterthought, and the design system encodes it (perceptually uniform colour tokens, consistent focus indicators, semantic landmarks) so that conformance holds by construction rather than by manual patching.
Conformance status
Agined targets WCAG 2.2 Level AA. We do not yet claim full or partial conformance, because no manual or third-party audit has been carried out. Known gaps are tracked and being remediated — see Known limitations below. No core task has yet been formally confirmed completable with assistive technology.
Standards we build to
A single technical target — WCAG 2.2 AA — satisfies the frameworks that apply to us:
- WCAG 2.2 Level AA — W3C Web Content Accessibility Guidelines (October 2023).
- EN 301 549 and the European Accessibility Act (Directive (EU) 2019/882). We build to the forthcoming EN 301 549 V4.1.1 baseline (WCAG 2.2 AA), ahead of its harmonisation.
- Americans with Disabilities Act (ADA), Title III — for which WCAG 2.x AA is the standard courts apply.
- Section 508 of the U.S. Rehabilitation Act, which incorporates WCAG by reference.
What we have done
Measures currently in place across the website and applications include:
- Full keyboard operability with a strong, consistent focus indicator on every interactive element, and a “Skip to main content” link on every page.
- Semantic structure — landmarks, headings, and ARIA roles/states — so the page is navigable and announced correctly by screen readers, with live regions for status updates.
- Colour contrast meeting WCAG AA, verified automatically: a contrast audit in our codebase computes the contrast ratio of every brand colour pairing and fails on any regression.
- Respect for reduced-motion preferences — animations and transitions are neutralised when the operating system signals
prefers-reduced-motion. - Sign-in through Avonao ID, Avonao's account service. If you meet a barrier when signing in, tell us and we will take it up with Avonao ID.
- Correct page language for every supported locale, so assistive technologies pronounce content in the right language.
- Automated accessibility checks — static checks (accessible names, alternative text, focus order) and the colour-contrast audit.
Known limitations
Despite our efforts, some content may not yet be fully accessible. What is still in progress:
- A full manual screen-reader audit (NVDA, JAWS, VoiceOver) and an assisted manual assessment of the criteria that cannot be checked automatically (meaningful focus order, sensible reading sequence, target sizes) is not part of our checks, and has not been carried out yet.
- A runtime automated test suite (axe-core, pa11y, Lighthouse against live pages) is not in place yet — our checks are static.
- Some third-party or embedded content (for example, web-font delivery and any embedded media) may not fully conform to WCAG 2.2 AA. The same applies to pages hosted by Avonao ID (sign-in) and Avonao Billing (checkout and the billing portal), which are separate services.
If you encounter a barrier that is not listed here, please tell us — your report directly shapes what we fix next.
Compatibility
The platform is designed to work with current versions of major browsers (Chrome, Edge, Firefox, and Safari) on desktop and mobile, in combination with the leading screen readers (NVDA, JAWS, VoiceOver, and TalkBack). It is built with progressive enhancement, so core content and navigation remain usable on older or assistive configurations. We have not yet completed formal testing of specific browser and screen-reader combinations.
Feedback & how to report a barrier
We welcome your feedback on the accessibility of this site. If you experience a barrier, or need information on this site in a different format, please contact us:
- Through our contact form, noting “Accessibility” in your message.
- Through the support assistant available on every page.
We aim to acknowledge accessibility feedback within 5 business days and to provide a substantive response, including a timeline for any fix, as quickly as we can.
Enforcement procedure
If you contact us about an accessibility barrier and are not satisfied with our response, you may escalate to the relevant authority. In the European Union, the European Accessibility Act is enforced at the national level: you may contact the national accessibility enforcement authority in your member state. In the United States, ADA matters fall under the U.S. Department of Justice.
How we assessed this
Self-assessment only. No third-party evaluation has been done. Assessment so far is automated: the static accessibility checks and the brand colour-contrast audit in our codebase. Manual testing with a keyboard and screen readers has not yet been completed. We review this statement at least once a year and whenever a significant change ships.
Statement prepared 2026-11-08 · Last reviewed 2026-11-08 · Operated by Avonao, Inc., Delaware, USA