You are not the person it stops.

Each one is a separate thing to buy, because each is worth a different amount on a different site. A photographer with four hundred images and no duplicate titles should be able to pay for the first and not the second.

2 of them run today. The rest are switched off while they are rebuilt and checked on a real site, and nothing is charged for one that is off — the tools page says which is which.

• Alt text that does not match its pictureA rule can see that alt text exists. It cannot see the photograph, so it cannot tell you the sentence is about a different one.
• Alt text written for images that have noneThe missing alt is a rule’s answer and costs nothing. Looking at the picture and writing the sentence is this.
• Link text that does not stand on its ownStock phrases are caught by rules. Text that is unique and still says nothing is not, and that is the common case.
• Headings that do not describe their sectionHeading levels are a rule’s business. Whether a heading means anything is not.
• Public notices that are hard to readNo rule measures whether a sentence can be followed on the first read, on a phone, by somebody in a hurry.
• Tables: data, or page layout?The fix is the opposite in each case — add header cells, or mark it presentational. The mechanical check guesses.
• Icon buttons whose name does not matchA rule checks that a name exists. Whether aria-label="Menu" on a share button is right is a judgement, and a wrong name is followed.
• Page titles that do not tell pages apartNine pages titled the same pass every per-page check. Only visible once the whole site has been read.
• One wording, several destinations“Read more” pointing at nine articles. Invisible to any tool that reads one page at a time.
• Words that exist only as pixelsPosters, menus, flyers. The text cannot be selected, searched, translated or enlarged. Reading the picture is the only way to find it.
• Alt text on images that are linksA logo linking home should say “Home”, not “Company logo”. The alt is descriptive and still wrong, because the image’s job is navigation.
• Passages in another languageA French block on an English page, unmarked, is read aloud in an English voice. Common on bilingual Canadian sites and caught by almost nothing.
• Pressure to decide nowCountdowns, “only 2 left”, “14 people are viewing this”. A rule finds the sentence and cannot tell a real deadline from a timer that resets on reload.
• Declining, made to feel bad“No thanks, I don’t want to save money.” The way out exists, which is all a rule checks, and it has been written to charge you for taking it.
• Whether anyone can reach a personA site can pass every check and still have no way through to a human, which is where everybody the automation failed ends up.
• Forms that cannot be finishedEvery field labelled and the form still unfinishable: a format never named, a question nobody can answer in the order it is asked.

Every one of these had to pass the same test before it was built: a rule must not be able to answer it. If a rule can, it belongs in the free checks, where it costs nothing to run.

A machine can tell you the alt text is there. It cannot tell you whether it describes the picture. This is the part you pay for: Kithe reads the page, looks at the image, and writes wording you can use.

The picture on the page

What the page has

<img src="/img/header-2.jpg" alt="Our team at the summer barbecue">

Every automated checker on the market calls this a pass. There is an alt attribute, it is not empty, it is not a filename. Nothing flags it — and a screen reader announces a barbecue.

What it should have instead

<img src="/img/header-2.jpg"
     alt="Trays of metal printing type, with a composing
          stick holding a line of set text across them.">

Kithe looks at the actual image and the words around it, and writes this for you to approve, edit or throw out.

See the worked judgement cases, with the markup, on the examples page

This is what comes back. Not a score, not a traffic light — the page itself, with each problem ringed and keyed into the margin. Point at a ring to light up its note.

Read all six findings on this page

A machine can be certain about these. They are facts about the page, not opinions, so you get the same answer every time you run it. Each one tells you the page, the element, and what to change.

Read what each check is looking for, in full

This matters more than the feature list. If a supplier is vague about any of it, ask them to put it in writing.

• Never

  We will never issue a certificate.

  There is no such thing as a certificate of accessibility from a scanner. Anyone selling you one is selling you a PDF, not a working website.

• Never

  We will never tell you the site passes.

  Kithe hands you findings to read. It is not a compliance certificate and none of it is legal advice. Whether your site meets a standard is a judgement about you and your site, and it is not ours to make on your behalf.

• Never

  We will never change your site.

  Kithe reads pages. No login to your CMS, no write access, no mechanism to edit anything at all. Every fix is made by you.

• Never

  We will never ask you to install anything.

  No script tag, no plugin, no build step, no account for us on your side. We read what is already public. That is why the first check needs nothing from anybody.