Accessibility statement

1 What we are aiming for

The target is WCAG 2.1 level AA. This is a statement of intent and of current effort — it is not an audited conformance claim, and it is not signed off by a third party. Where the two differ, the honest version is the one below.

2 What is implemented

Pages are built from semantic HTML with real headings, landmarks and lists. Every form control has a label bound to it. Interactive elements are reachable and operable with a keyboard and show a visible focus ring. Colour is never the only carrier of meaning. Decorative artwork is marked so a screen reader skips it. Text scales with the browser's own size setting.

The public pages work without JavaScript — the language and country switcher, the navigation and the enquiry form all function with scripting switched off. Hebrew and Arabic get a right-to-left layout that is designed rather than mirrored, and numbers, dates and identifiers inside them are isolated so they read in the correct direction.

3 Known gaps

The document editor is a dense table and is harder to operate with a screen reader than the rest of the product. Some long data tables on the country pages scroll horizontally on a narrow screen. Printed output has been tested in recent desktop browsers only. None of these has been formally evaluated against every success criterion.

4 How it is tested

By hand: keyboard-only passes, a screen reader on the main flows, contrast checks against the palette, and rendering at 200 percent text size. There has been no external accessibility audit and no certification. When there is one, it will be named and dated here.

5 Reporting a problem

Write to support@docsorigin.com and describe what you were trying to do, on which page, and with what assistive technology. A specific report — the page, the control, what happened — is worth more than any automated score, and it gets a human answer.

6 If you are blocked right now

Say so in the same message. Something that stops you completing a document is treated as an outage, not as a feature request, and it goes to the front of the queue.