Accessibility Deep Dive: Understanding WCAG Guidelines

Web accessibility is not a niche concern or a checkbox for large corporations. According to the CDC’s 2024 data, roughly 18% of US adults report difficulty seeing, and similar shares report difficulty hearing or walking. For a small business in Houston, that represents a meaningful share of the people who might visit your website on any given day.

The Web Content Accessibility Guidelines, known as WCAG, exist to ensure those visitors can actually use what you built. This post breaks down what the guidelines are, which version applies right now, and what AA compliance requires in practical terms.

What WCAG is and who publishes it

WCAG is published by the World Wide Web Consortium (W3C) through its Web Accessibility Initiative. The W3C is the international body that also sets the standards for HTML and CSS. WCAG is not a product, a certification, or a paid service. It is an open specification that defines how web content should be structured so that people with disabilities can perceive, understand, and interact with it.

The guidelines cover a wide range of disabilities: low vision and color blindness, deafness and hearing loss, motor impairments that prevent mouse use, and cognitive conditions that affect attention or processing.

WCAG 2.1 vs. WCAG 2.2

WCAG 2.2 became the official W3C recommendation on October 5, 2023. It added nine new success criteria to the 2.1 standard, including minimum touch target sizes, more rigorous focus visibility requirements, protections against accessible authentication friction, and alternatives for drag-and-drop interactions.

For most Houston businesses rebuilding or auditing a site today, WCAG 2.2 is the current reference. All criteria from 2.1 carry forward; nothing was removed. The practical difference for most sites is modest: if you are already at 2.1 AA, closing the gap to 2.2 AA primarily means reviewing focus indicators and touch targets.

The four WCAG principles: POUR

Every WCAG success criterion maps to one of four principles.

Perceivable: All content must be available to at least one sense. Images need text alternatives. Videos need captions. Content cannot rely solely on color to convey meaning.

Operable: All functionality must be reachable without a mouse. Keyboard navigation, sufficient time to complete actions, and avoidance of content that causes seizures are all operable criteria.

Understandable: Language must be declared in the HTML. Error messages must explain what went wrong and how to fix it. Navigation must behave consistently across pages.

Robust: Content must work with current assistive technologies and hold up as those technologies evolve. This primarily means writing valid, semantic HTML that screen readers and browser extensions can parse reliably.

Understanding conformance levels: A, AA, and AAA

WCAG has three levels of conformance.

Level A covers the most critical barriers. A site that fails A-level criteria is essentially unusable for some visitors. Missing image alt text is a Level A failure.

Level AA adds requirements that directly affect everyday usability: the 4.5:1 color contrast ratio for normal text (3:1 for large text at 18pt or larger, or 14pt bold), descriptive form labels, meaningful focus indicators, and sufficient heading structure, among others. AA is the standard most legal frameworks reference and the baseline most professional accessibility work targets.

Level AAA is the most demanding tier. Some AAA criteria are impractical to meet across an entire site. They are typically pursued for services with specialized or regulated audiences, not for general small business websites.

Level A alone is not enough. A site that meets only A-level criteria will still fail on contrast, keyboard focus, form usability, and other everyday barriers that affect a large portion of disabled users.

ADA, Title III, and your business website

The Americans with Disabilities Act requires places of public accommodation to be accessible to people with disabilities. Courts have increasingly applied this requirement to business websites. The Department of Justice’s April 2024 final rule codified WCAG 2.1 AA as the specific standard for state and local government websites under Title II. For private businesses covered under Title III, there is no equivalent federal rule, but federal courts have consistently treated WCAG 2.1 AA as the benchmark when evaluating whether a site is accessible.

For a Houston small business, the practical implication is this: building to WCAG 2.1 AA is the clearest, most defensible approach to demonstrating that your site does not exclude users with disabilities. It is also good design. Sites that meet AA requirements are easier to use for everyone: on small screens, in bright sunlight, with an aging monitor, or with a slow connection.

