Vira-AI

technical · 5 min read

Is your website legal? WCAG accessibility explained

A non-technical explanation of website accessibility guidelines, how to stay compliant, and why accessible design boosts conversions.

2026-07-02 · By ViraAI Team

For years, website accessibility was seen as a checkbox for government agencies and enterprise corporations.

But the legal and commercial landscape has changed. In the United States, ADA (Americans with Disabilities Act) lawsuits targeting small business websites have skyrocketed. In Canada, provincial laws (like the AODA in Ontario) carry heavy fines for non-compliant business sites.

Aside from the legal risks, website accessibility is a major business opportunity. Roughly 20% of the population lives with some form of permanent or temporary disability. If your site blocks them, you are locking out 20% of your potential market.

Here is a simple, non-technical breakdown of website accessibility, and how to make sure your site stays on the right side of the law.

What is Website Accessibility (WCAG)?

Website accessibility simply means designing your site so that anyone—including people with visual, auditory, physical, or cognitive impairments—can read, navigate, and use it.

The global standard for this is the Web Content Accessibility Guidelines (WCAG), currently on version 2.2. The standards are grouped into three levels of compliance:

  • Level A: The absolute minimum. Basic navigation, screen reader access.
  • Level AA: The target standard for business websites. Covers color contrast, clean keyboard navigation, and proper scaling.
  • Level AAA: The highest standard. Typically reserved for specialized medical or educational resources.

The core checkpoints to test today

You don't need a degree in computer science to spot major accessibility issues. Here are four simple tests you can run on your site right now:

1. The Keyboard Test (No Mouse)

Unplug your mouse or turn off your trackpad. Open your website homepage and try to navigate using only the Tab key on your keyboard.

  • Can you see where the focus box is?
  • Can you open the menu, fill out the contact form, and hit submit using only the Tab and Enter keys?
  • Do you get stuck in a "trap" where you can't navigate backward?

If you cannot navigate your site with a keyboard, anyone using a screen reader or assistive switch device is blocked from buying from you.

2. The Color Contrast Test

Open your website on your phone under direct sunlight. Can you still read the body text?

WCAG 2.2 AA requires a contrast ratio of at least 4.5:1 for body text. If you have light gray text on a white background, or white text laid over a busy photo, it is non-compliant. The text is invisible to people with low vision or color blindness.

3. Image Alt Text

Every image on your site must have "Alt Text" (alternative text) embedded in the code. Alt text is a short, written description of what is in the image.

If you have a photo of a dental office lobby, the alt text should be: "Modern dental practice waiting room with wood paneling and green chairs.". If a screen reader encounters the image, it reads this description aloud. If the alt text is missing or just says "IMG_30291.jpg", the image is useless.

4. Text Rescaling

Try zooming in on your website to 200% in your browser.

  • Does the text overlap?
  • Do buttons disappear off the screen?
  • Can you still complete the primary actions?

An accessible site must scale cleanly without breaking layout.

Why custom code beats accessibility overlays

Many businesses try to fix accessibility by installing a cheap Javascript plugin or "accessibility overlay widget" (those small blue figures in the corner of a site).

These overlays do not fix the underlying code. In fact, many screen-reader users actively hate them because they overwrite the user's custom browser configurations. Legally, courts have ruled that widgets do not protect you from ADA lawsuits.

The only real fix is to build the accessibility directly into the HTML structure from the start.

We build every Vira-AI site to WCAG 2.2 AA standards by default. There are no widgets, no bloated scripts, and no compromises on design. Just clean, semantic markup that is accessible to all.

Read our WCAG compliance checklist for a deeper technical breakdown, or check out our pricing to start your accessible build.

Need a website? Get a free quote →