OOmnistu

Blog / Web & Ecommerce

Web & Ecommerce

Website accessibility basics: what WCAG asks of a business site

Understand WCAG's four principles and use introductory checks to identify barriers without claiming a full conformance assessment.

OOmnistu
Reviewed 2026-11-16 · 3 min read

The Web Content Accessibility Guidelines (WCAG) are the shared international standard for making web content usable by people with disabilities. They are developed through the W3C process (https://www.w3.org/WAI/standards-guidelines/wcag/). WCAG 2.2 has 13 guidelines under four principles: perceivable, operable, understandable and robust. Each guideline has testable success criteria at three levels: A, AA and AAA. A site meets WCAG by meeting the success criteria, according to W3C.

This article is not legal advice. Which level you must meet, if any, depends on your country, sector and customers.

The four principles in plain language

The W3C's summary (https://www.w3.org/WAI/standards-guidelines/wcag/glance/) paraphrases the guidelines. Here is what each means for a services or e-commerce site.

Perceivable: can people take in the content?

Operable: can people use it?

Understandable: does it make sense?

Robust: will it keep working?

A 30-minute self-check

  1. Tab through the homepage and one form. Note where focus disappears or order is wrong.
  2. Zoom the browser to 200 percent. Does anything overlap or vanish?
  3. Look at your five most important images. Do they have meaningful alt text?
  4. On an authorized test form that cannot create a real purchase or unwanted submission, submit it empty. Is each error explained?
  5. Play your main video. Are there captions?

Write down what fails. That list is your starting brief for a developer.

What a checklist cannot do

A self-check finds obvious barriers. It is not a conformance claim. W3C itself notes WCAG is a technical standard and not an introduction to accessibility, so use its quick reference and techniques pages for specifics, and test with real assistive technology users where you can.

Limits

This article rests on two W3C WAI overview pages about WCAG, not on the full WCAG specification or its techniques documents. It is a starting checklist, not a conformance claim and not legal advice; accessibility law differs by country and needs counsel.

By Omnistu.

Sources

Previous
Web font loading: avoiding blank text and layout jumps