Accessibility ties directly into how professional design builds customer trust. A site that is hard to navigate or impossible to read in low-light conditions signals carelessness to every visitor, not just those using assistive technology. It is also an integral part of designing a site that serves small business goals, where usability and credibility carry more weight than visual flair alone.

At Desque, accessibility is not an optional upgrade. WCAG AA color contrast and keyboard navigation are baseline requirements on every web design build we deliver.

A practical WCAG compliance checklist for SMB websites

You do not need to read every success criterion to do a first pass. These eight checks catch the most common failures on small business sites.

1. Color contrast: Run your primary text and background colors through a contrast checker. Normal body text needs a 4.5:1 ratio or better.
2. Image alt text: Every meaningful image needs a descriptive alt attribute. Decorative images should have alt="" to be skipped by screen readers.
3. Keyboard navigation: Tab through your entire site without using a mouse. Every link, button, and form field should be reachable and visible.
4. Form labels: Every input field needs a descriptive <label> element linked to it. Placeholder text does not count.
5. Heading structure: Use heading levels sequentially (H1, then H2, then H3). Do not skip levels or use heading tags for visual styling.
6. Video captions: If your site has any video, all speech and significant audio needs accurate captions.
7. Focus indicators: The browser’s default focus ring can be stripped by CSS. Make sure focused elements are visually distinct.
8. Error messages: Form validation errors should clearly identify which field failed and explain how to correct it.

Tools for a quick self-audit

Three free tools cover the automated portion of an accessibility audit.

WAVE (WebAIM) is a browser extension that annotates your page with accessibility errors, alerts, and structural information. It is the most visual option.

Lighthouse is built into Chrome DevTools. Run an accessibility audit from the Lighthouse panel on any page; it scores the page and lists specific failures with linked documentation.

axe DevTools (Deque) is a browser extension that runs a more comprehensive automated check. It integrates into the DevTools console and is widely used for development workflows.

Note that automated tools catch roughly 30 to 40% of accessibility issues. Keyboard testing and screen reader testing with real assistive technology are still necessary for a thorough audit.

What to expect from an accessibility review

A proper accessibility review covers both automated scanning and manual testing. It produces a prioritized list of issues mapped to specific WCAG criteria, ranked by impact and effort to fix.

If your site is due for a redesign, an accessibility review beforehand informs the scope. Fixes baked in during design cost far less than retrofits added after launch. For the Delta Security Force site and the Detail Exchange redesign, accessibility requirements were part of the design brief from day one, which meant contrast, keyboard navigation, and semantic structure were right the first time rather than patched afterward.

For a deeper look at how WCAG color and typography requirements apply in practice, the next part of this series covers accessible color and typography in detail.

If you want an expert eye on your current site before your next redesign, reach out and we can walk through the gaps together.

---

Frequently asked questions

What is WCAG and who creates it?

WCAG stands for Web Content Accessibility Guidelines. It is published by the W3C (World Wide Web Consortium) through its Web Accessibility Initiative. The guidelines define how web content should be built so people with disabilities (visual, auditory, motor, and cognitive) can use it effectively.

What is the difference between WCAG 2.1 and WCAG 2.2?

WCAG 2.2 became the official W3C recommendation on October 5, 2023. It added nine new success criteria to the 2.1 standard, covering focus visibility, minimum touch target sizes, accessible authentication, and drag-and-drop alternatives. WCAG 2.2 is the current version. All 2.1 criteria carry forward unchanged.

What are the WCAG conformance levels A, AA, and AAA?

Level A covers the most critical barriers: the kind that make a site completely unusable for some users. Level AA adds practical requirements like color contrast ratios, keyboard navigation, and labeled form fields. It is the legal and industry baseline most businesses target. Level AAA is the most rigorous and is generally pursued only for specialized audiences or regulatory mandates.

Does ADA require my business website to be accessible?

ADA Title III requires places of public accommodation to be accessible, and courts have extended this to many business websites. There is no single federal rule specifying WCAG 2.1 AA for private businesses, but courts consistently treat it as the standard against which compliance is measured. Building to AA is the clearest way to demonstrate good-faith effort.