Accessibility Statement

1. What This Statement Covers

This statement covers learningcortex.com, the Learning Cortex web application, and the Learning Cortex mobile applications for iOS and Android. It does not cover third-party websites we link to, or study material that an institution or a student uploads into the product. Both are addressed under Known Limitations below.

2. Conformance Target

We hold Learning Cortex to the Web Content Accessibility Guidelines (WCAG) 2.1 at Level A and Level AA. That is the standard incorporated by Colorado’s technology accessibility rule, 8 CCR 1501-11, and it is the version we currently test and remediate against.

WCAG 2.2 Level AA is our forward target. New interface work is written against the 2.2 success criteria, but we have not finished assessing the existing product against them, so we do not claim conformance with 2.2 today.

3. Current Status

Learning Cortex is partially conformant with WCAG 2.1 Level AA. Partially conformant means that most of the product meets the standard, and that some parts of it do not.

We have completed substantial remediation across both the web and mobile applications, described in the next section. Known gaps remain, and they are set out in Section 5.

4. Measures We Have Taken

• Colour is defined once, in a shared set of design tokens, so a contrast correction reaches every screen that uses the token. Field borders and interactive states that fell below the 3:1 and 4.5:1 thresholds have been re-cut.
• Interactive controls can be reached and operated from the keyboard, in a predictable order, with a focus indicator that stays visible. Marketing pages carry a “Skip to main content” link ahead of the repeated navigation.
• Structure is carried in the markup rather than in appearance alone: headings, labelled form fields, button and dialog semantics, and live regions that announce work which finishes on its own, such as an upload completing, a quiz being generated, or an answer being graded.
• The mobile application permits pinch-zoom, and its document viewer renders a real text layer rather than a flat image of the page.
• An accessibility rule set (jsx-a11y) runs in our linter across the codebase, catching markup faults such as an image with no text alternative, or a click handler on an element the keyboard cannot reach.

5. Known Limitations

Material uploaded by institutions and students

We display documents as their authors made them. A scanned PDF is a photograph of a page, and no viewer can make it conformant. Our pipeline extracts a text layer, running optical character recognition when a document arrives without one, so that the words can be read aloud, searched, and selected. That does not repair the document: heading structure, reading order, table relationships, and descriptions of figures cannot be recovered from an image, and we do not invent them. If you have been assigned material you cannot read, tell us and we will work with you, and with your institution where that is relevant, to obtain an accessible copy.

AI-generated content

Quizzes, flashcards, summaries, explanations, and chat replies are generated. They are delivered as real text, so a screen reader can read them, but their wording, their ordering, and any reference they make to a visual are model output. We cannot guarantee that every generated item meets every success criterion. The cases we see are an explanation that leans on a diagram and a question whose image is described thinly. Report any that block you and we will supply the material another way.

Third-party surfaces

Parts of the experience are operated by other companies and shown inside our product. We do not control their code. These are sign-in and account management (WorkOS), payment and subscription management (Stripe), the cloud file pickers for Google Drive, OneDrive, and Notion, and the embedded player used for video lectures. We raise defects with these vendors, and we cannot fix their interfaces ourselves. If one of them blocks you, contact us and we will complete the task with you by another route.

6. How We Assess

Our assessment is a self-evaluation. It combines manual keyboard walkthroughs of the primary flows, screen-reader checks of those same flows, contrast measurement against the design tokens, and automated rule-based scanning during development. We have not yet commissioned an independent third-party audit or published a VPAT / Accessibility Conformance Report. When we do, we will link it from this page.

7. Report a Barrier

If any part of Learning Cortex blocks you, tell us. Email reaches us directly and needs no account, so you never have to get through the product to report that the product is in your way. If you are signed in, the in-product contact form reaches the same inbox.

• Email: support@learningcortex.com — the subject line Accessibility routes it fastest.

It helps if you can name the page or screen, say what you were trying to do, and tell us which assistive technology you use. None of that is required. A single sentence is enough for us to start.

8. Accommodations and Alternative Formats

You can ask us for an accommodation, or for material in an alternative format. That includes a plain-text or large-print copy of this statement, our Privacy Policy, or our Terms of Use, and it includes an accessible version of a document assigned to you inside the product. Use any of the contacts in Section 7.

We acknowledge every accessibility report and request within 2 business days and give a substantive response within 5 business days. Where a fix will take longer than that, we tell you what we are doing, when we expect it to be done, and how to complete the task in the meantime.

9. Institutions and Escalation

If you are evaluating Learning Cortex for a school, college, or university, you can request our current accessibility documentation and our remediation plan through the contacts above. If you are a student or a member of staff at an institution that already uses Learning Cortex, you may also raise the issue with your institution’s accessibility or disability services office. We work with those offices directly.

10. Review of This Statement

This statement was last reviewed on August 28, 2026. We review it at least once a year, and again after any significant change to the product or to the standard we are held to.