Accessibility Statement
Last updated: 8 September 2026
We want everyone who works on our projects to be able to use the OZ Project Portal. This statement explains how accessible it is today, what does not yet work well, and how to get help or tell us about a problem.
Contents
1. Our commitment
{{COMPANY_LEGAL_NAME}} is committed to making the Portal usable by as many people as possible, including people who use screen readers, magnification, speech recognition or keyboard-only navigation.
The Portal is a private business system rather than a public sector website, so the Public Sector Bodies (Websites and Mobile Applications) Accessibility Regulations 2018 do not apply to it. Our duty to make reasonable adjustments under the Equality Act 2010 does apply, and we take that as the standard to meet.
2. Compliance status
The Portal is partially compliant with the Web Content Accessibility Guidelines version 2.2 at level AA, because of the issues listed in section 4.
This assessment is based on our own review of the application rather than a formal external audit. We say so plainly: we have not yet commissioned an independent accessibility evaluation.
3. What we have done
- Keyboard navigation. The Portal can be operated by keyboard, and every focusable control shows a visible focus ring. Dialogs trap focus while they are open and return it when they close, and the Escape key closes them.
- Colour contrast. Text colours are drawn from a single defined palette chosen to meet the AA contrast ratio. We deliberately avoid using transparency to create "muted" text, because it produces contrast that fails the standard.
- Icon-only buttons have names. Buttons that show only an icon are given an accessible name automatically, including buttons that appear in tables after the page has loaded.
- Status messages are announced. Confirmations and errors are placed in a live region so a screen reader reads them without the user having to hunt for them. Error messages are given a more assertive announcement than confirmations.
- Dialogs are marked up properly, with a labelled title and the correct role, so assistive technology describes them as dialogs.
- Text resizes. Layouts use relative units and reflow rather than breaking when text is enlarged or the window is narrow.
- No motion traps. There is no autoplaying video, no carousel and no content that moves on its own.
4. Known problems
We know about the following. They are on our list to fix.
| Problem | Who it affects | What to do meanwhile |
|---|---|---|
| Reordering by dragging has no keyboard alternative. Folders, table columns and board rows are reordered by dragging them. | Keyboard-only and screen reader users; some people using speech recognition or a pointer with limited precision | Ask a colleague or an administrator to set the order for you. Order is stored per project, so it only needs doing once. |
| There is no "skip to content" link. Keyboard users pass through the navigation on every page. | Keyboard and screen reader users | Use your screen reader's heading navigation to jump to the main region. |
| The drawing, CAD and 3D model viewers are not accessible. They are visual components and cannot be read by a screen reader. | Screen reader users and people with low vision | Download the file and open it in your own software, which may offer better support. Ask us if you need a drawing described. |
| Revit previews are images with no description. The preview is a thumbnail embedded in the file by the authoring software. | Screen reader users | The file's own details — number, revision, status, date — are available as text next to the preview. |
| Large data tables are difficult to navigate. The file and board tables have many columns, and moving through them with a screen reader is slow. | Screen reader users | Column visibility can be reduced per project, which shortens the row considerably. An administrator can set this up. |
| Uploaded documents are usually not accessible. Drawings, scanned documents and PDFs come from third parties and are rarely tagged for screen readers. | Screen reader users | Contact us — see section 6. We will get you the information in a form you can use. |
5. Content we do not control
The Portal's main purpose is to distribute documents produced by architects, engineers and other consultants. We do not control how those documents are authored, and construction drawings are, by their nature, visual. We cannot make a third party's drawing accessible retrospectively.
What we can do is get you the information in it. Please ask — we would much rather do that than have you struggle with a file that was never going to work.
6. Getting help, or telling us about a problem
If you cannot use part of the Portal, or you need information in a different format — larger text, plain text, a described drawing, or a conversation with someone who can talk you through a document — contact {{SUPPORT_EMAIL}}.
Please tell us the page or screen involved, what you were trying to do, and what assistive technology you use if any. We aim to reply within five working days.
Reports of accessibility problems are welcome and are treated as faults, not complaints. If a fix is not quick, we will tell you what the workaround is and when we expect to resolve it.
7. If you are not happy with our response
Tell us first at {{SUPPORT_EMAIL}} and we will look at it again.
If you are still not satisfied, the Equality Advisory and Support Service can advise you about your rights under the Equality Act 2010 — equalityadvisoryservice.com.
8. What we are doing next
Our priorities, in order:
- A keyboard alternative for every reordering action.
- A skip link on each main screen.
- Better structure and announcements in the large data tables.
- An independent accessibility audit once the above are done.
We review this statement whenever we change the interface, and at least once a year.
Close