Accessibility
Datakoot aims to meet WCAG 2.1 Level AA, which covers the WCAG 2.0 Level A and AA criteria incorporated by reference into the Revised Section 508 Standards (36 CFR Part 1194). This page states what we tested, what we found, and — just as importantly — what we have not tested.
Report date: 29 August 2026 · Product: datakoot.com website and documentation · Contact: [email protected]
How this was tested
Automated testing used axe-core 4.13.0 driven through Chromium, run against 11 representative pages covering every template on the site: the home page, pricing, onboarding, the guides index, a guide article, three of the nine server pages, terms, the post-purchase page, and the 404 page.
Results: 0 violations, with 212 rule-checks passing across those pages and 27 distinct rules exercised.
Automated tools detect only a portion of accessibility barriers. The following were additionally checked by hand:
- Keyboard operation — the first Tab stop is a working “Skip to content” link; 30 sequential Tab stops were walked on the home page; a visible focus indicator was confirmed by screenshot.
- Reflow (1.4.10) — all ten page types were checked at a 320 px viewport. All reflow without horizontal scrolling.
- Contrast (1.4.3) — every text colour token was computed against the page background: body text 16.81:1, secondary 9.20:1, tertiary 4.98:1, brand blue 5.82:1, cyan 10.37:1. All exceed the 4.5:1 threshold for normal text.
- Motion (2.3.3) — with
prefers-reduced-motion: reduce, animated counters render their final values immediately and reveal animations are disabled. - Structure — one
<h1>per page, a single<main>landmark, labelled navigation regions, and a declared page language.
Conformance summary
| Component | Standard | Status | Notes |
|---|---|---|---|
| datakoot.com website & docs | WCAG 2.1 AA | Supports | Tested as described above. No known defects. |
| MCP API endpoints | WCAG 2.1 AA | Not applicable | Machine-to-machine JSON-RPC. No user interface, no human-perceivable content. |
| Chrome extensions (nine) | WCAG 2.1 AA | Not yet evaluated | Each has a browser popup interface. These have not been formally tested and are not claimed as conforming. |
| Per-server landing pages | WCAG 2.1 AA | Partially evaluated | Served from the API subdomains and normally redirected to the equivalent page on datakoot.com. Not separately audited. |
| Billing & account portal | WCAG 2.1 AA | Third party | Operated by Polar. Their conformance is theirs to state, not ours. |
Known limitations
We would rather tell you these than have you find them.
- No assistive-technology testing has been performed. The site has not been evaluated with JAWS, NVDA, VoiceOver or Dragon. Conformance is asserted from automated and manual inspection only.
- The nine Chrome extensions have not been audited. If an extension is part of what you are procuring, tell us and we will test it and report honestly before you buy.
- Two axe rules returned “needs review” rather than pass or fail — colour contrast over the animated background, and one ARIA attribute usage. Contrast was subsequently verified by direct computation against the background colour, as listed above.
- No third-party audit has been commissioned. This report is a self-assessment, which the Section 508 program permits but which carries less weight than an independent review.
Legal basis and scope
Section 508 of the Rehabilitation Act (29 U.S.C. §794d) binds federal agencies in what they procure and use; it does not directly bind private companies. The obligation reaches a vendor through the terms of a contract. The Revised 508 Standards incorporate WCAG 2.0 Level A and AA by reference. We target WCAG 2.1 AA, a strict superset of that, because agency solicitations commonly ask for it.
This document is an Accessibility Conformance Report in substance. A formal VPAT®-format edition is available on request for procurement files.
Found a barrier?
Email [email protected] with the page and what went wrong. It reaches the person who builds the site, not a queue. Accessibility defects are treated as functional defects, not feature requests.