Accessibility is Ockem’s business — we help organizations make their documents accessible and prove it. This page describes where our own website stands, how we test it, what we know is not yet right, and how to reach us if something gets in your way.
Scope
This statement covers the public pages of ockem.com. It does not cover the Ockem Proof application at proof.ockem.com, including its free-trial pages and the shared scorecard and certificate pages linked from this site. The application will get its own evaluation and statement; until then we make no conformance claim for it and do not publish an Accessibility Conformance Report (ACR).
Conformance status
Our target is WCAG 2.2 Level AA. ockem.com is partially conformant: some content does not yet fully meet that standard, as listed under Known issues below.
The site is built with semantic HTML landmarks, a skip-to-content link on every page, keyboard-operable navigation, and color contrast checked against the AA thresholds on our light and dark surfaces. Animations play once and are switched off when your system asks for reduced motion (prefers-reduced-motion). Most finish within five seconds. Two run longer, and each has its own pause control: the home page’s opening animation, and its four short demonstrations of the calls left for you, which play one after another.
How we test
- Automated checks on every change — our build pipeline loads every public page of ockem.com in a browser and scans it with axe-core against the WCAG 2.0, 2.1 and 2.2 Level A and AA rules, and checks that every page reflows without sideways scrolling at widths from 320 to 1440 pixels. A page that fails either check fails the pipeline, and we fix it before releasing.
- Manual review — our most recent manual review, of keyboard-only navigation and focus order in the navigation, forms and trial links, was completed on July 19, 2026, before the site was redesigned in October 2026. Automated checks find only part of what a person finds, so we treat this as the evaluation most in need of repeating.
Known issues
- Pages on proof.ockem.com. Some pages this site links to, such as the sample scorecard, are part of the Proof application and outside this statement. They have known issues, identified on October 5, 2026, that the product team is fixing.
- A deliberate low-contrast specimen. The illustrations of color contrast on the rule page and on the home page show a low-contrast text sample, because it is the example failure the product is shown fixing. It is not needed to understand the page: the rule page’s illustration is hidden from assistive technology, and the home page’s has a text description that names the colors and their ratios.
If our checks or your feedback surface another issue we cannot fix immediately, we will list it here with a workaround.
Fixed on October 5, 2026: the screenshots of the sample certificate, its verification page and the sample scorecard, and the “How it works” illustrations on the home page, now carry a one-sentence text alternative, with the full transcription in a visible “Text version” under each image.
Technologies relied upon
ockem.com relies on HTML, CSS, WAI-ARIA and JavaScript, together with the browser and any assistive technology you use.
Feedback
If you encounter an accessibility barrier on ockem.com, or in any document or certificate we produce, please tell us: email info@ockem.com or use the contact form. We reply within one business day and fix confirmed barriers as a priority.
About this statement
This statement was prepared on October 5, 2026, from a self-evaluation: the automated checks described above, run on the site as released that day, and the manual review of July 19, 2026. It is reviewed whenever the site changes materially, and next by April 5, 2027. It was updated on October 9, 2026 for the redesigned home and How it works pages.