Skip to content
  • AdaChecked
  • ← Back to site
Accessibility

Accessibility Statement

Effective: September 18, 2026 · Version 1.1

On this page

  1. Our commitment
  2. Conformance status
  3. Measures we take
  4. Known limitations
  5. Technical specifications
  6. Assessment approach
  7. Feedback
  8. Enforcement
  9. About this statement

1. Our commitment

AdaChecked builds tools that measure web accessibility. We hold this site to the standard we report against for our customers, and we publish where it currently stands rather than only the parts that look good.

This statement applies to adachecked.com. The AdaChecked web application at app.adachecked.com is covered by its own assessment, which is in progress.

2. Conformance status

Conformance has not been fully determined. We are not claiming a conformance level for this site yet. Automated testing across every public page returns no violations, but a full assessment requires manual and assistive-technology testing that has not been completed. W3C distinguishes partial conformance, which means known failures in identified content, from content that has not been evaluated — this site is currently the second. We will state a conformance level when the assessment supports one, and name the known failures at that point.

An automated audit of every public page on this site on 18 September 2026, run with axe-core against the WCAG 2.0, 2.1 and 2.2 A and AA rulesets, returned no violations across 22 pages, tested without waiting for scroll animations to settle. That result is narrower than it sounds and we would rather state the limit than let the number stand alone: the same run reported about 1,900 elements whose contrast it could not resolve, because they sit on gradient or layered backgrounds where no single effective colour can be computed. axe records those as undetermined rather than as passes. We checked them by hand and found one genuine failure — body text at 2.15:1 against the 4.5:1 threshold, in the section of the home page that publishes these figures — which was fixed the same day. We are not claiming any conformance level on the strength of any of this. Automated testing detects a majority of issues by volume but only roughly a fifth to a third of WCAG's success criteria are machine-testable at all; the remainder — screen-reader announcement quality, focus order through a whole task, meaningful alternative text, and whether a page is genuinely operable end to end — requires manual and assistive-technology testing. That work is scheduled and this statement will be updated with its findings and date.

3. Measures we take

  • Accessibility is reviewed as part of the normal development process, not as a release gate at the end.
  • Every page is tested against the WCAG 2.2 A and AA rulesets with automated tooling before it ships.
  • Semantic HTML, a single H1 per page, landmark regions, and a skip link are structural requirements rather than preferences.
  • Interactive components follow the WAI-ARIA Authoring Practices, including keyboard operation and visible focus.
  • Motion respects the prefers-reduced-motion setting.
  • Contrast is checked against the 4.5:1 body-text and 3:1 non-text thresholds, and colour is not used as the only way information is conveyed. A September 2026 review found and fixed a focus indicator at 1.18:1 and several secondary text colours below 4.5:1. A second review on 18 September 2026 found body text at 2.15:1 on a dark section, caused by two stylesheet rules of equal specificity where the later one won; it was fixed the same day and the rule was rescoped so the pattern cannot recur. We mention both because a list of measures with no failures in it is not a credible one.

4. Known limitations

We list these because an honest statement is more useful than a clean one:

  • A full manual and screen-reader audit of this site has not yet been completed. Until it is, the conformance claim above stays at partial.
  • Some marketing pages use scroll-triggered reveal animation. It is suppressed for visitors who ask for reduced motion, but it has not been tested with every assistive-technology combination.
  • Product screenshots on the marketing pages carry descriptive alternative text, but a dense dashboard or a page of a report is hard to convey fully in one string. Where a screenshot carries an argument, the surrounding copy states that argument in text as well, so nothing on this site depends on seeing an image.
  • PDF reports produced by our products are generated from scan data. We are working toward tagged, fully accessible PDF output and are not there yet.
  • Content embedded from third parties, including the Sanity editing environment at /studio, is outside our direct control. /studio is a staff-only surface and is not part of the public site.

5. Technical specifications

Accessibility of this site relies on HTML, CSS, JavaScript and WAI-ARIA. It is built to work with current versions of the major browsers together with the assistive technologies commonly paired with them.

6. Assessment approach

This site has been assessed by self-evaluation, using automated tooling across every public page together with manual keyboard and structural review. It has not yet been assessed by an independent third party. When it is, we will say who did it and when.

7. Feedback

If you hit a barrier on this site, we want to hear about it, and we treat it as a defect rather than a suggestion.

Email — hello@adachecked.com

Contact form — adachecked.com/contact

We aim to respond within one business day. Please tell us the page, what you were trying to do, and the browser and assistive technology you were using, if you know them — it makes the problem far faster to reproduce.

8. Enforcement

If you are not satisfied with our response, you may be able to escalate to the enforcement body in your jurisdiction — for example the U.S. Department of Justice under the ADA, a national enforcement body under the European Accessibility Act, or the relevant provincial authority under the AODA in Canada. Nothing in this statement limits those rights.

9. About this statement

This statement was prepared on 14 September 2026 and last revised on 18 September 2026, and reflects the state of the site on that date. It is reviewed whenever the site changes materially, and at least every six months.

AdaChecked does not provide legal advice, and this statement is not a representation that the site meets any particular legal requirement.

© 2026 AdaChecked
  • Home
  • Terms
  • Privacy
  • Contact