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.
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?
- Give images and other non-text content a text alternative. Product photos need descriptions; decorative images should not add noise.
- Provide captions or alternatives for video and audio. A demo video without captions leaves out deaf visitors and anyone watching on mute.
- Make content work when presented differently, including through assistive technology, without losing meaning. Use real headings, lists and tables, not styled text that only looks like them.
- Make it easier to see and hear content: enough contrast between text and background is part of this.
Operable: can people use it?
- Everything should work from a keyboard. Try it: press Tab through your homepage and checkout. Can you reach and use every link, menu and button?
- Give users enough time to read and use content. Watch for timed pop-ups and sessions that expire fast.
- Avoid content that causes seizures or physical reactions, such as flashing.
- Help users navigate and find content: clear headings, page titles, consistent navigation.
- Make non-keyboard inputs easier, for example touch targets on phones.
Understandable: does it make sense?
- Write readable text.
- Make pages behave predictably: menus in the same place, no surprise changes when a field is focused.
- Help users avoid and correct mistakes: clear form labels and error messages that say what to fix.
Robust: will it keep working?
- Maximize compatibility with current and future tools. In practice use programmatically exposed names, roles, values and relationships that assistive technologies can understand. Valid markup alone is not proof of accessibility.
A 30-minute self-check
- Tab through the homepage and one form. Note where focus disappears or order is wrong.
- Zoom the browser to 200 percent. Does anything overlap or vanish?
- Look at your five most important images. Do they have meaningful alt text?
- On an authorized test form that cannot create a real purchase or unwanted submission, submit it empty. Is each error explained?
- 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.