Accessibility Statement

Cloudlayer wants its website, application, hosted forms, signing experiences, documentation, and support to be usable by people with disabilities. Cloudlayer’s product target is the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA for customer-facing hosted experiences and core product workflows.

This statement is a commitment and status disclosure, not a claim that every Cloudlayer surface has been independently certified or fully conforms to WCAG 2.2 AA.

Measures

Cloudlayer includes accessibility in design, implementation, and release work through measures such as:

• semantic HTML, heading order, labels, landmarks, and meaningful link text;
• keyboard operation and visible focus;
• color-contrast and non-color cues;
• responsive layouts, text resizing, reflow, and reduced-motion support;
• accessible names and state for interactive controls;
• validation messages and instructions associated with the relevant fields;
• automated accessibility checks, keyboard walkthroughs, and representative screen-reader testing;
• accessibility review of shared components and customer-facing form and signing patterns; and
• a documented route for feedback, investigation, and remediation.

Customer-authored content affects the accessibility of documents, templates, forms, media, and embedded material. Cloudlayer provides structure and controls, but Customer remains responsible for headings, reading order, alternative text, labels, contrast, language, captions, document tagging, and the accessibility of external content it supplies.

Assessment status

Cloudlayer uses automated and manual testing during development. The Service has not been represented as independently certified for WCAG 2.2 AA. A formal conformance statement will identify the evaluated version, scope, method, date, and known exceptions after the required assessment is complete.

Known limitations

Complex customer-authored HTML, imported files, captured third-party webpages, generated PDFs, external integrations, and early or beta editor features may contain accessibility limitations that Cloudlayer cannot automatically correct. A visual match to source material does not ensure an accessible reading order or tagged document.

If a workflow is inaccessible, contact us so we can investigate the affected route and offer an available alternative. Do not include passwords, private keys, or unnecessary sensitive data in a report.

How can you send accessibility feedback?

Email support@cloudlayer.io with the subject “Accessibility feedback” and include:

• the page, form, document, or workflow involved;
• the task you were trying to complete;
• the browser, device, and assistive technology, if relevant; and
• a description of the barrier and any preferred contact method.

Cloudlayer will acknowledge the report, investigate it, and communicate the disposition or available workaround. Accessibility requests involving Customer-operated content may be shared with that Customer so it can address content it controls.

The Privacy Notice explains how report data is handled. The Security page describes the maintained security posture, and the Terms of Service govern use of the Service.