Home › Situations

Accessibility on every screen, in every language

The a11y pack checks alt texts, names, labels, headings, WCAG AA contrast and landmarks on the exact screens your agent walked, in every language.

The problem

The accessibility audit covered the home page in English; the signed-in checkout in Czech was never checked.

Ask your agent

Add the a11y pack to the sign-up and checkout scenarios, walk them on staging in every language on desktop and mobile, share the run and list which accessibility criteria fail on which screens.

Pack criteria are added to each step without writing them by hand; each failure comes with the elements as evidence.

What comes out

Every screen of the flow with its criteria; failing ones carry the evidence.

LIVE · today 14:44 CEST · 7 of 11 passed · 7/11 steps · Open the live run ↗

• Failed

• OK

• OK

• OK

Waiting for a person· 2 Oct 2026· 36 screens· CS, EN

• OK passed or approved by a person
• Returned a person sent it back with a note
• Failed a check failed
• ? a person decides

Why it holds

• Seven checks you can count

  Images have alternative text, links and buttons have names, form fields have labels, heading levels are not skipped, text meets WCAG AA contrast, a main landmark exists, ids are unique.

• On the states crawlers miss

  The checks run where the agent actually went: signed in, after an action, in a filled form, in every locale and viewport.

• Apps too

  On Android and iOS screens Kaloko checks labels and touch targets from the UI tree.

• Enough for acceptance

  The pack is a WCAG 2.2 AA subset for accepting each change. For a full audit, use a dedicated crawler or an accessibility specialist alongside it.

Step-by-step guides