Skip to main content

Accessibility statement

Crash That Course is run by Unicorn Flames LLC. We want everyone to be able to use this site and our classes. This page says how accessible the site is today, what we know is not right yet, and how to get help.

Conformance status

The Web Content Accessibility Guidelines (WCAG) set out how to make web content usable for disabled people. They have three levels: A, AA and AAA.

crashthatcourse.com is partially conformant with WCAG 2.2 level AA. That means some parts do not fully meet the standard yet. They are listed under Known limitations.

What this statement covers

  • Every page on crashthatcourse.com, including the blog.
  • The Salesforce Workforce Navigators training page, its two videos, captions and transcripts.
  • Our class surveys and their results pages.
  • The talk video and transcript on the How we teach page.

Some parts come from other companies: the Google Calendar booking page, the YouTube player and the Cloudflare Stream player. We chose them with care, but we cannot change how they are built. Their known problems are listed below, with a way around each one.

What we do

On this site

  • Every page works with a keyboard alone, with a visible focus outline and a link to skip to the main content.
  • Text and controls meet the WCAG AA color contrast ratios, and most text meets the stricter AAA ratio.
  • Pages reflow to a 320 pixel wide screen without side scrolling, and work when text is enlarged to 200 percent.
  • Videos never play on their own. Nothing loads from YouTube or Cloudflare Stream until you press Play.
  • Our own training videos have checked captions and a full transcript that also describes what is on the screen.
  • Survey questions have labels, say which answers are required, and tell you exactly which answer is missing.
  • If your device is set to reduce motion, the site does not animate.

In our classes

We describe every slide out loud and put every prompt in the chat as text. We start on the free AI plans. You can read more on how we teach.

Known limitations

  • No audio description track on our videos. Instead, each transcript describes what is on the screen at each point, such as slides, forms and menus. If you need the video itself with audio description, email us and we will work out a version with you.
  • The Tech Week talk on the How we teach page. It is part of a longer YouTube stream, and YouTube's automatic captions for it contain errors. A checked transcript and a checked caption file are linked next to the video.
  • The YouTube and Cloudflare Stream players. Automated tests report some problems inside these players, such as unlabeled controls and low contrast. We cannot change them. Every video on this site has a transcript, and our own videos can be downloaded to play in any player you like.
  • The Google Calendar booking page. Google builds this page. If it does not work for you, email us and we will book a time with you another way.
  • Email addresses on the live site. Our hosting provider can hide email addresses from spam robots, which sometimes shows a placeholder instead of the address to screen readers. The address is [email protected].
  • No outside audit yet. We test the site ourselves. An outside accessibility audit has not been done yet.

Feedback and other formats

If something on this site or in a class does not work for you, or you need something in another format, email [email protected]. Tell us what you need, or what is not working, and we will work out the fix with you. You can ask before a class, during it or after it.

We reply within 2 business days.

You never need to explain a diagnosis. Tell us what would help. That is enough.

If you are a program lead, you can raise access needs for your cohort on the booking call or at any time after it.

How we tested

We assessed this site ourselves on November 8, 2026. We used:

  • Keyboard-only testing of every page, the video players, the embed dialog and the survey forms.
  • Automated checks with axe, Pa11y and Lighthouse on every page, and the IBM Equal Access checker during an earlier audit.
  • Manual checks of color contrast, page titles, headings, link text, captions and transcripts.
  • A reflow check at 320 pixels wide.

We have not yet tested with the NVDA or JAWS screen readers. That is next on our list.

Technical details

The site relies on HTML, CSS and WAI-ARIA to work with your browser and any assistive technology. Some features, such as the survey checks, the video players and the embed code dialog, also need JavaScript.

It is built to work with current versions of Chrome, Edge, Firefox and Safari, on desktop and on phones.

If you are not happy with our reply

Email Tim Haines, the owner, at [email protected] and put "Accessibility complaint" in the subject. He reads these himself.

If you are in one of our classes through a program, you can also tell your program lead, who can raise it with us directly.

You can also file a complaint with the U.S. Department of Justice, Civil Rights Division, at civilrights.justice.gov.

Date of this statement

This statement was written on November 8, 2026, after a full review of the site. We review it whenever the site changes in a big way, and at least once a year.