Accessibility Statement

1. Our Commitment

AIRMY Technologies, Inc. is committed to ensuring digital accessibility for people with disabilities. We continuously improve the user experience for everyone and apply relevant accessibility standards. We believe that accessible design is better design — for all users, in all contexts.

This statement applies to the AIRMY website at airmy.dev, the AIRMY dashboard at dashboard.airmy.dev, the developer documentation site, and the AIRMY marketing pages. It does not currently cover customer-deployed agent interfaces, which are the responsibility of the deploying customer, though we provide accessible components and documentation to assist them.

We have a designated Accessibility Lead (a senior UX engineer) who owns the accessibility programme, coordinates remediation efforts, and is the primary contact for accessibility-related feedback.

2. Conformance Status

The Web Content Accessibility Guidelines (WCAG) defines requirements for designers and developers to improve accessibility for people with disabilities. It defines three levels of conformance: Level A, Level AA, and Level AAA.

Our target is full WCAG 2.1 Level AA conformance. We use this as our benchmark because it is referenced in legislation across the EU (EN 301 549), UK (Public Sector Bodies Accessibility Regulations 2018), and is broadly considered the industry standard for commercial web applications.

3. Technical Specifications

The AIRMY platform relies on the following technologies for accessibility:

• HTML5 — semantic markup with appropriate landmark regions (<main>, <nav>, <header>, <footer>, <aside>), heading hierarchy, and meaningful element order.
• WAI-ARIA 1.1 — ARIA roles, states, and properties are used where native HTML semantics are insufficient, particularly in dynamic components (modals, accordions, live regions, comboboxes).
• CSS3 — styles use relative units (rem, em) to support browser text resizing. Focus indicators are visible and meet contrast requirements. No information is conveyed by colour alone.
• JavaScript with progressive enhancement — core content and navigation are accessible without JavaScript where possible. Dynamic interactions enhance the experience but do not gate access to information or core functionality. Focus management is handled explicitly for dynamically inserted content.

We test against the latest stable versions of the browsers listed in Section 6. Older browser versions may have degraded but functional accessibility support.

4. Measures to Support Accessibility

AIRMY takes the following measures to ensure accessibility of our digital services:

• Accessibility in design: all new UI components are designed against WCAG 2.1 AA criteria from the outset. Our design system (internal) documents accessible usage patterns and contrast ratios for every component.
• Automated testing in CI: axe-core is integrated into our CI/CD pipeline via @axe-core/playwright. Every pull request runs automated accessibility checks against all key pages and components. Critical axe violations block merge; moderate violations generate warnings tracked in our accessibility backlog.
• Manual testing: our Accessibility Lead performs manual keyboard-only and screen-reader testing on all new features before they ship to production. We follow the W3C Easy Checks and a custom checklist aligned to WCAG 2.1 AA criteria.
• User research with disabled users: we include people with disabilities in our user research programme. Research participants include keyboard-only users, screen reader users, and users with cognitive and motor differences. Findings directly inform our remediation priorities.
• Designated Accessibility Lead: the Accessibility Lead attends all sprint reviews, approves designs for new features, and maintains the accessibility backlog. Their role is formally defined in our engineering handbook.
• Staff training: all engineers and designers complete accessibility awareness training on joining. The Accessibility Lead runs quarterly accessibility office hours and reviews key topics arising from testing or user feedback.

5. Keyboard Navigation Guide

The AIRMY platform is designed to be fully operable using a keyboard alone. A skip navigation link (Tab on first load) allows keyboard users to bypass the navigation and jump directly to main content.

6. Assistive Technology Compatibility

We test the AIRMY platform regularly with the assistive technology and browser combinations listed below. Test results reflect the state of the platform as of March 2026 on the latest stable browser versions.

7. Colour & Contrast

7.1 Contrast Ratios

AIRMY uses a monochrome design system (black background, white text) with deliberate opacity levels. Our target contrast ratios meet or exceed WCAG 2.1 Level AA requirements:

