Accessibility

Built for Everyone.

AVNIR is committed to making the platform accessible to all users, regardless of ability or assistive technology. This statement describes our conformance target, the measures we have taken, and how to reach us if you encounter a barrier.

Conformance target

We target WCAG 2.2 Level AA conformance for all pages and features of the AVNIR platform and public website. WCAG 2.2 is the current standard recommended by the W3C Web Accessibility Initiative (WAI) and referenced in accessibility legislation globally.

Our commitment

AVNIR believes that an intelligently designed product must be accessible to all. Accessibility is built into our engineering process from the start — not added as an afterthought. We are committed to continuously improving the accessibility of our platform and to meeting or exceeding the requirements of WCAG 2.2 Level AA, Section 508 (US), and the European Accessibility Act (EAA) where applicable.

This statement was last reviewed in May 2026. We review and update it at least once per year and whenever significant platform changes are made.

Measures taken

The following technical and design measures are applied across the AVNIR platform and public website:

Semantic HTML & document structure

We use semantic HTML5 elements throughout — nav, main, section, article, aside, header, and footer — so that assistive technologies can correctly interpret page structure. Every page has a single, well-defined H1, followed by a logical heading hierarchy.

Keyboard navigation

All interactive elements — links, buttons, form inputs, accordion triggers, and navigation items — are reachable and operable by keyboard alone. Focus order follows a logical, meaningful sequence. A skip-to-main-content link is visible on focus at the top of every page for keyboard users who want to bypass repeated navigation.

Focus states

We provide visible, high-contrast focus indicators on all interactive elements. Focus styles are not suppressed globally — they are only replaced with custom indicators that meet or exceed WCAG 2.2 AA contrast requirements.

Reduced-motion support

AVNIR respects the prefers-reduced-motion media query. All CSS animations and JavaScript-driven transitions are disabled or significantly reduced for users who have indicated a preference for reduced motion in their operating system settings. This includes hero animations, page transitions, and accordion expand/collapse effects.

Colour contrast

We design for WCAG 2.2 AA minimum contrast ratios: 4.5:1 for normal text and 3:1 for large text and UI components. Our dark design system uses a deep navy background (#02102e) with light ink and muted text colours calibrated to meet these thresholds. We do not rely on colour alone to convey information.

Alternative text for images

Meaningful images include descriptive alt text. Decorative images (such as background blobs, bird illustrations, and ambient visual elements) are marked with empty alt attributes or aria-hidden='true' so they are not announced by screen readers.

ARIA landmarks & live regions

We use ARIA landmark roles and labels (aria-label, aria-labelledby, aria-describedby) to identify regions of each page and to associate labels with interactive components. Dynamic content changes are announced via appropriate live regions where needed.

Forms & interactive components

Form inputs have associated labels. Required fields are indicated with both visual cues and text. Error messages are descriptive and programmatically associated with their inputs. Accordion components implement the ARIA Authoring Practices Guide pattern with aria-expanded and aria-controls.

Typography & readability

Body text is a minimum of 15px on all pages. Line height is set to 1.72–1.80 for prose content to support readability. Text can be resized up to 200% without loss of content or functionality. We do not use justified text, which can create uneven spacing that affects users with cognitive disabilities.

Known limitations

We are actively working to reach full WCAG 2.2 AA conformance. The following are known areas in progress:

  • Complex data visualisations — relationship maps and network graphs currently have limited screen-reader support. Text-based equivalents and table views are planned as accessible alternatives.
  • Third-party embedded content — some embedded components from third-party integration providers may not meet our accessibility standards. We raise accessibility issues with providers and provide alternatives where possible.
  • Touch gesture interactions — certain gesture-based features in the mobile application may not have fully equivalent alternatives in all versions. We are improving these in active development.

We do not consider any of these known limitations acceptable on a permanent basis. If a limitation is blocking your use of a core feature, please contact us — we will prioritise a solution and provide an accommodation in the interim.

Feedback & reporting barriers

We rely on user feedback to identify and resolve accessibility barriers. If you encounter a problem accessing any part of the AVNIR platform or this website, or if you have a suggestion for improvement, we want to hear from you.

Please contact us with the following information (as much as you are able to provide):

  • The URL of the page or the feature where you encountered the barrier.
  • A description of the problem — what you tried to do and what happened.
  • The assistive technology you are using (if any), including the name and version.
  • Your browser and operating system.
AVNIR Accessibility
Atlanta, GA, USA
info@avnir.com

Please use the subject line “Accessibility Barrier”. We acknowledge all accessibility inquiries within two business days and aim to resolve reported barriers as quickly as possible. If we cannot resolve an issue immediately, we will provide an accessible alternative while we work on a permanent fix.

Formal complaints

If you are not satisfied with our response to an accessibility concern, you may contact the relevant enforcement body in your jurisdiction:

  • United States: The US Access Board (access-board.gov) for Section 508 concerns, or the US Department of Justice for ADA Title III concerns.
  • European Union: Your national accessibility enforcement authority under the European Accessibility Act.
  • United Kingdom: The Equality and Human Rights Commission (equalityhumanrights.com) or the Equality Advisory and Support Service.

This Accessibility Statement was prepared in May 2026 and is reviewed at minimum annually. Technical measures are applied on an ongoing basis as the platform evolves.

Last reviewed: May 2026