Real barriers, not just rule hits
Tallyn reasons about the page in context: a clickable div that traps a keyboard, an alt that should be empty, a control with no accessible name. The findings a checker cannot produce.
Product
See an audit
This is a typical e-commerce checkout. Click any issue. Nothing here is a mockup: it is the product screen, with the product’s own output and the same copy-ready fix.
Checkout page
shop.example.com/checkout
54
score · At risk
2
critical
2
serious
5
issues total
Issues, ranked by impact
Who it affects
Screen reader users, who reach this field and hear only "edit text" with no idea it wants their email, and voice-control users, who have no name to speak.
Why it matters
The input relies on a placeholder for its name, and a placeholder is not a label: it disappears on focus and is not reliably announced. At checkout, a field a person cannot identify is a field they cannot complete, so the sale is lost at the last step.
In your markup
<input type="email" placeholder="Email address"><label for="email">Email address</label>
<input id="email" type="email" name="email"
autocomplete="email">A real <label> tied to the input by id gives it a name for every assistive technology, and autocomplete speeds up everyone else.
The read
This is a standard e-commerce checkout, and two of its issues block people outright: the email field has no label and the pay control cannot be reached by keyboard. Fix those two first, then the low-contrast total and the missing product alt text. The structure underneath is sound.
What you get
Tallyn reasons about the page in context: a clickable div that traps a keyboard, an alt that should be empty, a control with no accessible name. The findings a checker cannot produce.
Every issue is rated critical, serious or minor by how much it blocks real people, and ordered so the thing to fix first is at the top.
Each issue names the people and the consequence, so it is a real barrier for a real person, never a bare rule id.
The corrected markup for your own content, ready to copy, with a one-line note on why it works.
Run the page again and see which issues cleared and how the score moved. Progress you can show the team.
Barriers a deterministic check can confirm are marked as verified, so you know what was measured versus reasoned about.
Where we draw the line
Tallyn finds the real barriers, explains who they affect, and drafts the fix. That gets you most of the way and makes the rest cheaper. It is not a legal certification of compliance, and no automated tool can be one, because some questions need a person testing with a screen reader and a keyboard.
Use Tallyn to fix the clear problems fast, then bring a manual audit in for sign-off. Read our full stance.