Skip to content
Platform

Accessibility

Our accessibility commitments, known gaps, and how to report a barrier you hit.

Last updated on October 25, 2026.

ACADA is built to work with a keyboard, a screen reader, larger text and higher contrast, and we aim to meet WCAG 2.2 Level AA. We have not completed a formal audit yet, and some parts of the site, including content made by instructors, fall short. If something stops you using ACADA, tell us. A person replies within 2 business days.

This summary is for orientation only. The sections below are the operative terms.

1. What this covers

This statement covers acada.ac and everything ACADA L.L.C., a Tennessee limited liability company (ACADA, we), builds and runs there: the marketplace, the course player, the Instructor Dashboard and the Editor, rooms and messages, settings, checkout, and the emails we send. It applies to everyone who uses the site, with or without an account.

Content that instructors publish is covered only as described in section 4. Websites of other companies that you reach through links on ACADA are not covered.

2. What we aim for

We design and build ACADA to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. WCAG is the technical standard for accessible websites, and Level AA is the level most accessibility laws refer to.

We do not claim full conformance yet. No formal audit of the whole site has been completed. Section 5 lists what we know falls short, and we update this statement as that changes.

Every change to ACADA's code is checked against accessibility rules before it is released. A change that breaks those rules is not released.

3. What ACADA provides

Keyboard. Every control can be reached and used with a keyboard. A "Skip to content" link is the first Tab stop on every page. The control that has focus is outlined. Dialogs keep focus inside them, close with Escape, and return focus to where you were.

Screen readers. Buttons, links, menus, switches and dialogs have names and announce their state. Navigation areas and the main content are labelled landmarks. Confirmations and alerts that appear at the top of the page are announced. Images we place have text alternatives.

Display. In Settings, under Appearance, you can choose:

  • a theme: Light, Dark, Aqua, Amber, Velvet, or your device's setting;
  • a text size: small, medium or large. Your browser's own zoom also works;
  • increased contrast, which darkens borders and secondary text. It is off until you turn it on. If your device asks for more contrast, we apply it to the policy pages, which carry the smallest text on the site;
  • reduced motion, which turns off animation. If your device asks for reduced motion, we respect that too.

These settings are kept in your browser, not your account, as described in section 3 of the Cookie Policy.

Media and images. A course's preview video shows captions when the instructor has added a captions file. An audio block shows a transcript when the instructor has written one. Images in lessons carry the text alternative the instructor entered.

Time limits. Nothing on ACADA times out while you read, answer a quiz, or write a message. Only sign-in sessions and the one-time codes and links we email you expire.

4. Content made by instructors

Courses, lessons, rooms and articles are written by instructors, not by us. The editor gives every instructor the fields needed to make their content accessible: a text alternative on every image, a captions file on every preview video, and a transcript on every audio block. We ask instructors to fill them in, and to host lesson videos on a service that supports captions.

We do not review content for accessibility before it is published, and we do not remove content for lacking these. When you report a barrier in a course, we contact the instructor, ask them to fix it, tell you that we have, and tell you again when they respond. What instructors must and should include in a course is set out in the Course Content Policy.

5. Known limitations

These are the parts of ACADA we know do not meet the standard in section 2 today.

  • Content from other companies. Videos and other content embedded from YouTube, Vimeo, Loom, Wistia, Figma, Miro and the other services listed in section 4 of the Cookie Policy are built by those companies. Their players, captions and controls are theirs, and we cannot change them.
  • Instructor content. Some courses lack text alternatives, captions or transcripts, because the instructor did not add them.
  • Drawing tools. The whiteboard and the graphing tool are drawing surfaces. Drawing on them needs a mouse, trackpad or touch screen.
  • Dense screens. Some screens in the Instructor Dashboard, the Editor and chat may need horizontal scrolling at the largest text size or on a narrow window.
  • Teal buttons in the dark theme. Button labels on the teal fill are 2.8:1 against it, below the 4.5:1 that WCAG 2.2 AA asks for. Turn on Increase contrast in Settings → Appearance for buttons that meet it.
  • No audit yet. We have not had the whole site tested against WCAG 2.2 by a specialist. There may be barriers we have not found.

6. If a barrier stops you using what you paid for

If a barrier in a course you paid for stops you using it, tell us using the steps in section 7. We will work with the instructor to fix it. If it is not fixed within 30 days of your report, we refund the purchase, as described in the Purchases, Refunds & Subscriptions policy.

We do not promise to produce content in a format the instructor has not supplied, such as a transcript of a whole course. We do promise that a barrier never leaves you paying for something you cannot use.

7. Reporting a barrier

To report something you cannot use, choose "Accessibility barrier" on the support form, or write to support@acada.ac. It helps to include the page, what you were trying to do, and the browser and assistive technology you use.

A person reads every report and replies within 2 business days. If the barrier is in ACADA's own interface, the reply says what we will change and when. If it is in an instructor's content, the reply says that we have passed it to the instructor, and we tell you when they respond.

8. Changes to this statement

When we change this statement, we change the date shown at the top. If a change removes something we provide or a commitment we make, we post a notice in the app at least 14 days before it takes effect. Adding a feature or closing a known limitation takes effect at once.

9. Contact

Questions about accessibility on ACADA go to support@acada.ac.

10. Related policies