Last reviewed: 2 November 2026

We want the public oCMS website to be usable with a keyboard, on small screens and with assistive technology. Our target is the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA. A complete conformance assessment has not been performed; this page describes the checks we have run and the limits of those checks.

This statement covers ocms.tech. The separate shared demo, GitHub and other linked websites have their own interfaces.

Jump to using the site, tested coverage, limitations, or feedback.

Using the site

  • Use Skip to content at the start of the keyboard tab order to reach the main page content.
  • Use Tab and Shift+Tab to move between controls, and Enter or Space to activate the appropriate control. Focus indicators identify the selected link or button.
  • The mobile menu, platform tabs, troubleshooting disclosures and documentation links can be operated with a keyboard.
  • Code examples remain readable when JavaScript is unavailable. If a copy button cannot access the clipboard, it selects the example for manual copying.
  • Long code lines scroll inside their code block. Text outside those examples wraps to the page width.
  • Images have text alternatives; documentation screenshots also have captions and can be opened at full size.

What we checked

The latest site review used Chromium, Firefox and Playwright WebKit at viewport widths of 320, 390, 768 and 1280 pixels. The automated checks cover selected navigation, keyboard focus, search, image loading, code-copy fallback, native disclosures, no-JavaScript rendering and horizontal page overflow. Desktop and mobile screenshots were also inspected.

WebKit testing provides Safari-engine coverage; it is not a native Safari or physical iPhone test. These checks do not establish complete WCAG conformance. We do not currently claim testing with NVDA, JAWS, VoiceOver or assistive-technology users, and do not claim a guaranteed loading time on a mobile connection.

Known limitations and practical alternatives

  • Admin screenshots: fine interface text can be difficult to read at phone width. Use the full-size image and the accompanying written instructions.
  • Code examples: long commands may require horizontal scrolling within the example. Select or copy the text into an editor if that is easier to read.
  • Consent and verification controls: the site uses Klaro for cookie choices, and hCaptcha on protected sign-in screens. These interfaces need separate assistive-technology testing. Contact us if either prevents access.
  • External services: GitHub, the demo, embedded or linked media, and other websites are outside this site's test coverage. You can email us about project documentation instead of using GitHub.

Report a barrier or request another format

Email webmaster@ocms.tech. Include the page URL, what you were trying to do, the barrier, and your browser or assistive technology if relevant. Tell us if a plain-text explanation or another format would help. Do not include account passwords, recovery codes or other secrets.

We review reports and use them to prioritize improvements. Related information: Privacy Policy, Cookie Policy, and documentation.

Source: https://ocms.tech/accessibility-statement