Skip to content

Last reviewed:

Accessibility

How accessible AdCrunch is, what does not work yet, and how to tell us about a problem.

We want each person to be able to use AdCrunch, with a keyboard alone or with a screen reader. This page gives our target, our status, and the problems that we know about.

Our target

Our target is the Web Content Accessibility Guidelines (WCAG) 2.2, Level A. The target applies to each part of AdCrunch that you see in a browser:

  • this website, adcrunch.dev;
  • the documentation, docs.adcrunch.dev;
  • the sign-in pages;
  • the AdCrunch console.

Status

AdCrunch partially conforms to WCAG 2.2 Level A. “Partially conforms” means that some content does not meet all the Level A criteria yet. The known gaps are in the next section.

Known gaps

  • The manual review is not complete. Automated tests check our pages, but an automated test finds only part of the problems. We have not yet checked each criterion by hand on each page.

Content from other companies

Some parts of AdCrunch come from other companies. They are outside our target, because we do not control them:

  • The layout of the documentation. The navigation, the search and the page frame of docs.adcrunch.dev come from Blume, a documentation framework. On a wide screen, the search button shows “Search ⌘K”, but its name for a screen reader is “Search”. An automated test reports this as a failure of WCAG 2.5.3.
  • The Support widget. PostHog supplies the Support widget. We have not tested it.
  • YouTube videos. The video player in a blog article comes from YouTube. Some videos in blog articles belong to other people. Some of these videos have no captions.

How we check

  • Automated tests run on each change to our code. They check our components, and the built pages of this website, the documentation and the sign-in pages, against the Level A rules of the axe-core tool.
  • We also check some pages with a keyboard alone.

Tell us about a problem

If a part of AdCrunch does not work for you, write to hello@adcrunch.dev. Tell us the page, what you tried to do, and the browser and the assistive technology that you use. We reply within five working days.