ALO ARK · Accessibility Statement
ALO ARK is built for professionals in motion, all of them. We aim for the platform and website to conform to WCAG 2.1 Level AA, and we build with accessibility in mind from the start: semantic markup, keyboard navigability, a skip-to-content link on every page so keyboard users can bypass the navigation, sufficient color contrast, text alternatives for meaningful images, and forms with proper labels.
Where we are: the current site targets WCAG 2.1 AA. Video introductions carry an optional transcript, written by the member and shown beneath the video, so an introduction can be read when it cannot be heard. As the platform grows (profiles, Build Teams, member messaging), new features are held to the same standard.
Found a barrier? Tell us and we'll fix it or find you a path around it while we do: support@aloark.com with "Accessibility" in the subject line. We acknowledge every report within 5 business days and aim to resolve or give you a workaround within 14.
Last reviewed: August 24, 2026. The public site was audited against WCAG 2.1 Level AA on that date: heading structure, image alternatives, form labels, keyboard focus, motion preferences, and computed color contrast on every text pair. Three issues were found and fixed the same day (two low-contrast text colors and incomplete reduced-motion coverage). One item remains for the next review, when the platform opens: a full audit of the signed-in surfaces, including the profile builder and the paths through references and introductions.
Updated September 29, 2026: the site now serves in English and French, with the language switch in the header and footer of every page; the French pages hold the same WCAG 2.1 AA standard and declare their language to assistive technology. One known item is queued: the skip-to-content link on French subpages currently reads in English. The same day, an automated and keyboard audit (axe-core, WCAG 2.0 and 2.1, Levels A and AA) ran across eight public pages in both languages: it found ten text styles below the contrast threshold, eleven form controls without programmatic labels on the Runway Calculator, and one incorrect ARIA role in the landing page's persona picker, and all were fixed the same day. Reduced-motion behavior and keyboard order were verified clean. One documented exception stands: the faint wordmark behind the closing section is decorative by design and is hidden from assistive technology.