Fifteen directions of the audit go into your checklist on the first call. The client site opens inside the window, already signed in, so the account pages and the checkout are walked like any other. You file findings as you go, and the report is built from them. The directions a machine cannot judge stay open until you sign them.
$79/yr locked for good · first hundredOne email, when it ships. Nothing else.
Whether the alt text says anything. Whether the reading order matches the eye. Whether the error message helps. Each is its own line in the checklist, and it stays open until you write down what you saw. A direction closes on a signed verdict, never on a green tick.
See the panelsjig.open("/checkout")
jig.login("admin")
jig.fill(form → 96)
jig.read("network")
Connect Cursor, VS Code or Claude Code over MCP. Your agent writes the code; here it opens the page, signs in as a role and presses the buttons.
Connect your editorAn accessibility audit is not a button. It is a plan, a walk, a register of findings, a signed report, and another pass after the fixes. Jig holds all of it. The first call puts fifteen directions into your checklist. The site opens inside the window, already signed in, so the account pages and the checkout are walked like any other. You file findings as you go, and the report is built from them: each one carries the criterion it breaks and the node it sits on. Directions a machine cannot judge stay open until you sign them. Jig, a workbench for the whole audit.
For QA and for whoever ships the code · macOS, signed and notarised · Windows, not signed yet · everything it measures runs on your machine
Pick a panel, the same way you would inside Jig. The first two are the ones you will live in.
Machine-detectable WCAG 2.2 violations with the element and the wording to quote. Plus the Tab route, walked rather than assumed.
Nothing here is impossible without Jig. That is the point. It is possible, and it costs a week: walk the site by hand, keep the register in a spreadsheet, retype it into a template, then do the whole pass again after the fixes.
An IDE is built for the person who writes the code, and every attempt to bolt manual testing onto one ends the same way: a plugin that opens a preview and can tell you nothing about it. Jig starts from the other end: the application is the document, and everything around it is for reading that application rather than editing it. Keep your editor; connect it, and the agent in it gets hands here.
Five applications open at once and you tell them apart before reading a word: green is staging, red is the production copy nobody may touch. The tint travels with the project: open it on another machine and it looks the same.
It writes the endpoint, writes the form, and then describes to you what to click, because a coding agent has no browser with your logins in it. Connect your editor to Jig and it stops describing: it opens the page, signs in as one of the project’s roles, fills the form in one pass and reads what the server actually answered.
{ "mcpServers": { "jig": {
"command": "npx", "args": ["-y", "jig-mcp"] } } }There is no key in the snippet. Jig writes its address to a file only you can read, and the client picks it up there, so a restart on a different port needs nothing re-pasted.
Which project it lands in is decided by the folder your editor is open in; several editors connect at once and none of them moves your window. It is refused for exactly the same reasons the chat here is refused: connecting an editor grants nothing that was not already granted.
The first pass over somebody else’s form costs work: a hand-rolled list of divs has to be pressed, watched, understood: where does the value actually land. Jig does that once and writes it down: a procedure per control, plus a whole layer for the form (the order fields take values in, the knots, the places that fought back). From the second pass on it is not analysis any more, it is a read from disk.
The same three rings Jig shows in its settings, after a week on an internal admin panel.
Everything worked out here stays with you and runs with no network. The key is the place plus the markup, so the same application is recognised from any of your projects, and a stranger’s site inherits nothing.
Several machines under one key: what a colleague worked out on your internal admin arrives by itself. Encrypted before it leaves, with a key derived from your licence.
The first Jig in the world to meet an unknown widget pays for taking it apart. Everyone after gets the procedure instantly and free, with no key at all. What travels is a hash and the procedure: no address, no page, no values.
A developer adds a field or drops a wizard step: different shape, same address. Jig recognises the form by its place, carries what still applies onto the new structure, and says what changed.
Ant Design, MUI, Vuetify, PrimeReact, Kendo, Mantine, web components: built into the engine, working from the first minute. Memory is for where your own begins: the internal panel built out of divs.
96% of fields filled with no memory and no model, measured across forty pages of forms
Findings by severity, each carrying the criterion it breaks, the page it was seen on and the node it sits on. Beside them the run passport: who evaluated, on which browser and screen reader, at which viewport. Then coverage by direction and by route, and a plain count of what nobody looked at. Four files per pass, and the PDF carries a structure tree, so the document can be read the way it asks the client’s site to be readable.
POST /api/orders → 200 REF-48121 POST /api/orders → 200 REF-48122 ← the same order, twice
The browser, the inspector, the form map, the fill, the mocks, the recorder, the audit, the network log: none of it goes anywhere. When you hand a task to Claude, what travels with the question is the shape of the work: the field names of the page, the names of your roles, your checklist and the titles of your findings. What you type stays here, and so do passwords, account logins and the addresses of your stands. A screenshot only ever leaves if you switch that on yourself.
Jig never acts in a tab you are signed into yourself. It works in its own, and the login it uses is the one you gave it. And it only ever opens the sites you allowed for this project; anything else is refused, whatever the task says.
Not one page. The audit walks every route, signed in and signed out, and the report is built three ways at once: by direction, by route, and page by page. One section says out loud how many directions were not tested at all. A percentage hides that. A list does not.
Self-contained: the screenshots are inside it, so it opens on somebody else’s machine with nothing attached. It names what passed, what failed, what was blocked, and how many items nobody opened at all.
Numbers say what happened; what it means for the release is known only to the person who looked. Write that into the report itself. The text lives in a markdown file beside it, so it survives every rebuild.
Printed by Jig rather than by the browser, so headings and tables arrive as headings and tables. A screen reader walks the document instead of meeting a picture of one.
The first run of anything is free, always. What you pay for is the second one, because the repeat is where a professional’s time actually goes.
Three seconds in Jig against seventy-three with a Playwright script, and the script had to be written first. Here nobody wrote one.
$0 forever
No account needed
$99 / year, per person
One payment. Nothing renews itself: our till does not keep your card.
$149 / year, per seat
Invoice from a registered business, with the documents your finance department asks for. Seats can be reassigned.
$79 / year, fixed for good
The first hundred people to buy keep this price for every year they stay, including after the public price goes up.
Qiksy BridgeChrome extension · already on the Web Store · free, no licence, no accountQiksy Bridge is our Chrome extension for testing inside the browser you already use, and it is free for everyone, agent bridge included. Two tools, both halves of the trade: the browser for the work you plan, the extension for the page you happen to be on.
It rides along in the browser you already have open: your profile, your logins, the tab in front of you. It fills the form, catches the console error, the failed request with the server’s own body and the accessibility violation, and hands the lot back as one file you attach to the ticket. Nothing to script, no second browser to sign into.
A regression pass with a name, several signed-in roles at once, the same form filled four ways, a recorded flow replayed on a button, and the difference between last week’s run and this one. This is the half a lead, a QA owner or whoever signs the release off actually needs: something to show, not a feeling.
A developer checking the feature they wrote an hour ago on staging, under their own SSO. Support reproducing what a customer sent. A project manager opening the link in a ticket to see for themselves. Nothing to set up and nothing to plan: it is already in the browser they use all day.
Neither half needs a model to measure. Forms, findings, the network with response bodies, the WCAG audit, the Tab-order walk: local, free, no account and no Claude. A model only enters when you hand the work to an agent, and then it is your own Claude subscription, not tokens resold by us.
So this is not two-for-one. It is one job that happens in two places (the pass you plan, and the page that lands in front of you), and having paid for the larger half, you should not have to buy the smaller one twice. It only runs this way round. A Qiksy Bridge key does not unlock Jig. Jig is the larger tool, and paying for the smaller one cannot buy it.
Full Pro for thirty days. Two weeks is not long enough to meet a regression, and the regression is the thing Pro is for.
The thinking is done by your own Claude subscription, and only by it. Jig finds it on this machine and works through it: unlimited, with nothing extra to pay and nothing counted by us. We have no model service of our own and sell no allowance: the one thing we could charge for here is inference, and inference on your subscription costs us zero. Without Claude on the machine, Jig still measures everything it measures; it simply does not think, and it says so rather than pretending.
Leave an address and we will write once, when Windows lands and sales open, with the founding price attached.
Windows: this installer is not signed yet. The certificate is still in identity validation. Windows will show a blue “Windows protected your PC” screen: choose <b>More info</b>, then <b>Run anyway</b>. It installs into your own user profile and never asks for administrator rights. Tested on a real Windows Server 2022: the build behaves exactly as the Mac one.
Or from the Microsoft Store: signed by Microsoft, no warning screen, and it updates itself.
You are downloading Jig from us directly, not from a store, so both systems say something the first time. Here is exactly what, and which button to press.
The installer puts Jig in your own user folder and never asks for an administrator password.
Windows shows a blue window headed “Windows protected your PC”, and the only button on it says “Don’t run”. Do not stop there. Press the link “More info” first, and a second button appears: “Run anyway”. That is the one you need.
Where that window names the publisher it will say “Unknown publisher”, and that is expected right now: our signing certificate has been bought and is going through the certificate authority’s identity checks. Until it is issued there is nothing to sign the file with. So the name is not what tells you this file is ours. The checksum below does.
The image opens with Jig on the left and a shortcut to Applications on the right: drag the first onto the second, and that is the install.
There are two files, one per processor, and the wrong one will not start. If you do not know which Mac you have: Apple menu, “About This Mac”. The line says either “Apple M…” or “Intel”.
Each number below belongs to that exact file. Run the command and compare what it prints with what is written here: if they match, nothing was changed on the way to you.
0db8e3f130e2f8f08c069bfcda7a91d5a433dd2e78545c933c692692e8c26e013cd38aeac0f5dda596224a2ab69efa7ee7257047144948720744d377a9a7e1bc5c64cdbf785081b00eac736c4282b4a1366a3d714ac54a99792cf021dffe4ac1We are building Qiksy in the open: new tools, real progress, the occasional stumble. One short note when something ships.
One note when it ships. Nothing else.