Buyer guide
Accessibility in the website build
A WCAG logo on a footer is not a conformance claim. W3C’s own logo page says claims are not verified by W3C, and the content provider is solely responsible. If someone makes a claim, the specification says it includes a date, the guideline version, the level, and the pages in scope. A badge with none of that is a decoration.
Written by SiteMivo. We design for the criteria below. We do not claim a certified audit unless a dated one exists. See accessibility. Drafted with research assistance.
The criteria, not the slogan
| Criterion | Level | Name | What you should be able to check |
|---|---|---|---|
| 1.3.1 | A | Info and relationships | Headings are headings in the HTML, not just big text. |
| 2.4.6 | AA | Headings and labels | The heading says what the section is for. |
| 2.1.1 | A | Keyboard | You can do the job without a pointer, unless the path itself requires one. |
| 2.4.7 | AA | Focus visible | You can see which control has keyboard focus. The stricter focus-appearance rule, 2.4.13, is AAA. We do not pretend AA includes it. |
| 4.1.2 | A | Name, role, value | A control has an accessible name, a role, and a state a browser can read. |
| 2.5.3 | A | Label in name | If the button says “Start a project”, the accessible name includes those words. |
| 1.4.3 | AA | Contrast minimum | Text is generally 4.5:1, 3:1 for large text. |
| 1.4.11 | AA | Non-text contrast | Meaningful icons and control boundaries are 3:1 against the adjacent colour. |
| 2.5.8 | AA | Target size minimum | Pointer targets are at least 24 by 24 CSS pixels, with the exceptions in the criterion. |
| 2.3.3 | AAA | Animation from interactions | Motion you trigger can be turned off, unless the motion is the function. We design for this even though AA does not require it. |
Understanding docs: 1.3.1, 2.1.1, 2.4.7, 2.5.8, conformance claims.
Custom websites treat these as build requirements, not a plugin added after the design is frozen.