Skip to main content
Latchkey home

Help center

How can we help?

Six categories, covering the Widget, Flow, Services, the accessibility interface, the legal and privacy questions, and what changed in each release.

The help center is being written during the private beta. No articles are published yet. This page lists the six categories and what each one will cover, rather than links that would go nowhere and counts that nothing computes.
Contact support

There is no search box here on purpose. Search arrives with the articles: a field that searched an empty corpus would return nothing on every query, which tells you less than the categories below do.

What the help center will cover

The taxonomy is fixed; the articles are not written. Each category below says what will be in it, so you can tell now whether your question is one we have planned for.

  • Getting started with the Widget

    Installing the snippet, verifying it loaded, and everything that comes after: the CMS and platform install paths, customising the interface, managing your account, and the questions support answers most often.

    • Install paths for hosted platforms and hand-rolled sites
    • Verifying the install with a free scan
    • Customising the launcher, position and colours
    • Licences, sites and team members
    • Payment, plan changes and traffic caps
    • Troubleshooting a widget that will not appear

  • Flow

    The developer platform: crawling a whole site including the pages behind a login, triaging what comes back, and shipping the patches your developers review.

    • Adding a site and running a first crawl
    • Authenticated scans, and why login is attempted exactly once
    • Journeys, assets and scheduled audits
    • Reading a code patch and its fix label
    • The SDK, the MCP server and the GitHub app
    • Troubleshooting a crawl that stopped early

  • Services

    How the human work is ordered and delivered: what we need from you, what arrives, and how long each engagement takes.

    • How the free scanner works and what it covers
    • Expert audit, VPAT and ACR, user testing, file remediation
    • What an Evidence Pack contains

  • Accessibility information

    One article per visitor profile and per adjustment group in the widget interface: what each one changes on the page, and who it is for. The interface itself ships in 33 languages.

    • The visitor profiles, one article each
    • Content, colour, orientation and navigation adjustments
    • What the interface deliberately does not do to assistive technology

  • Legal and privacy

    The questions that come from a legal or procurement reader rather than a developer. Compliance is a legal determination, not a product feature.

    • What an Evidence Pack is, and what it is not
    • What a demand letter is, and what we can and cannot do about one
    • What the widget changes about legal exposure, stated plainly
    • Screenshots, encryption at rest, retention and one-click delete
    • Cookies and local storage, item by item

  • Release notes

    What changed, when, and what you may need to do about it, kept per surface so a widget change is not buried under portal changes.

    • Widget
    • Flow
    • Apps and plugins
    • Free scanner
    • Customer portal

While the articles are being written

  • Ask us directly

    While the articles are being written, a person answers. Tell us the site and what you are trying to do.

    Contact support

  • Check an install

    The free scanner reports whether a Latchkey widget was detected on a page, with no account.

    Run a free scan

  • What automated checks reach

    Automated checks cover roughly one third of WCAG success criteria. The limitations page names what is left.

    Read the limitations

Articles will be written as markdown in the product repository and rendered here, so a screenshot in an install guide is versioned with the interface it shows. If a question you ask support turns out to be a missing article, that is how the corpus gets written.