WCAG 2.1 isn't optional guidance. It's the legal standard for web accessibility in the US, EU, UK, Canada, and Australia. For most WordPress sites, images are the primary compliance failure point.

What Is WCAG 2.1 and Who Does It Apply To?

WCAG stands for Web Content Accessibility Guidelines, published by the World Wide Web Consortium (W3C), the international standards body for the web. Version 2.1, released in 2018, is the current baseline standard for web accessibility. It defines three levels of conformance: Level A (minimum), Level AA (standard), and Level AAA (enhanced). Level AA is the level referenced by virtually every accessibility law worldwide, and it's the standard your WordPress site should meet if you serve any audience in jurisdictions with accessibility laws.

The geographic reach of WCAG 2.1 is broader than most site owners realize. In the United States, the ADA (Americans with Disabilities Act) Title III has been consistently applied to websites by federal courts since at least 2017. The Department of Justice issued formal guidance in 2022 confirming that websites must comply with WCAG 2.1 AA standards. In the European Union, the European Accessibility Act (EAA) applies to commercial websites operated by businesses with 10 or more employees, with enforcement effective June 2025. The UK Equality Act and Canada's AODA reference equivalent standards. If your site operates internationally or serves customers in any of these regions, you're likely subject to these requirements.

For WordPress sites, WCAG 2.1 Level AA compliance isn't aspirational, it's legally expected if you operate in any of these jurisdictions and your site is considered a place of public accommodation. If you sell products or services, publish content for a general audience, or accept appointments or applications online, your site almost certainly falls under these requirements. The sooner you implement compliance, the lower your legal risk and the better experience you provide to all users, including those with disabilities.

Success Criterion 1.1.1. The Image Alt Text Rule

Principle 1 of WCAG is Perceivable: "information and user interface components must be presentable to users in ways they can perceive." Success Criterion 1.1.1 operationalizes this principle for non-text content: "All non-text content that is presented to the user has a text alternative that serves the equivalent purpose." In plain language, every image that conveys information must have a text description that conveys the same information to someone who cannot see the image.

The phrase "equivalent purpose" is the key to understanding what makes alt text adequate. If a photo of a product shows a red suede loafer with a gold buckle on a white background, the alt text needs to convey that the image shows a red suede loafer with a gold buckle, not just "shoe" or "product image." The description must function as a substitute for the image for someone who cannot see it. Screen readers, software used by blind and low-vision users, read alt text aloud. If the alt text is inadequate or missing, the screen reader user gets an inadequate or absent experience, missing critical information about the image's content.

For images that are purely decorative, background textures, divider lines, purely aesthetic elements with no informational content. WCAG requires a different approach. These images should have an empty alt attribute (alt="") rather than a missing one entirely. The empty alt tells screen readers to skip the image entirely, which is the correct behavior. An image with no alt attribute at all causes some screen readers to read out the image filename, which is disruptive and unhelpful to users. The distinction between alt="" and a missing alt attribute matters tremendously for accessibility.

The difference between alt='' (correct for decorative images) and a missing alt attribute (incorrect for any image) matters. alt='' = screen reader skips the image intentionally. No alt attribute = screen reader may read the filename. Always include the alt attribute, just leave it empty for decorative images.

