Legal
Accessibility Statement
This statement applies to the justbrowser.app website, including the marketing pages and the web dashboard (together, "the Site"). It explains what Velocity Digital Labs, LLC ("we", "us") is doing to make the Site usable by as many people as possible, where we know it falls short today, and how to tell us when something gets in your way.
1. Our commitment
We aim for the Site to conform to the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. We treat this as an ongoing obligation rather than a finished project: new pages and features are built against the same target, and we correct problems as we find them or as you report them.
This statement describes the current state of the Site as we understand it. It has not been verified by an independent accessibility audit, we hold no accessibility certification, and we do not claim audited conformance. Where we say something has been done, it means we have implemented and checked it ourselves.
2. What we checked, and what passes
We last checked the Site on November 11, 2026. We checked the home page, Pricing, Download, the sign-in, sign-up and password reset pages, the blog and a sample post that uses the post template's headings, lists, table, code, note and quotation, every comparison page, the API documentation, the browser fingerprint checker, the legal pages including this statement, the pages for verifying an email address, accepting a team invitation, unsubscribing from emails and returning from checkout, and the page shown for an address that does not exist. We checked every page of the web dashboard, signed in with a test account, together with its search, notifications, account menu and profile details, and its dialogs for deleting the account, a team or an API token and for cancelling an invitation. We also checked the error messages of the sign-in and sign-up forms, and the two pages that the desktop application opens inside a browser profile, described in section 3. On November 12, 2026 we checked again the pages we changed that day: the home page, the sign-in and sign-up pages, the pages for requesting a password reset and setting a new password, the pages for verifying an email address and accepting a team invitation, the browser fingerprint checker, this statement, and those two pages. On November 15, 2026 we checked again the fingerprint check page, which we changed that day.
On each page we ran the automated checker axe-core (version 4.14) against its WCAG 2.0, 2.1 and 2.2 Level A and AA rules, in the light and the dark theme, at a phone width (375 pixels) and a desktop width (1440 pixels). Where axe-core cannot measure the contrast of text, such as text over a gradient, we measured it from the pixels on the screen. We checked that each page fits a width of 320 pixels, checked the contrast of buttons and links while the pointer is over them, and went through each page with the keyboard alone (Tab, Shift+Tab, Enter, Space and Escape). We checked the home page with its animations on, paused and off.
Automated checks find only some kinds of barrier. We did not test with a screen reader, screen magnification or voice-control software, and the Site has not been reviewed by people with disabilities.
On every page above except the two described in section 3, the following holds.
- Automated checks. axe-core reported no failure of its WCAG Level A or AA rules, in either theme, at either width, or in any of the states we opened.
- Structure. Pages use native HTML landmarks, one main heading with the headings below it in order, lists for list content, and real buttons and links for controls, so that screen readers and other assistive technology can navigate by structure.
- Keyboard and focus. Every link, button and form field can be reached and used with the keyboard alone, in an order that follows the page, and shows a visible focus outline. Focus is never trapped, and the control that has focus is never hidden behind the site's top bar or its menu. Escape closes the menu on small screens and the dashboard's menus and dialogs, and focus that was inside them goes back to the control that opened them. Wide tables, code samples and the picture of the app on the home page, which scroll sideways inside their own box, can be scrolled with the keyboard.
- Colour contrast in both themes. Text meets the WCAG 2.2 Level AA contrast minimums (4.5:1 for normal text, 3:1 for large text) in the light and the dark theme, including buttons and links while the pointer is over them, text over gradients and at the edges of a table that scrolls, and the home page's sections while they move into place. Only decoration, such as the large lettering at the foot of each page, and the small print inside the picture of the app on the home page are fainter.
- Text alternatives. Images that convey information have text alternatives, and decorative icons are hidden from assistive technology.
- Reflow. At a width of 320 pixels, the width of a 1280-pixel window zoomed to 400%, no page scrolls sideways: the site's header links move into a menu, and only wide tables, code samples, the picture of the app and the dashboard's row of tabs scroll, inside their own box.
- Moving content. The home page's moving content, such as the strip that lists what each profile keeps separately, the background of the first screen, the faint grain over the page in the dark theme and the animations in the pictures of the app, stops when you press the Pause animations button near the top of the page, below the prices. Press it again, when it reads Play animations, to start it again. Everything on the page also stands still when your device is set to reduce motion, and the button is then not shown.
- Light and dark. Every one of these pages follows your operating system's light or dark preference and has a switch to choose either; the choice is remembered in your browser.
3. Known limitations
As of November 15, 2026, we know of the following limitations. We state them plainly so you know what to expect, and we intend to address them.
- The pages the desktop application opens inside a browser profile. The fingerprint check page shown when a profile is first opened follows your operating system's light or dark preference but has no switch. The new-tab page keeps its earlier design and is light only: it does not follow your operating system's light or dark preference or have a switch. Everything else that section 2 lists holds for them too.
- Third-party content. The checkout form and the form to change your card are Stripe's: the checkout is shown on Stripe's own page or in a frame on our Billing page and checkout page, and the card form in a frame on our Billing page. In the desktop app, the checkout, Change card and Complete payment are our own form around Stripe's card fields, which are in Stripe's frames. Some subscription management (your billing address and tax ID) is handled on pages hosted by our payment processor, Stripe, and signing in with Google happens on Google's pages. Cloudflare Turnstile, which some of our account pages show to check that a person rather than a script is using them, is drawn by Cloudflare in a frame of its own; our checks covered our pages, not the inside of that frame. We do not control the accessibility of these, although we take it into account when choosing providers.
4. The desktop application
JustBrowser itself is a native desktop application for Windows (x64) and macOS (Apple Silicon) built on Electron, together with the browser core pinned to each profile. It is a separate product from the Site and is assessed separately. WCAG 2.2 is written for web content, so this statement's conformance target does not extend to the desktop application, and nothing here should be read as a claim about it.
We do accept barrier reports about the desktop application through the same channel described in section 5, and we use them to prioritise work on the application.
5. Reporting a barrier
If you cannot access part of the Site, or you find content that does not work with the assistive technology you use, please tell us. Email legal@justbrowser.app and include, as far as you can:
- the address (URL) of the page or the name of the screen where the problem occurs;
- what you were trying to do and what happened instead;
- the assistive technology you use (for example, the screen reader, magnifier, switch device or voice-control software and its version);
- your browser and operating system, if you know them.
5.1 What happens next
We aim to respond within 10 business days of receiving your report. Where we can, we will describe a workaround in that response and tell you whether and when we expect to fix the underlying problem. If you need the information on a page in a different format in the meantime, ask in the same email and we will provide it where we reasonably can.
We use the details you send us only to investigate and resolve the barrier you report. See our Privacy Policy at /privacy for how we handle support correspondence.
5.2 Other ways to contact us
This mailbox is for accessibility barriers. If you are reporting a security vulnerability, email security@justbrowser.app instead; our security disclosure page at /security explains what to include. Requests about your personal data go to privacy@justbrowser.app. To delete your account, email privacy@justbrowser.app from the address on the account; we delete your data within 30 days except where law requires retention.
Postal correspondence can be sent to Velocity Digital Labs, LLC, 1111B S Governors Ave #52122, Dover, DE 19904, United States.
6. Changes to this statement
We will update this statement when the Site changes in a way that affects accessibility, when a known limitation is resolved, or when a new one is found. We will post the updated version with a new date and, for changes that narrow what you may do or reduce your rights, notify account holders by email before they take effect. Our Terms of Service at /terms continue to govern your use of the Site.
Last updated: November 15, 2026.