Accessibility

The commitment

This site aims to conform to the Web Content Accessibility Guidelines (WCAG) 2.2, level AA. That is the target we build and test against, not a level we certify: nobody has audited this site, and we will not claim a conformance level nobody has measured. The honest description today is partially conformant — the sections below say exactly what that means.

What is tested, on every build

Every page of this site passes an automated static check before it can be published. That check enforces, on every build without exception:

• Exactly one main heading per page, and a heading order that never skips a level.
• A text alternative on every image, and a label on every form control.
• A skip-to-content link, a declared page language, and landmark structure a screen reader can navigate by.
• Link text that says where the link goes, rather than "click here".

The site also avoids the common structural traps by design: no content is conveyed by colour alone, text is real text rather than images of text, the layout reflows at high zoom without horizontal scrolling, and all animation respects prefers-reduced-motion.

What is not tested yet

Checks that need a real browser — measured colour contrast, visible focus order, and a screen-reader walkthrough — are not yet part of the build, and this page will not pretend otherwise. The colour palette was designed to AA contrast ratios, but designed-to is not measured, and the browser-based audit is on the roadmap before launch. When it runs, this page gets updated with what it found.

The application is a separate question

This statement covers cocad.ai, the website. CoCAD the desktop application is still in development and not yet released; its accessibility — keyboard access to every tool, screen-reader support, contrast in the interface — is being built into it now, and it will get its own honest statement when there is a release for one to describe.

Found a problem? Tell us

If anything on this site is hard to use with a keyboard, a screen reader, magnification, or any other assistive technology, please email support@cocad.ai and say what you were trying to do and what got in the way. Reports go to the person who builds the site, not a ticket line — expect a reply within a few business days, and a fix as fast as one is possible. An accessibility report is treated as a bug report, because it is one.