Which Images Need Alt Text (And Which Don't)

Not all images on a WordPress site are equal from a WCAG perspective. The standard divides images into meaningful images (those that convey information) and decorative images (those that exist purely for visual effect, with no informational content). The key question is: would a visitor who cannot see this image miss any information? If yes, the image needs descriptive alt text. If no, it should use alt="" to indicate it's purely decorative and can be skipped by assistive technology.

The category that causes the most confusion is linked images. When an image is the only content inside a link, for example, a company logo that links to the homepage, or a social media icon that links to a profile page, the alt text needs to describe the link's destination, not just the image itself. The logo that links to the homepage should have alt="DuplexFix, home" or simply alt="DuplexFix," not alt="logo image" or alt="". This ensures screen reader users understand what clicking the image will do.

Images that NEED descriptive alt text:

  • Product images in WooCommerce, describe the product, variant, angle, and any distinguishing features
  • Blog post featured images and inline images that illustrate the article's content
  • Charts, graphs, and infographics, alt text should summarize the key data or finding, not just say "chart"
  • Screenshots and UI captures, describe the application and what's shown on screen
  • Logos in the header or footer that are the only link to the homepage
  • Team member photos, describe the person's role if shown in a professional context
  • Before/after images, both images need alt text describing the state shown

Images that should use alt="" (empty, not missing):

  • Decorative section dividers or borders with no informational purpose
  • Background gradient or texture images that exist purely for visual appeal
  • Purely decorative icons that have adjacent text labels (e.g., a star icon next to the text "Reviews")
  • Stock photos used purely for visual appeal that don't relate to the page's specific content

How to Audit Your WordPress Site for WCAG Compliance

A WCAG audit for images has two parts: finding images that are missing alt text entirely, and evaluating whether existing alt text is adequate and serves an equivalent purpose. The first part can be automated with tools and plugins. The second part requires human judgment, a tool can confirm that an alt attribute exists, but only a person can determine if "image" is adequate alt text for a photograph of a surgical procedure or a complex technical diagram.

For most WordPress sites, the audit reveals that the majority of the problem is missing alt text, not inadequate alt text. This is the solvable part. Once you've fixed the zero-alt-text images, you can focus human review time on the smaller set of images where the generated or manually written descriptions might need refinement. Start with automation to identify gaps, then apply judgment to fix quality issues.

Method 1. Google Lighthouse (Free, per page): Open Chrome on any page → press F12 → click Lighthouse → Run Audit → Accessibility. Look for "Images do not have alt attributes." Lighthouse tests the rendered page, including images loaded by JavaScript or page builders like Elementor. It's quick but only tests one page at a time.

Method 2. AI Alt Text Generator Bulk Scan (Most complete): The plugin audits your entire WordPress media library in seconds, not page-by-page, but your entire uploaded image collection. Run it from the WordPress admin after installing the plugin. It shows total image count, images missing alt text, and estimated fix cost. This gives you the fullest picture of your compliance gaps.

Method 3. Screaming Frog SEO Spider (Up to 500 URLs free): Crawl your site → Images tab → filter "Missing Alt Text." Export as CSV for a complete list. Screaming Frog tests the rendered HTML of each page, catching images embedded by themes, page builders, and plugins. It's thorough and gives you actionable data.

Method 4. WAVE Web Accessibility Evaluator (Free browser extension): Install the WAVE extension for Chrome or Firefox. Visit any page and click the WAVE icon, it overlays accessibility errors directly on the page, with a red icon marking each image missing alt text. Excellent for visual, page-by-page review and understanding what users see.

How to Fix Image Accessibility Issues at Scale

For a small site with under 50 images, manual fixing is practical. Go to Media → Library in WordPress admin, click each image, fill in the Alternative Text field with a description of the image content, and save. This approach gives you full control and ensures quality, but doesn't scale. At 50 images averaging two minutes each, that's already over an hour and a half of focused effort. At 200+ images, manual fixing becomes impractical.

For sites with hundreds or thousands of images, which describes most active WordPress sites, manual fixing isn't realistic. The math simply doesn't work. A WooCommerce store with 500 products, each with 3-4 product images, has 1,500-2,000 images to caption. Doing that manually, even at one minute per image, would take 25-33 hours of work. And that's before accounting for future uploads. Most site owners never find the time or budget to complete manual fixes at that scale.

AI Image Alt Text Generator solves this with its Bulk Scan and generation pipeline. It uses GPT-4 Vision to analyze each image and generate WCAG 2.1-compliant descriptions in batch. The Accessibility Mode specifically follows the phrasing conventions that screen reader users find most useful, concise, purposeful, describing the function or content of the image without the redundant "image of" prefix that WCAG explicitly discourages.

  • Install AI Image Alt Text Generator from Gumroad
    Download and activate the plugin in WordPress
  • Go to plugin settings, select Accessibility Mode
    This mode prioritizes WCAG compliance over SEO keyword inclusion
  • Connect your OpenAI API key
    Free credits available for new accounts; API cost is $0.001-$0.003 per image
  • Run Bulk Scan, review the count and estimated cost
    Takes 60-90 seconds to audit your entire media library
  • Generate alt text for all missing images in one click
    Runs in background; takes 1-2 minutes per 100 images
  • Review generated descriptions for specialized or sensitive images
    Medical, legal, technical images benefit from human review
  • Enable auto-generate on upload for ongoing compliance
    Every new image gets tagged automatically from upload forward

ADA website accessibility lawsuits have increased steadily every year since 2015. In 2023, Seyfarth Shaw's annual report recorded 4,605 ADA Title III federal lawsuits related to website accessibility, a 4% increase over 2022. The most common allegation in these lawsuits is missing or inadequate alt text on images. The pattern is consistent: law firms using automated scanning tools identify sites with accessibility failures, send demand letters, and negotiate settlements. The accessibility compliance gap creates a predictable legal liability.

The cost of reactive compliance, responding to a demand letter or lawsuit, is significantly higher than the cost of proactive compliance. A single ADA demand letter typically costs $5,000, $15,000 in legal fees to respond to, and settlements often range from $10,000, $50,000 plus attorney fees and a compliance deadline. Compare this to the cost of fixing alt text: for a site with 1,000 images, AI Image Alt Text Generator plus OpenAI API fees total well under $50. The math is undeniable, fixing compliance now is vastly cheaper than defending a lawsuit later.

The legal landscape is also expanding. The European Accessibility Act goes into effect for commercial websites in June 2025. The UK Equality Act's digital accessibility requirements continue to be enforced. Canadian AODA compliance deadlines have passed. If your site serves international customers, the question isn't whether accessibility law applies, it's which laws apply and on what timeline. Proactive compliance protects you from liability across all these jurisdictions simultaneously.

The DOJ's 2022 guidance explicitly states that the ADA applies to websites and that WCAG 2.1 Level AA is the benchmark the DOJ uses to assess compliance. This guidance applies to any business open to the public, regardless of size. It's not optional or aspirational, it's the legal standard.

Maintaining Compliance Long-Term

WCAG compliance isn't a one-time fix, it's an ongoing operational requirement. Every new image you upload, every WooCommerce product you add, every blog post you publish adds to your image inventory. Without a systematic process, new compliance gaps open as fast as you close old ones. The only sustainable approach is to make alt text generation automatic and default, so compliance becomes the starting state rather than something that requires periodic manual auditing and correction.

AI Image Alt Text Generator's auto-generate on upload feature solves this fundamental problem. Once enabled, every image uploaded to your WordPress media library is automatically processed by GPT-4 Vision and tagged with a description before it ever appears on your site. This makes WCAG 2.1 Success Criterion 1.1.1 compliance the default state rather than something that requires periodic manual auditing and catch-up work. You move from "compliance as a project" to "compliance as a system."

What WCAG level do I need to comply with?
Level AA is the legally required standard in virtually every jurisdiction: US (ADA, Section 508), EU (EAA), UK (Equality Act), Canada (AODA), and Australia (DDA). Level A is the minimum, meeting only Level A typically isn't sufficient for legal compliance. Level AAA is aspirational and not legally required in most contexts. Focus on Level AA as your compliance target.
Can AI-generated alt text be considered WCAG-compliant?
Yes. WCAG Success Criterion 1.1.1 requires that alt text serves the "equivalent purpose" of the image. If AI-generated alt text accurately describes the image content, it meets this requirement. GPT-4 Vision is generally accurate for standard website imagery (products, landscapes, screenshots, people). You should review and correct AI-generated alt text for specialized images (medical, technical, legal) where precision is critical.
Do I need to add alt text to background images set via CSS?
No. Background images set via CSS (background-image: url()) are not part of the HTML content and are ignored by screen readers. They're treated as decorative. Only images in HTML img tags, or images rendered by JavaScript and page builders into the DOM as img elements, need alt text under WCAG 1.1.1.
How often should I audit my site for accessibility?
After any major content update, theme change, or plugin update that might affect how images are rendered. A quarterly audit is good practice for active sites. The most effective ongoing approach is to use auto-generate on upload to maintain compliance continuously rather than relying on periodic audits to catch gaps.

Make Your WordPress Site WCAG 2.1 Compliant Today

Stop risking ADA lawsuits over missing alt text. AI Image Alt Text Generator audits your entire media library and generates compliant descriptions for every image, in one operation.

Get AI Alt Text Generator →