Accessibility
Accessibility statement
This statement applies to 99datarooms.com, the 99 Data Rooms application, and the pages people reach when someone shares a document or sends a signature request. It is published by 99 Developers Ltd.
We want as many people as possible to be able to use this service. That means you should be able to navigate it with a keyboard alone, use it with a screen reader, zoom to 200 percent without losing content, and read it with reduced motion or a high-contrast setting turned on.
How accessible this service is
We are aiming for the WCAG 2.2 AA standard. As at the date at the top of this page, this service is partially conformant: most of it meets that standard, but some parts do not. We would rather tell you exactly which parts than claim a level of conformance we have not reached.
Since our first check, documents shared with you carry their text for screen readers, the skip link takes you past the menu, every application screen has its own title, the fields in settings and on protected links are labelled, and the application's quieter text and the button on a protected link meet the contrast standard. What is left is listed here.
What does not work yet
| Problem | Who it affects | Standard not met | Expected fix |
|---|---|---|---|
| Document pages are drawn as pictures with their text laid over them. A screen reader can read that text, but it does not reflow or resize with your browser's text settings. You can zoom the page, but the text will not rewrap. | People who enlarge text, and people using a narrow or magnified viewport. | WCAG 2.2, 1.4.4 Resize Text and 1.4.10 Reflow (Level AA) | 31 March 2027 |
| In the application, a few names and details can still be cut to one line when text spacing is increased, for example some document names on the home screen and the name in the account menu. | People who set their own text spacing, including many dyslexic readers. | WCAG 2.2, 1.4.12 Text Spacing (Level AA) | 31 December 2026 |
| Not yet evaluated: testing with screen readers, most application windows, account settings other than the profile, the full signing journey, protected links using a passcode or code, and the password reset form. Problems there may not be listed yet. | Potentially anyone. | Not yet determined | Evaluated by 31 January 2027 |
What to do if you cannot access something
If you cannot read a document that has been shared with you, contact the person or company who sent you the link and ask them for the file directly, or for the content in another format. They control the document and can send it to you.
If that is not possible, or if the problem is with our own site or app rather than a document, email support@99datarooms.com. Tell us what you were trying to do and what got in the way. We aim to reply within five working days. If you need information from our own pages in another format, such as large print or plain text, ask and we will provide it.
Reporting a problem
We are always looking to improve. If you find a problem that is not listed above, or you think we are not meeting this statement, email support@99datarooms.com. Please say which page or screen it was, what you were using (for example a screen reader and which browser), and what happened. Reports like these are genuinely useful and they change what we build next.
If you are not happy with our response
We are a private company, so the accessibility regulations that cover public sector websites do not apply to us. Our duty to you comes from the Equality Act 2010, which requires us to make reasonable adjustments so that disabled people are not put at a disadvantage.
If you are not satisfied with how we have responded, the Equality Advisory and Support Service gives free, independent advice on the Equality Act in England, Scotland and Wales. In Northern Ireland, contact the Equality Commission for Northern Ireland.
Technical information
99 Developers Ltd is committed to making this service accessible, in accordance with the Equality Act 2010. This service is partially conformant with WCAG 2.2 AA. "Partially conformant" means some parts do not fully conform to the standard, and those parts are listed above.
Things we have built deliberately, which may be useful to know:
- Every page starts with a skip link as the first thing a keyboard user reaches, and it takes you past the menu to the page's main content.
- Animation and page transitions are switched off if your system asks for reduced motion.
- The application offers a light and a dark theme, and remembers which you chose.
- The service itself does not rely on cookies, and no analytics or tracking script runs on document pages at all. On our public marketing pages we ask separately before running session-replay analytics, and nothing is recorded unless you agree.
One deliberate design decision is worth explaining, because it can look like an accessibility barrier. Documents shared through 99 Data Rooms are watermarked and protected by default: printing, text selection and copying are off in our viewer, and the document is hidden when its window loses focus. Those settings discourage casual copying, but they must never be the reason a disabled person cannot read a document, so the accessible text of a document is not something we withhold on that basis.
How we tested
On 29 September 2026 we checked this service against WCAG 2.2 level AA. This was a self-evaluation by our own team, assisted by automated tools: automated checks at desktop and phone sizes in light and dark themes, then testing by hand for keyboard use, zoom to 400 percent, text spacing, target size and reduced motion. It covered the public website, sign-in and the main application screens. The document viewer and signing pages were checked with a sample document rather than a real link, and not past the point where a signature is confirmed, which is why the full signing journey is listed above as not yet evaluated.
What works: turning on reduced motion stops animation, we found no keyboard traps, and the cookie banner, menus and sign-in pages work with a keyboard. What does not work yet is listed above, with the date we expect each fix. We have not commissioned an independent external audit.
On 10 November 2026 we re-checked every problem this statement listed against the current service: the public pages in a browser, for the skip link, a 320 pixel wide window, the size of links and the moving logo list, and the application, the document viewer and the signing pages in their code, where an automated check now holds each fix in place. Six problems are fixed and have come off the list; part of a seventh is fixed, and the rest of it is listed above.
Reviewing this statement
We review this statement at least every six months, and whenever we change something that affects it. This page was last reviewed on 10 November 2026. The next scheduled review is 31 January 2027.