Skip to main content
Here are answers to the most common questions about Labrador. If you don’t find what you’re looking for, contact the support team, most questions are answered the same business day.

​
Getting started

Yes. The Free plan costs $0 per month and never requires a credit card. It includes one project slot, the full WCAG 2.1 and 2.2 testing toolkit across Levels A, AA, and AAA, and HTML, VPAT, and CSV exports. It also includes live chat support. The demo project included in every account does not count against your one project slot.
No. Labrador runs entirely in your browser at testwithlabrador.com, there is no software to install or configure. The one optional install is the Labrador Chrome extension, which you only need for two features: running axe automated scans and generating AI remediation recommendations from a live page. The extension is available for Google Chrome only.
Labrador supports WCAG 2.1 and 2.2 at Levels A, AA, and AAA on all plans, including the Free plan. You choose your target standard and conformance level when you create a project.
Every new account comes with (Demo) University of Montauk, a sample audit that is most of the way through testing. Use it to explore documented issues, severities, and remediation guidance, try the exports, and finish the last pages yourself to get a feel for the workflow. It never counts towards your plan’s project limit, and you can delete it whenever you like.
The demo project is seeded when an account is created, so accounts made before the demo existed never received one. Long-standing Labrador users are the most likely to be missing it. Nothing is wrong with your account.On the Free plan, click Sample Project on the Projects dashboard, next to + Create Project. The button appears whenever your account has no demo project. On a paid plan the button is hidden, so contact support and we will add it for you.
Treat it as a finished audit you can take apart. Open a completed page to see how issues are documented, with severities, remediation status, and attached evidence. Run an Export to see exactly what a client receives. Then finish one of the last two pages yourself, which is the quickest way to feel the real workflow before you point Labrador at your own site. The empty pages are useful for trying the axe scan and the batch not-applicable tool without touching real audit data.Deleting it is safe and frees nothing, because it never occupied a project slot to begin with.

​
Projects and auditing

Yes. Every criterion row has a checkbox on its left. Click one, then hold Shift and click another to select everything in between. On a keyboard, press Space or Enter to set your starting point, then Shift + Space or Shift + Enter on a later criterion to select the range.A toolbar appears with the number selected and buttons to mark them Pass, Fail, N/A, or Untested.A range only selects what is currently visible, so filtering first is the trick: filter to Untested, select the whole filtered list, and mark it in one action. Only do that for criteria you have actually evaluated. See batch marking.
No. The testing methodology, WCAG 2.2 AA or VPAT® 2.5 – WCAG 2.2, is set at project creation and cannot be changed afterwards. If you need a different methodology, create a new project. This also means that if you want a .docx VPAT output, you must select the VPAT methodology when you create the project. If you are unsure which to pick, choose WCAG 2.2 AA Testing: it fits almost every engagement, including most cases where a VPAT is the eventual deliverable.
When you reach your plan’s project limit, Labrador will not let you create additional projects until you free up a slot or upgrade your plan. To free a slot, delete an existing project from your Projects dashboard. Deleting a project frees the slot immediately, no audit data on other projects, team memberships, or billing is affected. Note that capacity limits apply to projects only: there is no limit on the number of pages, components, and user journeys you can add within a single project.
Pages are full web pages, a homepage, a checkout screen, an article template. Components are reusable UI elements, a navigation header, a cookie banner, a modal, that appear across many pages; you audit them once and the findings apply wherever they are used. User journeys are ordered multi-step task flows, such as signup or checkout, that surface issues which only appear in transitions between steps. Most audits combine all three, and for most sites 10 to 20 items in total is a practical, defensible scope. See Managing pages and User journeys.
Yes. Criterion statuses and issues auto-save as you work, there is no save button to remember. If you close the browser mid-way through filling in an issue, your work is preserved.
Create a retest version from the Version actions menu inside your project. A retest bumps the minor version number (for example, v1.0 becomes v1.1) and carries all of your pages, criterion statuses, notes, and issues forward into the new version. Carried-forward issues are marked as such, so you know which findings you are retesting. When you verify a fix, set the issue’s remediation status to Closed; when every carried-forward issue on a criterion is closed, the criterion’s status updates automatically. For a scheduled re-audit or a major redesign, create a new major version (v2.0) instead, with your existing page list or a blank slate. Older versions are never modified: they become read-only, and you can still review and export from them at any time. See Audit versions.

​
Automated scanning and AI

Yes. With the Chrome extension installed, you can run an axe-core scan straight from the Criteria Overview of any page, component, or user journey with a URL set. Findings arrive mapped to their WCAG criteria, you review every result before anything is written to your project, and each accepted finding becomes an issue under the correct criterion with the axe rule and affected element pre-filled. Automated scanning catches roughly 30 to 50 percent of accessibility issues on a typical page; the rest require a human tester. Labrador’s approach is hybrid: run the scan first to get the machine-detectable issues out of the way, then spend your effort on the issues only a human can find.
Once you have written an issue description on a failing criterion, click Generate Recommendation. The Chrome extension guides you to the live page, you click the problem element, and Labrador drafts developer-ready fix guidance from your description, the captured HTML, and the WCAG criterion under review. The suggestion appears in the Remediation Help field, where you can edit it before it becomes part of any exported report. The feature is powered by Claude Opus and is currently in beta. Always review AI output before sharing it, you are responsible for the accuracy of your reports.
Only when you explicitly click Generate Recommendation on a specific issue, and only the minimum needed: the issue description and the markup of the element being tested. No other audit data is included, and nothing is sent at any other time. See Trust & Security for the full subprocessor list.
Check four things: you are using Google Chrome (the extension does not run in other browsers), the Labrador extension is installed and active, the page, component, or user journey you are testing has a valid URL set in your project, and, for AI recommendations, you have written an issue description first. The URL is the most common culprit, without it the extension cannot navigate to the right page. The page must also be one you can load in your own browser session, including completing any sign-in it requires.

