Accessibility
Accessibility statement
Last updated: 29 September 2026
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.
The most important limitation is significant, so we are putting it first rather than burying it in a list.
What does not work yet
| Problem | Who it affects | Standard not met | Expected fix |
|---|---|---|---|
| Document pages are drawn as images. A screen reader cannot read the text of a document you are viewing, and you cannot select that text or search within the page. | People using a screen reader, and anyone who relies on selecting or searching text. | WCAG 2.2, 1.1.1 Non-text Content (Level A) | 31 October 2026 |
| Because document pages are images, text in them 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 October 2026 |
| The skip link at the top of each page does not yet move you past the menu. | Keyboard and switch users. | WCAG 2.2, 2.4.1 Bypass Blocks (Level A) | 7 October 2026 |
| At 400 percent zoom on a narrow screen, the menu button is cut off, so the site menu cannot be opened. | People who zoom or use a magnifier. | WCAG 2.2, 1.4.10 Reflow (Level AA) | 7 October 2026 |
| Footer links are too small to tap easily, and the moving logo strip on the home page cannot be paused. | People with limited dexterity, and people distracted by movement. | WCAG 2.2, 2.5.8 Target Size and 2.2.2 Pause, Stop, Hide | 7 October 2026 |
| In the application, some grey text has too little contrast, and some labels are cut off when text spacing is increased. | People with low vision. | WCAG 2.2, 1.4.3 Contrast (Minimum) and 1.4.12 Text Spacing (Level AA) | 31 October 2026 |
| In the application, keyboard focus can move behind the settings window, some settings fields are not linked to their labels, and every screen has the same page title. | Keyboard and screen reader users. | WCAG 2.2, 2.4.3 Focus Order, 1.3.1 Info and Relationships, 2.4.2 Page Titled | 31 October 2026 |
| On a protected link, the email field has no label, and in dark mode one button has low contrast. | Screen reader users, and people with low vision. | WCAG 2.2, 1.3.5, 3.3.2 and 1.4.3 | 16 October 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 16 October 2026 |
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 alerts@99developer.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 alerts@99developer.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. It does not yet move you past the menu, as listed above.
- 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. A person sharing a document can turn on watermarking and screenshot deterrence. 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.
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 29 September 2026. The next scheduled review is 31 January 2027.