What WCAG Levels Mean for a Small Business Website

WCAG is the technical standard from the W3C Web Accessibility Initiative. WCAG 2.2 has 13 guidelines organized under four principles: perceivable, operable, understandable, and robust. You conform by meeting testable success criteria at level A, AA, or AAA [1]. The letters are not a design style. They are a bar.

What do the four principles mean in practice?

Perceivable means a person can take in the content, including with alt text or captions. Operable means they can use it, including from a keyboard. Understandable means the labels and errors make sense. Robust means it works with the tools people already have. WAI's introduction uses the same idea in plainer language: people have to perceive, understand, navigate, and interact [2]. The principles are the headings. The success criteria are the tests.

Which version should a new site follow?

W3C encourages the latest. WCAG 2.2 was published on 5 October 2023, with an update on 12 December 2024. Later versions add criteria. They do not change the old ones, except that 4.1.1 Parsing is obsolete in 2.2 [1]. A requirement written against 2.1 is not thrown out by moving to 2.2. You add the new criteria. You do not get to drop the old ones.

Is WCAG the same thing as a law?

Not by itself. In the United States, the Department of Justice's March 2022 web guidance says the ADA applies to state and local government sites and to businesses open to the public, and it points to WCAG and the Section 508 standards as helpful guidance. That document does not set a detailed technical regulation, and it says the guidance has no force of law [3]. ISO/IEC 40500:2025 is the ISO text of the October 2023 WCAG 2.2, and EN 301 549 in 2026 uses WCAG 2.2 [1]. Those are standards. Whether one of them is required for your business is a legal question, not a line in this article.

What does level AA usually refer to?

Meeting the level A criteria and the level AA criteria. AAA is the stricter set of success criteria on the same guidelines [1]. If a contract says "WCAG AA" and does not name the version, ask which version. 2.2 adds criteria that earlier 2.x versions did not have, and it does not remove the older criteria except the obsolete parsing one [1].

Who checks whether you actually met the level?

A person, using a method such as WCAG-EM when you need a real conformance look, not a browser score [5]. WAI also publishes Easy Checks for a first pass you can do without being a specialist [5]. The level in the contract is a list of criteria. Someone still has to try the pages.

What fails on an ordinary small-business page?

The Justice Department's list is the practical one: poor contrast, color used alone, images with no text alternative, video without captions, forms without labels or error text, and mouse-only controls [3]. WAI's forms tutorial adds the build detail: a label on each control, instructions, validation that a person can recover from, and no time limit unless the person can extend it or the limit is essential [4]. Those are the failures a small site actually ships.

Does a tool report mean you conform?

No. WAI says no tool alone can determine whether a site meets the guidelines. A person has to evaluate it, and evaluation should start early because late fixes mean redoing work [5]. The Justice Department says a clean automated report is not proof of access, and an overlay is not a substitute for that check [3]. A score of 100 in a browser extension is not a WCAG conformance claim.

Where does alt text sit in the levels?

It is an access requirement and a search field at the same time. WAI says equivalent alt text is what a screen reader and a search engine get instead of the picture [2]. Google says alt text is the most important image metadata and that keyword stuffing is a bad experience [6]. Write the description. Do not paste the target phrase into every image and call it AA.

• A, AA, AAA — success criteria, stacked. AA means A plus AA.
• 2.2 — the version W3C encourages. It adds criteria. It does not erase the older ones.
• 4.1.1 — Parsing is obsolete in 2.2.
• A law — WCAG is a standard. Do not treat a guidance page as a statute.
• A tool score — not a conformance claim.

How does this show up in a website project?

As acceptance criteria, not as a plugin in the last week. Website development should name the version and the level in the scope. A mobile layout is related and it is not the same test. Maintenance is where a new form does not quietly drop the labels. If the contract is still being priced, the price should say whether an evaluation is included or quoted separately.

What should you write down before you promise a level?

The version, the level, and who will evaluate it. W3C wants the latest version, and it wants a human check, not only a tool [1] [5]. If you cannot name those three, you do not yet have a WCAG promise. You have a sentence.