​
Exports

Labrador supports four export formats:
  • HTML, an interactive, client-ready report with executive summary, detailed findings, screenshots, and remediation guidance. Includes Show Failures Only and Expand/Collapse All controls.
  • VPAT / DOCX, a Word document formatted as a VPAT® 2.5 conformance report, available for projects created with the VPAT methodology.
  • CSV, a flat export of all logged issues for flexible use in spreadsheets or other tools.
  • Jira-ready CSV, a CSV formatted for direct import into Jira, available on all plans including Free.
HTML, VPAT (where applicable), and CSV exports are available on all plans. The HTML report is fully self-contained: your client opens the file in any modern browser with no Labrador account, no login, and all screenshots and videos embedded. Custom report branding (your logo and identity) is available on the Enterprise plan.
There is no dedicated PDF export format. Instead, the HTML report includes a built-in Print / Save PDF button and a print-optimised layout (screenshots that are click-to-enlarge on screen render at full size in print), so you can produce a PDF directly from the report in your browser. The VPAT DOCX can likewise be saved as a PDF from Microsoft Word or Google Docs.
Yes, if you created the project with the VPAT® 2.5 – WCAG 2.2 methodology selected. The VPAT export format is available on all plans; the methodology choice at project creation is what determines whether it applies.

​
Jira integration

The live Jira integration, which pushes issues to Jira automatically and syncs status changes in both directions, is available on the Core, Plus, and Enterprise plans. It connects to Jira Cloud through Atlassian’s sign-in flow; if your team runs self-hosted Jira Server or Data Center, use the Jira-ready CSV export instead. The Free plan does not include the live integration, but it does include the Jira-ready CSV export, which you can import into Jira manually.
Once you connect a project to Jira Cloud and save your field mappings, new issues you log in Labrador are pushed to your Jira board automatically. After that, status and priority changes flow in both directions: close or reprioritise an issue in Labrador and the linked Jira ticket updates, and vice versa. The integration card in Labrador shows Reverse sync active when Jira-to-Labrador updates are enabled.

​
Team collaboration

Yes, for the read-and-respond roles. Any project owner, on any plan, can invite collaborators as View Only or Developer, and the invited person does not need a paid account either. What requires payment is edit access: assigning someone the Edit or Admin role requires that the invited person’s own account is on a paid plan. Separately, the broader team features, criterion-level comments, notifications, and team management, are part of the Plus plan and above. See Team members for the full breakdown.
Yes. Invite them as Developer: they follow the invitation link, create a free account on the spot, and land straight in the project. The Developer role lets them view the audit, leave comments, and update the remediation status of issues (for example, marking an issue as In Progress or Fixed for Retesting). They cannot modify criterion results, log new issues, or change project settings, so your audit stays intact.
Because the paid-plan requirement applies to the invited person’s own account, not yours. Edit and Admin roles require the collaborator to be on a paid plan at the moment you assign the role, and a newly created account on trial counts as free for this rule. Once they move onto a paid plan, you can promote them from the Teammates panel.

​
Billing and account

Yes, from your Billing Settings. Upgrades take effect immediately, you get the additional capacity and features the moment you confirm. Downgrades take effect at the end of your current billing cycle, so you keep everything you have paid for until the period runs out. Payments are processed by Stripe, a PCI DSS Level 1 provider; your card number is submitted directly to Stripe and never reaches Labrador’s servers.
Yes. Open the account menu in the top-right corner and choose Dark mode, then choose it again to switch back to light.It applies to the app itself, so projects, audits, account, billing, and notifications all follow your choice, while public pages such as the homepage and pricing stay light. The setting is stored in the browser you set it in rather than on your account, so it will not follow you to another computer. See Account settings for more.
Email security@testwithlabrador.com from the email address registered to your account. A member of the Labrador team will process your request and confirm when it is complete. All account data, projects, audit records, issues, and attachments are deleted within 30 days. This action is permanent and cannot be undone.

​
Security

All audit data, projects, pages, criteria, issues, screenshots, and file attachments, is stored in the United States on Microsoft Azure infrastructure in the East US 2 region (Virginia). Connections use TLS with HSTS preloading, and stored data is encrypted at rest with AES-256. See the Trust & Security page for full details on storage, encryption, and subprocessors.
Yes. Labrador runs two independent backup processes: a nightly database backup with point-in-time recovery covering the previous 35 days, and a separate daily backup to an independent system retained for 30 days. Access to backups is limited to Labrador’s engineering team. Deletions, on the other hand, are permanent: Labrador uses hard deletes, not hidden flags, and deleted data ages out of all backup systems within 35 days.
Yes. You can enable 2FA with any authenticator app (Google Authenticator, Authy, 1Password) from your account settings, and Labrador issues single-use recovery codes at setup, save them immediately, they are shown only once. If you sign in with Google, your Google account’s own two-step verification applies instead. See Two-factor authentication.
SSO and tailored security support are part of the Enterprise plan offering, but SAML-based SSO is not yet generally available. Enterprise customers who require SSO should contact Labrador to discuss timeline and requirements. Labrador’s Trust & Security page keeps an honest list of what is and is not built yet.

​
Support

Three ways: live chat via the yellow chat button on any Labrador page (weekdays, 9am to 5pm GMT and EDT, typically answered within minutes), email to help@testwithlabrador.com (answered within 24 hours on business days, put “Urgent” in the subject for time-sensitive issues), or the support form at testwithlabrador.com/support. Accessibility issues on Labrador’s own site go to accessibility@testwithlabrador.com, and security reports to security@testwithlabrador.com.