Measures currently in place
- Semantic headings, landmarks, navigation labels, and a skip-to-content link.
- Keyboard-accessible links, controls, and visible focus behavior supported by the browser.
- Responsive layouts that reflow for smaller screens without requiring horizontal page scrolling.
- Text alternatives for meaningful images and labels for embedded or interactive content where practical.
- Color contrast and typography selected for readability against the dark interface.
- Plain-language contact paths for support, privacy, and refund requests.
Video, audio, and digital materials
Advancing AI uses video heavily. We aim to provide captions or equivalent text for customer-facing spoken content and to avoid relying on audio alone to communicate a required action. Some demonstration media may still be in the process of receiving complete captions, transcripts, or audio description.
If a video, PDF, template, or lesson is not usable with your assistive technology, contact us and identify the item. We will make a reasonable effort to provide the information in an accessible alternative format.
Known limitations
Third-party video players, checkout interfaces, linked platforms, generated documents, or vendor widgets may have accessibility behavior outside our direct control. AI-generated captions and transcripts can also contain mistakes and should be reviewed.
We are continuing to test page structure, keyboard use, zoom, mobile reflow, text alternatives, and media support as the site evolves.
Request assistance or an alternative format
Use the Contact page and put “Accessibility Request” in the subject. Include the page or product, the format or assistive technology involved, and the best way to reach you. Do not include medical information unless it is necessary to explain the requested format.
We target an initial response within two business days. Complex remediation or alternative-format work may take longer, but we will explain the expected next step.
Accessibility feedback
If something is difficult to see, hear, understand, navigate, or operate, please report it. Specific page URLs, screenshots, browser details, or assistive-technology information are useful but not required.
Feedback is used to prioritize practical fixes. No one should have to write a standards brief just to tell us a button is impossible to use.