Our commitment to inclusive digital experiences and equitable access to I am J technology.
We aim to improve accessibility throughout the product lifecycle and to address barriers that prevent people from perceiving, understanding, navigating, interacting with, or contributing to our services.
We recognize that accessibility needs vary and that no single implementation serves every person or situation.
We use recognized accessibility principles and guidance as practical references, including perceivable, operable, understandable, and robust design.
Where applicable, we seek alignment with relevant accessibility requirements and commonly accepted web and mobile accessibility practices.
Design and development considerations may include semantic structure, keyboard access, focus visibility, text alternatives, sufficient contrast, resizable text, adaptable layouts, clear labels, error identification, captions, reduced-motion preferences, and compatibility with assistive technologies.
Content should use clear language, meaningful headings, descriptive links, readable formatting, and alternatives for important visual or audio information where practical.
Documents, demonstrations, images, and videos are reviewed and improved over time as resources and technical capabilities permit.
Mobile interfaces should support accessible navigation patterns, scalable text, screen-reader use, understandable controls, and alternatives to gestures where practical.
Voice interaction can improve access for some users but may create barriers for others; core tasks should not depend exclusively on speech when a reasonable alternative can be provided.
AI can assist with translation, visual description, conversational interaction, and knowledge access, but AI output may be incomplete or inaccurate.
Accessibility-related AI features should communicate limitations and should not be relied upon as the sole basis for safety-critical, medical, legal, or other high-impact decisions.
Accessibility needs in schools, humanitarian operations, remote environments, and public-sector deployments may differ according to devices, connectivity, language, physical setting, and user population.
Customers and deployment partners should communicate known accessibility requirements during planning so that appropriate configurations and support measures can be evaluated.
Accessibility review may include automated checks, manual inspection, keyboard testing, assistive-technology testing, responsive-layout review, and user feedback.
We prioritize remediation according to severity, frequency, affected task, available workaround, and impact on independent access.
Accessibility performance can vary by device, operating system, browser, assistive technology, settings, connectivity, and third-party components.
Using current supported software and enabling available accessibility settings may improve the experience.
We welcome reports describing accessibility barriers, affected pages or features, device and assistive technology used, and the task the person was trying to complete.
We will review good-faith reports and use them to guide remediation and product improvement.
For questions, concerns, requests, or reports related to this document, contact I am J Corporation through the official contact form.
Open the I am J contact form →