Skip to content
DOCUGRIP©

Accessibility statement

We build a tool that checks other people's documents for accessibility, so it would be poor form not to say where we stand ourselves. Everything below was measured on the production build, and anything we did not measure is listed as not measured.

Target
WCAG 2.1 Level AA
Status
Partially conformant
Last measured
13 August 2026

What we measured

Counted on the production build across the home page, a tool page, the accessibility checker, the OCR tool and the pricing page.

  • Page language is declared5 of 5 pages checked. Screen readers pick pronunciation from this.
  • One h1 per page, no skipped heading levels5 of 5 pages. Zero level jumps found.
  • Skip link worksFirst element in tab order, and it becomes visible when focused.
  • Landmarks presentmain, nav, header and footer on every page checked.
  • Text contrast400 elements measured on the home page against their computed background. Zero below the 4.5:1 threshold (3:1 for large text).
  • Keyboard focus is always visibleThis one failed until we measured it: the stylesheet removed the browser's focus ring everywhere and only put it back for components that opted in. Icon-only buttons had no indicator at all. The default is now inverted.
  • Images have alternative textZero images without an alt attribute; zero links without an accessible name.
  • Target size62 targets are smaller than 24×24 px, but all of them keep at least 24 px of spacing, which is the exception WCAG 2.2 allows. Zero real failures.
  • Reduced motion is honouredAnimations stop when the system asks for less motion.

What we have not measured, and what is missing

A statement is only worth reading because of this section. Listing what passes is easy; listing what does not is what makes it checkable.

  • Not tested with real assistive technologyNo run with NVDA, JAWS or VoiceOver. Automated checks cover only part of WCAG; a screen reader can be technically satisfied and still unusable.
  • Five pages sampled, not 480The site has more than 480 pages. They share the same components, so the result should hold, but 'should' is not 'was measured'.
  • The PDFs we generate are not taggedOur resume builder sets the document language and title, but produces no tag tree — so a resume made here would fail two checks in our own accessibility tool. Building a tag tree is not something our writer supports yet. We are saying it rather than hiding it.

Tell us what broke

If something here is unusable with your setup, write to us and say which page, which assistive technology and what happened. We treat it as a defect, not a request.

support@docugrip.com