WordPress Accessibility Plugin: How to Meet WCAG 2.1 (and Prepare for the European Accessibility Act)

What is WCAG 2.1 and why does it apply to WordPress?

The Web Content Accessibility Guidelines (WCAG) 2.1, published by the W3C, are the international standard for web accessibility. They define how to make digital content accessible to people with disabilities — including users who rely on screen readers, keyboard navigation, or assistive technologies.

WCAG 2.1 is organized into three conformance levels: A (minimum), AA (standard), and AAA (enhanced). Most regulations, including the European Accessibility Act, require Level AA compliance at minimum.

WordPress itself does not enforce WCAG compliance. The platform generates accessible markup where possible, but every theme, plugin, and piece of content you add can introduce accessibility issues — and image ALT text is the most common failure on WordPress sites, according to the WebAIM Million report.

The European Accessibility Act: deadlines and fines

The European Accessibility Act (EAA) — Directive 2019/882 — entered into force in June 2025. It requires all digital products and services offered in the EU to meet accessibility standards aligned with WCAG 2.1 Level AA. This is not a voluntary guideline. It is a binding regulation.

Who is affected? Any business that sells products or provides services to EU users — including WooCommerce stores, service websites, SaaS platforms, and media sites. If your WordPress site is accessible to EU users, the EAA applies to you.

WCAG 2.1 ALT text requirements for images

The core accessibility requirement for images is defined in WCAG 2.1 Success Criterion 1.1.1 — Non-text Content (Level A): every non-decorative image must have a text alternative that conveys the same information or function.

The 4 ALT text mistakes WordPress sites make

Four patterns account for the vast majority of ALT text violations on WordPress. All four are undetectable without a dedicated audit — they are invisible to visual inspection.

1. Missing ALT text

Images uploaded without any ALT attribute. WordPress does not require ALT text before publication, so many media libraries accumulate hundreds of images with no text alternative. Screen readers will typically announce the filename — which is meaningless to users.

2. Generic ALT text

ALT attributes that use placeholder words: "image", "photo", "banner", "logo". These pass a basic presence check but fail WCAG 1.1.1 because they convey no meaningful information about the image content.

3. ALT text that is too short

A one-word ALT like "cat" or "team" technically exists but rarely conveys equivalent information. WCAG requires the text alternative to serve the same purpose as the image — a meaningful description is necessary for informative images.

4. Duplicated ALT text

Multiple images sharing the same ALT attribute — a common result of bulk uploads or template-based sites. Duplicated ALTs create confusion for screen reader users navigating by image, and signal low-quality content to search engines.

How to audit image accessibility in WordPress

WordPress's native media library provides a way to edit individual ALT attributes, but no built-in audit tool. There is no way to see, at a glance, how many images are missing ALTs, which ones use generic text, or whether you have duplicates across your library.

A dedicated WordPress accessibility plugin scans your entire media library and surfaces issues by category. A structured audit should classify every image across four dimensions:

How to fix ALT text at scale

Once you have identified which images are non-compliant, the challenge is remediation — especially on sites with hundreds or thousands of images. Manual correction is time-consuming and error-prone without the right workflow.

Option 1: Bulk inline editing

The most controlled approach: work through the audit results category by category — missing first, then generic, then duplicated — and write descriptive ALT text for each image. This produces the highest-quality results and is recommended for product photos, diagrams, and images of people.

Option 2: Automatic generation from filename

For sites with consistent file naming conventions, generating ALT text from the filename is a fast starting point. Filikod's Automatic ALT Text Generation setting strips file extensions and special characters to produce a basic ALT. Better than nothing — but review for accuracy before relying on it.

Option 3: AI-assisted generation

The most powerful approach: AI vision models analyze each image and generate a descriptive ALT text based on actual visual content. This is especially valuable for large media libraries where manual review is not feasible. Filikod's premium tier will offer AI-powered ALT generation as a key feature in the coming months.

WCAG 2.1 image accessibility checklist for WordPress

Use this checklist to verify your WordPress site meets WCAG 2.1 Level AA for images before the EAA June 2030 deadline.

• All non-decorative images have an ALT attribute with meaningful descriptive text
• Decorative images use an empty ALT attribute (alt="")
• No image uses a generic ALT value ("image", "photo", "banner", "icon")
• No image uses its filename as ALT text
• No two meaningful images share the same ALT attribute
• Functional images (buttons, links) have ALT text describing the action or destination
• Product images on WooCommerce include product name and key attribute in ALT text
• Infographics and charts have a text alternative that conveys the same data
• New images uploaded after June 2025 are compliant at the time of upload
• A structured audit has been run on the full media library — not just recent uploads