Accessibility Statement

Our approach

• We aim to use semantic HTML, keyboard-accessible controls, readable contrast, visible focus states, descriptive labels, and text alternatives for meaningful images.
• We test core flows such as navigation, forms, checkout, and account access as the product evolves.
• Client project accessibility requirements are discussed in the project scope and may require additional work beyond the Standard Website package.

Feedback

If you encounter an accessibility barrier, contact AIR through the contact page with the page, device, and issue. We will review the report and work toward a reasonable improvement.