Skip to main content

Accessibility

Making Orbis Sign easier to use

We aim to make the public website and core signing journeys usable with a range of browsers, devices and assistive technologies. This statement is limited to checks we can substantiate.

Statement reviewed: 10 September 2026

Our approach

Orbis Digital Ltd operates Orbis Sign. We use semantic HTML, visible labels, keyboard focus styles, responsive layouts and text alternatives as practical foundations. We do not currently claim conformance with WCAG 2.2 at a particular level, and this statement is not an accessibility certification.

What has been checked

A static review of the public marketing templates checked heading order, page-level headings, footer landmarks, meaningful image alternative text, declared image dimensions, keyboard-focusable calls to action and minimum 44-pixel targets for key navigation actions. Reported heading skips in the shared footer were corrected.

These checks did not constitute a complete manual screen-reader audit, keyboard audit of every application workflow, or testing across every browser and assistive-technology combination. No independent accessibility audit has been represented.

Accessibility basics

  • Pages use a single main heading followed by structured section headings.
  • Navigation and major actions have visible keyboard focus treatments.
  • Form controls on the public contact form have programmatic labels and validation messages.
  • Layouts adapt for phone, tablet and desktop widths without requiring a desktop-only menu.
  • Marketing photographs use descriptive alternative text where they communicate information; decorative imagery can be ignored by assistive technology.
  • Content does not rely on colour alone for the meaning of legal, help and security information.

You can use browser zoom and operating-system text settings. Results can vary in document-editor and PDF-rendering areas where spatial placement is part of the task.

Known limitations

  • The visual PDF editor relies on placing fields at positions on document pages and may be difficult to operate with a keyboard or screen reader.
  • Uploaded PDFs are supplied by Customers. Their reading order, tagging, contrast, form semantics and alternative text are outside the public site's control.
  • Some dense application tables and document previews may require horizontal navigation or magnification on small screens.
  • We have not verified every third-party hosted billing page against the same checks.
  • A complete screen-reader and voice-control test record for every account, administration and signing path is not available.

Customer documents and signing

Customers are responsible for the accessibility of PDFs they upload and for choosing a signing process suitable for their recipients. If a recipient cannot use the standard signing journey, the sender should consider an accessible source document or a reasonable alternative process. Do not send private documents or signing links through the public contact form.

Accessibility feedback

If an accessibility barrier prevents you from getting information or completing a task, use our contact form or email . Tell us the page or step, what you were trying to do, and the browser or assistive technology involved if you are comfortable doing so. Select technical support and avoid including passwords, one-time codes, signing links or document contents.

Report an accessibility barrier