How Pinquin works.
Pin your channels and name an owner for each area. Pinquin tests, prioritises, routes and retests on its own, and only tells people what is theirs.
Ten minutes to a first, honest picture.
Every customer starts with a demo on their own website. When you go ahead, we open your workspace and set it up with you. Then it takes five steps.
Pin channels
Pinquin suggests the channels it finds from your domain. You confirm them.
Confirm critical journeys
Pinquin suggests the tasks your customers must be able to finish. You mark which ones matter and fix their names.
Give access
A synthetic test user for logged-in areas, and the build source for your apps.
Name owners
One person for each area. Syncing to their work tool is optional.
Review and go live
Look through the first results. Nobody hears from Pinquin before you go live.
Every channel. One loop.
Websites, apps, documents and AI assistants feed the same actions, owners and retests. Each channel says plainly what Pinquin checks and what a person still needs to judge.
Websites and logged-in web apps
A real browser loads each page as a visitor would. Rule checks run inside the page, and test agents walk your critical journeys. For logged-in areas, Pinquin signs in with a synthetic test user you provide.
Not covered: Anything the crawl and your journeys don’t reach.
iOS and Android apps
Every new build is checked for labels, roles, contrast and touch targets. Each night, your critical journeys run on real phones, at the largest text size and rotated.
Not covered: Driving VoiceOver and TalkBack live, which comes later.
Documents and PDFs
Tags, headings, language, reading order, tables and forms are checked against PDF/UA. Findings are grouped by the template behind each file, so one fix covers thousands of statements.
Not covered: Whether alt text describes the image well. Scanned PDFs without text are flagged.
AI assistants and chatbots
Pinquin tests the conversation itself: sending a message, hearing new replies announced, moving through generated headings and lists, and recovering from errors, by keyboard and screen reader.
Not covered: Whether the answer is correct. Pinquin tests accessibility, not content.
Seven test agents.
Each agent drives a real browser or device towards a goal, such as opening an account, under one constraint. It decides what to do, so it survives a redesign. When it gets stuck, you see where and why, with screenshots and a step-by-step log.
Each agent tests a functional need. None of them is, or pretends to be, a disabled person.
Keyboard
No mouse, no touch.Focus order, keyboard traps, dialogs and menus, visible focus.Screen reader
Only what assistive technology announces.Names, roles and states, reading order, announced errors and status messages.Low vision
400% zoom, larger text, high contrast.Reflow, resize, text spacing, contrast of controls, use of colour.Voice control
Only spoken commands, using visible labels.Labels that match accessible names, no dragging or complex gestures.Plain language
Only clear instructions and errors.Instructions, error messages, headings and link text, sign-in without puzzles.Reduced motion
Less motion, more time.Animation that can be paused, flashing, time limits that can be extended.Media
Can’t hear the audio, or can’t see the video.Captions, transcripts and audio description are present.
When a person decides
Agents find two kinds of things. Checkable findings, such as a control that can’t be reached, become actions straight away. Judgments, such as whether an instruction is clear, go to a review list first. Your accessibility lead, or an expert, confirms or rejects each one. AI never decides pass or fail.
A few actions, each with one owner.
Most barriers come from a few shared things. Pinquin groups findings by their root cause and turns them into actions you can actually finish.
Every action has
A named person, not a team inbox
Every area has one owner. Anything found where nobody is named yet goes to the person who set up the workspace, so nothing falls through a gap. Each area can also sync to the team’s own tool; delivery status syncs back, and verification stays in Pinquin.
| Area | Owner | Also sync to |
|---|---|---|
| Online bank · Payments | Payments team lead | Jira |
| iOS and Android apps | Mobile lead | Azure DevOps |
| Statements · documents | Document Services lead | Don’t sync |
| Online bank · Loans | No owner yet: goes to the workspace’s setup lead | Don’t sync |
Done is not fixed.
An action is verified only when the test that found the barrier passes again, in the environment where it matters. The same agent reruns the same steps.
- Needs attentionA barrier exists and needs an owner or a decision.
- In progressSomeone owns it, in Pinquin or a synced tool.
- Awaiting verificationThe owner says the fix is live. A retest is queued.
- VerifiedThe original test passed.
- Fix didn’t passThe barrier remains, or only partly changed.
- Came backA verified barrier returned. Pinquin tells the owner.
An action can also be accepted: kept open on purpose, with a reason and a review date.
Honest about what it couldn’t test.
Pinquin tests against the 55 success criteria of WCAG 2.2 level A and AA, and says, criterion by criterion, how each one was checked.
- 36 criteriadecided by PinquinRules and test agents decide these on their own, such as contrast, keyboard access and reflow.
- 13 criteriareviewed until trustedPart of the answer is a judgment, such as clear headings or a sensible focus order.
- 6 criteriajudged by a personMedia criteria. Pinquin checks captions and descriptions exist; a person judges whether they are right.
No automated tool can prove full conformance, and Pinquin doesn’t claim to. When a test login expires or a page sits behind a CAPTCHA, Pinquin says so on the channel and the journey. Something that couldn’t be tested is never shown as verified.
Quiet, until it matters.
Quiet until you go live
During setup Pinquin tests but sends nothing. A banner on every page says so, with a link to review and go live. For 15 minutes after going live, you can step back into quiet mode.
Only when it’s yours
Owners hear when a new action is theirs, when their fix passes or fails its retest, and when something comes back. A daily summary is available instead; a blocked critical journey is still sent straight away.
Where people already are
Email is always on. An admin can connect Microsoft Teams or Slack, and each owner picks where they prefer messages. Team inboxes can be copied in; the owner is still a person.
Works with
See it on your own website.
A 30-minute demo, on your pages. We reply within one working day.
Request a demo