TRANSPARENCY & YOUR CHOICES

Accessibility statement

How to use Coduf’s web interface and report an accessibility barrier.

Our approach

The web interface is designed around readable content, keyboard-accessible navigation, descriptive controls and responsive layouts. Automated checks can identify some issues but do not establish that every page works with every assistive technology. This statement does not assert a formal certification or complete conformance across every product surface.

Navigation and reading

Use the skip link to reach the main content. Headings organize articles and policy sections. Browser zoom and operating-system text settings can help adjust reading size. Resource pages include section links, and informative images should have descriptive alternative text. Decorative artwork should not carry essential information.

Forms and content authoring

Form labels should identify their controls. Rich-text editing uses Tiptap and supports keyboard interaction alongside formatting controls. Authors must still supply meaningful headings, link text and alternative text for uploaded images. A capable editor does not automatically make uploaded content accessible.

Motion and visual presentation

Where supported by the interface, reduced-motion preferences disable optional transitions. The website uses a light presentation; it does not promise a separate dark theme. Screenshots show the product and should be accompanied by text explaining the relevant feature rather than being the only way to understand it.

Known limitations and review

Automated results cover a particular page and test configuration. Uploaded images, author-written text, external services and the desktop application require their own review. If you cannot complete a task, report the actual barrier rather than relying on a score to describe your experience.

Report a barrier

Use the support contact published on the site. Include the page address, what you tried to do, the browser and assistive technology if relevant, and what happened. Do not include passwords or private project files. A reproducible example helps identify the problem without exposing unnecessary personal information.