• Primary body text (rgba(255,255,255,0.72) on #000): contrast ratio approximately 10.2:1 — exceeds AA (4.5:1) and AAA (7:1) for normal text.
• Section headings (#fff on #000): contrast ratio 21:1 — maximum contrast.
• Secondary / muted text (rgba(255,255,255,0.4) on #000): contrast ratio approximately 5.4:1 — meets AA for normal text. Used only for non-essential supplementary information.
• Small uppercase labels (rgba(255,255,255,0.35) on dark backgrounds): we are in the process of reviewing these for large-text rules (3:1 ratio) and will update to a higher opacity where needed.
• Interactive controls: all buttons, links, and form fields have visible focus indicators with a contrast ratio of at least 3:1 against the surrounding background (WCAG 2.1 SC 1.4.11).

7.2 No Colour-Only Information

No information is conveyed by colour alone. Status indicators (e.g., agent health, deployment status) use both a colour-coded dot and a text label. Form validation errors include both a visual indicator and text description. Charts and data visualisations include alternative text descriptions and, where applicable, pattern fills or text labels in addition to colour coding.

7.3 Dark Mode

AIRMY's primary design is a dark theme. A light mode is available in user preferences (dashboard settings) and is currently in beta. We apply the same contrast standards to the light theme. The colour scheme does not depend on a user's OS-level dark mode preference, but we do respond to prefers-color-scheme on initial load before a user preference is saved.

8. Text & Typography

• Resizable text: all text is sized using relative units (rem / em). Text can be resized up to 200% using browser zoom without loss of content or functionality. We test at 200% zoom as part of our standard accessibility review checklist.
• No text in images: we do not use images of text to convey information. All text is rendered as selectable, copyable HTML text. The AIRMY logo is an exception (decorative image with appropriate alt text).
• Line spacing and readability: body text uses a line height of 1.8 (180% of font size), exceeding the WCAG 2.1 SC 1.4.12 spacing requirement of at least 1.5. Paragraph spacing is at least 2× the font size.
• Reading level target: we target a reading level of approximately Grade 10–12 (Flesch-Kincaid) for instructional content and a Grade 8 reading level for help documentation and error messages. We use plain language guidelines and avoid unnecessarily technical jargon where plain language serves equally well.
• Letter spacing and word spacing: no CSS overrides reduce letter or word spacing below browser defaults. Users can override spacing via browser settings or user stylesheets without loss of content.

9. Content & Language

• Language attribute: all pages declare lang="en" on the <html> element. Where content switches language within a page (e.g., a multi-language error message), the appropriate lang attribute is set on the containing element.
• Consistent navigation: the main navigation, footer, and sidebar are identical in structure and order across all pages. Navigation labels are consistent and predictable.
• Descriptive link text: all links have descriptive text that makes sense out of context. We do not use "click here", "read more", or other non-descriptive link text. Where identical link text points to different destinations, we use aria-label to disambiguate.
• No time limits: there are no time limits on reading or using AIRMY's public-facing pages. Session timeouts in the authenticated dashboard display a clear warning 5 minutes before expiry with an option to extend.
• Skip navigation link: a visible skip-to-content link appears as the first focusable element on every page. It is visually hidden until focused, at which point it becomes clearly visible (white text on black, meeting contrast requirements).
• Page titles: every page has a unique, descriptive <title> element that identifies both the page name and the site (e.g., "AIRMY | Cookie Policy").
• Focus management: when modals open, focus moves to the modal container. When modals close, focus returns to the triggering element. Single-page app route changes announce the new page title to screen readers via a live region.

10. Known Limitations

Despite our best efforts, some areas of the AIRMY platform have known accessibility limitations. We document them here honestly, along with our remediation plans.

11. Assessment Approach

11.1 Internal Review

AIRMY assesses the accessibility of our platform through a combination of:

• Automated testing: axe-core in CI/CD, Lighthouse accessibility audits on every deployment, and continuous monitoring via Silktide.
• Manual expert review: our Accessibility Lead performs structured WCAG 2.1 AA evaluation using the WCAG-EM methodology on all major features before release.
• Screen reader testing: manual testing with NVDA + Firefox and VoiceOver + Safari as primary combinations; JAWS + Chrome and TalkBack tested quarterly.
• Keyboard-only testing: all interactive features are tested keyboard-only before every production release.

11.2 Third-Party Audit

An independent accessibility audit by Deque Systems is scheduled for Q3 2026. The audit will cover the dashboard, API documentation, and marketing website using a combination of automated and manual evaluation. The full report and remediation plan will be published on this page following completion.

11.3 User Testing Panel

AIRMY maintains an ongoing user research panel that includes participants with a range of disabilities (visual, motor, cognitive, hearing). Panel members are compensated for their time. Insights from panel sessions directly inform our accessibility backlog prioritisation. If you would like to join the panel, please email accessibility@airmy.dev.

12. Feedback & Contact

We welcome feedback on the accessibility of airmy.dev. If you encounter any accessibility barriers, experience difficulty accessing content, or require content in an alternative format, please let us know:

• Email: accessibility@airmy.dev
• Response time: we aim to acknowledge your message within 2 business days and provide a substantive response (including a workaround or remediation timeline) within 5 business days.
• Postal address: AIRMY Technologies, Inc., 340 Pine Street, Suite 800, San Francisco, CA 94104, United States — marked "For the attention of: Accessibility Lead".

If you need content in an alternative format (e.g., large print, easy read, audio, accessible PDF), please state this in your message and we will accommodate the request as promptly as possible.

13. Formal Complaints

If you are not satisfied with our response to your accessibility feedback, or if you believe we are not meeting our accessibility obligations, you have the right to make a formal complaint or escalate to a regulatory body.

13.1 Internal Escalation

1. Contact accessibility@airmy.dev and request escalation to the Head of Engineering.
2. We will acknowledge the escalation within 2 business days and provide a formal response within 10 business days, including our assessment of the complaint and any proposed actions.

13.2 EU Users — Enforcement Bodies

If you are an EU resident and are not satisfied with our response, you may contact the relevant national enforcement body in your country under the EU Web Accessibility Directive (Directive 2016/2102). The full list of national enforcement bodies is available at:

w3.org/WAI/policies/enforcement

13.3 UK Users

UK users may contact the Equality and Human Rights Commission (EHRC) if they believe AIRMY has discriminated against them on grounds of disability in contravention of the Equality Act 2010:

equalityhumanrights.com/en/contact-us

13.4 US Users

US users may file a complaint under Section 508 of the Rehabilitation Act or the Americans with Disabilities Act (ADA) with the US Department of Justice Civil Rights Division:

ada.gov/filing_complaint.htm

This accessibility statement was prepared on 1 March 2026. It will be reviewed and updated at least annually, or whenever there are significant changes to the platform or when an accessibility audit is completed.