Accessibility Statement

We want Ofivio to be usable by everyone who has to use it — including people who navigate by keyboard, use a screen reader, need larger text, or cannot rely on colour to tell things apart.

We work toward WCAG 2.1 Level AA. We do not currently claim to conform to it. This is a large application with a long history and parts of it fall short. The honest position is that this is an ongoing effort, and section 3 says where the gaps are.

• Semantic HTML — real headings, lists, buttons and landmarks.
• Keyboard operation of navigation, forms and interactive controls, with a visible focus indicator.
• Focus handling for dialogs and menus: focus moves in, is trapped while open, and returns where it came from on close.
• ARIA roles and labels on custom controls.
• Text contrast checked against AA on the public pages and on the main application surfaces.
• Light and dark themes, both contrast-checked, with the preference remembered.
• Responsive layouts that work zoomed in and on small screens.
• Alternative text on images that carry meaning; decorative art is marked as decorative so screen readers skip it.
• Motion kept to a minimum by design — there is very little animation to disable.

These are the areas we know are not yet at the standard we want. This list is maintained rather than decorative:

• Charts and data visualisations convey information visually and do not all have a text or table alternative yet. Where a chart matters, the underlying figures are available in the corresponding report or list view.
• Dense tables — bills of quantities, ledgers, schedules — are wide, scroll horizontally, and are demanding to navigate with a screen reader. Improving the header association and keyboard model on these is active work.
• Drag-and-drop surfaces such as the planning boards, the Gantt view and whiteboards have limited keyboard equivalents.
• PDF output generated by the platform is not reliably tagged for screen readers.
• Older screens that predate our current design system are inconsistent in focus styling and labelling.
• The mobile application has had less accessibility testing than the web application.

Assessment is by internal review — automated checks plus manual keyboard and screen-reader testing. We have not commissioned an independent third-party audit, and we will say so here when we do.

Please tell us. A specific report is worth more than any statement on this page.

Write to contact@ofivio.com with Accessibility in the subject, or open a ticket at the Help Desk. It helps if you can say which page, what you were trying to do, and what you are using — browser, and screen reader or other assistive technology if any.

We aim to reply within 5 business days with either a fix, a workaround, or a timescale. If something is blocking you from doing your job, we will find you a way through it in the meantime — including doing it for you while we fix the underlying problem.

This statement applies to ofivio.com and the Ofivio web application. Our free-tools site ofivio.xyz and our mobile applications are built to the same intent but are covered by their own testing, which is less mature. Content served by third parties — advertising on the tools site, embedded provider widgets — is outside our control.