Request a demo

Accessibility that never sleeps.

Not another dashboard. Pinquin tests, routes and retests on its own, and only calls a problem fixed when it really is.

Request a demoSee how it works
Nordbank
  • Overview
  • Journeys
  • Actions
  • Channels
  • Teams
  • Settings
Example

Checked continuously · last run 4 minutes ago

Two journeys need you. Everything else is running and verified.

Do this next

Account opening: keyboard users can’t get past identity confirmation

New customers who don’t use a mouse stop at step 3 of 5.

Owner: Digital BankingOnline bankIn progress

Critical journeys

  • Open an accountAt risk
  • Apply for a loanNeeds attention
  • Pay a billAwaiting verification
  • Log inVerified
  • Contact supportVerified
Example. Overview for a fictional bank.

From findings to actions

212 findings. 5 actions.

Most barriers come from a few shared things: a button, a dialog, a document template. Pinquin traces findings to their root cause and gives each action one named owner.

  1. 96 findingsFix the accessible name in the shared primary button
  2. 41 findingsFix focus handling in the shared dialog component
  3. 38 findingsFix the statement template, not each PDF
  4. 22 findingsAnnounce errors in the loan application form
  5. 15 findingsRaise the contrast of the footer links
Example. 212 findings across five channels, grouped by root cause into 5 actions.

Three things to do.

Pinquin does the rest.

  1. Pin channels

    Website, web app, iOS and Android, documents, AI assistant.

  2. Connect teams

    One owner per area. Sync to Jira, Azure DevOps, GitHub Issues or Linear if you like.

  3. See the state

    A calm overview when you want it. A message only when something is yours.

Meanwhile, in the background.

Pinquin goes round this loop on its own, for every channel you pin. People step in only when something is theirs.

Stage 01

Detect

Rules, interaction tests and test agents look for barriers.

  1. Detect Rules, interaction tests and test agents look for barriers.
  2. Understand Repeated findings are grouped by their root cause.
  3. Prioritise Barriers on critical journeys move to the top.
  4. Route Each action goes to the named owner of its area.
  5. Verify The same test runs again once the fix is live.
  6. Monitor Pinquin watches for anything that comes back.

Seven test agents. Working around the clock.

Seven test agents walk your critical journeys, each under one constraint. When one gets stuck, you see exactly where.

Each agent tests a functional need. None of them is, or pretends to be, a disabled person.

  • KeyboardNo mouse, no touch.
  • Screen readerOnly what assistive technology announces.
  • Low vision400% zoom, larger text, high contrast.
  • Voice controlOnly spoken commands, using visible labels.
  • Plain languageOnly clear instructions and errors.
  • Reduced motionLess motion, more time.
  • MediaCan’t hear the audio, or can’t see the video.

One journey, through an agent’s eyes.

Choose a test agent and see how far it gets through opening an account.

Choose a test agent
Open an account · Critical journeyExample

Keyboard agent. Gets through 2 of 5 steps, then gets stuck at Confirm identity.

  1. Start applicationGets through
  2. Personal detailsGets through
  3. Confirm identityStuckFocus is trapped in the ID upload dialog.
  4. Choose an accountNot reached
  5. Sign and finishNot reached

Screen reader agent. Finishes the journey, but is slowed at Personal details.

  1. Start applicationGets through
  2. Personal detailsSlowedErrors appear on screen but aren’t announced.
  3. Confirm identityGets through
  4. Choose an accountGets through
  5. Sign and finishGets through

Low vision agent. Finishes the journey, but is slowed at Choose an account.

  1. Start applicationGets through
  2. Personal detailsGets through
  3. Confirm identityGets through
  4. Choose an accountSlowedAccount cards overlap at 400% zoom.
  5. Sign and finishGets through

Voice control agent. Gets through 3 of 5 steps, then gets stuck at Choose an account.

  1. Start applicationGets through
  2. Personal detailsGets through
  3. Confirm identityGets through
  4. Choose an accountStuck“Continue” is named “Next step” for assistive technology.
  5. Sign and finishNot reached
Example. A fictional bank’s account opening, tested by four of the seven agents.

Done is not fixed.

Marked as done isn’t good enough. An action is verified only when the test that found the barrier passes again, and if it comes back, Pinquin notices.

  1. Needs attention
  2. In progress
  3. Awaiting verification
  4. Verified

Quiet, until it matters.

  • Quiet until you go live.

    During setup Pinquin tests but sends nothing. You review the first results before anyone hears a word.

  • Honest about coverage.

    Every channel shows what was tested, what wasn’t, and why. Nothing untested is ever shown as verified.

  • Status, not a score.

    Healthy, Needs attention or At risk, backed by facts.

  • Where your teams work.

    Jira, Azure DevOps, GitHub Issues, Linear. Delivery status syncs back.

  • Messages that matter.

    Email, Microsoft Teams or Slack, only when something is yours.

  • European data stays in the EU.

    For customers in Europe, findings, evidence, screenshots and retest results are stored in the EU.

One test. Every rule that applies.

WCAG 2.2 AA, mapped to the rules where your users are.

  • European Accessibility Act
  • Web Accessibility Directive
  • EN 301 549
  • ADA
  • Section 508
  • AODA

Pinquin explains obligations in plain words. It is not legal advice.

Compliance, in plain words

Your website. Our demo. Thirty minutes.

See what Pinquin finds on your own pages. We reply within one working day.

Request a demo

We’re welcoming a small group of launch customers in the Nordics.